A user at the remote site of a dedicated T1 connection complained that intermittently he could not send or receive mail. The machine was current with Microsoft patches and his connection to the main office otherwise worked, but mail was often a problem. This was usually blamed on Internet connectivity problems, but when we put in a SME Server at the main office and he still had the problem, it was obvious that something else was wrong.
I began by getting him to a command prompt and asking him to "ping mailserver". He got responses with no packet loss. I checked from the server side that I could ping him also. I then had him "telnet mailserver 110". This did not work, but it wasn't refused: he just could not connect. My suspicion was that he was being blocked at his end, so to confirm it I obtained his IP address and did
arp -d 10.1.1.92
to delete him from the arp cache. I then had him try the "telnet mailserver 110" again and noted that his machine did NOT appear in the arp cache (arp -an) . That means that the telnet was definitely blocked. As I said, I suspected his end, so I asked him to disable Norton Anti-Virus entirely and reboot. That instantly fixed it.
Turns out that NAV had expired. Whether that caused the problem or not I don't know, but I left him with the promise that he would download a new NAV. He also had very little memory (128 MB running Win2K), so I suggested that be increased also.
Arp can be very helpful in debugging problems like this.
Got something to add? Send me email.
More Articles by Tony Lawrence © 2012-07-14 Tony Lawrence
Whenever the literary German dives into a sentence, that is the last you are going to see of him till he emerges on the other side of his Atlantic with his verb in his mouth. (Mark Twain)