Associate
- Joined
- 25 Apr 2012
- Posts
- 107
Given the intermittency of the fault, I’d recommend perusing this avenue first. The quote below is a .BAT script that will prompt you to enter an ip address, and then store the corresponding date, time and ping responses within a text document on your desktop. Keep this going for a few days and have a look through document occasionally. If you notice any drops, see if there is some underlying pattern.
Now, it is probably best to run some sort of packet capture next. I'd recommend something like Wireshark (it is fairly easy to use). You can either configure a mirror port on router to capture all of the network data or just run a Wireshark trace on your local connection (given that it only appears to be happening from your computer). You can then reference the drops on the text document with Wireshark and have a look at the packet data prior to the disconnection (or even upload this trace so I can take a look).
@Echo off
set /p host= Enter IP Address:
set logfile=Log_%host%.log
echo Target Host = %host% >%logfile%
for /f "tokens=*" %%A in ('ping %host% -n 1 ') do (echo %%A>>%logfile% && GOTO Ping)
ing
for /f "tokens=* skip=2" %%A in ('ping %host% -n 1 ') do (
echo %date% %time:~0,2%:%time:~3,2%:%time:~6,2% %%A>>%logfile%
echo %date% %time:~0,2%:%time:~3,2%:%time:~6,2% %%A
timeout 1 >NUL
GOTO Ping)
Now, it is probably best to run some sort of packet capture next. I'd recommend something like Wireshark (it is fairly easy to use). You can either configure a mirror port on router to capture all of the network data or just run a Wireshark trace on your local connection (given that it only appears to be happening from your computer). You can then reference the drops on the text document with Wireshark and have a look at the packet data prior to the disconnection (or even upload this trace so I can take a look).
