Depends on the router it’s hooked to and the level of traffic logging being performed. Being connected to a LAN is not the same as being connected to the internet.
No, it doesn’t depend on the router. The device can either send traffic to other devices on the internet or it can’t. If the device can ping something on the internet, then it is connected to the internet. It’s a tautology.
All traffic from that device is going to pass through the router. In order to start communicating with the other device, the first device has to send a packet. The router sees that packet, and routes it to the other device. If there’s no internet connection, things die here, but the router still saw that initial packet.
Sorry, I realized I misread your earlier post. I missed the word “trying,” and it sounded like your were saying the device might not be connected to the internet even though it’s successfully pinging a server.
They connect to allow the vitals to be pulled into the EMR to allow continuous documentation of vitals for the anesthesia record or central patient monitoring. More and more frequently, the database is not onsite and is shared amongst several sites within a hospital system.
But the device itself shouldn’t need internet connectivity for this. That networking should be handled by a local master device, the same way access control systems (e.g. Door badge readers, alarm monitoring, etc) work.
Then this device would only use a local, isolated network to access the master device.
Those things shouldn’t even be connected to the internet.
Might not be. This could have simply been some IT guy noticing that something kept trying to ping the outside world.
The only way some IT guy can notice it pinging the outside world is if it’s connected to the internet.
Depends on the router it’s hooked to and the level of traffic logging being performed. Being connected to a LAN is not the same as being connected to the internet.
No, it doesn’t depend on the router. The device can either send traffic to other devices on the internet or it can’t. If the device can ping something on the internet, then it is connected to the internet. It’s a tautology.
All traffic from that device is going to pass through the router. In order to start communicating with the other device, the first device has to send a packet. The router sees that packet, and routes it to the other device. If there’s no internet connection, things die here, but the router still saw that initial packet.
Sorry, I realized I misread your earlier post. I missed the word “trying,” and it sounded like your were saying the device might not be connected to the internet even though it’s successfully pinging a server.
Lol, no worries.
They connect to allow the vitals to be pulled into the EMR to allow continuous documentation of vitals for the anesthesia record or central patient monitoring. More and more frequently, the database is not onsite and is shared amongst several sites within a hospital system.
But the device itself shouldn’t need internet connectivity for this. That networking should be handled by a local master device, the same way access control systems (e.g. Door badge readers, alarm monitoring, etc) work.
Then this device would only use a local, isolated network to access the master device.
Agreed. Network connected to an isolation vlan without internet access