Unencumbered by any real knowledge, the only thing that comes to mind is
bad connections: disconnect Ethernet plugs, clean contacts, reconnect.
Are there any other explanations - perhaps with solutions that do not
require driving to the site?
If any part of the end to end path is wireless, I would focus there. You can >also do a traceroute to your intended endpoint to find the various hops
along the way. Try pinging the last hop before your endpoint to see if that >is equally unstable. Keep backing up, hop by hop, until you get solid pings. >The link after that (the first one that is unstable) will be suspect, and
any links after that will be unreliable as a result.
Per Char Jackson:
If any part of the end to end path is wireless, I would focus there. You can >>also do a traceroute to your intended endpoint to find the various hops >>along the way. Try pinging the last hop before your endpoint to see if that >>is equally unstable. Keep backing up, hop by hop, until you get solid pings. >>The link after that (the first one that is unstable) will be suspect, and >>any links after that will be unreliable as a result.
100% hard-wired... and the Tracert seems to show what I expected: a
direct route - since the device (an IP camera) is hung directly on
to the same switch that the server PC is connected to:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 45:09:13 |
Calls: | 6,648 |
Files: | 12,197 |
Messages: | 5,329,773 |