From: "Geo" 

"Mike N."  wrote in message
news:d3nec25h86m8rj5a6q6uaupe5k168qkm10{at}4ax.com...

>    Still no joy ... we may need a wireshark (or the MS Network Monitor)
run
> on your end to identify what's going on.

that's going to be difficult since the server is now on a switched gigE
network, I'd have to stick a hub in front of the machine so I could sniff
with my laptop.

Why is this only happening to Randall? Typically when I see something like
this the problem is with the dsl modem/router not having the correct MTU
set for the ISP it's connected to. We use 1492 when that happens and
usually that fixes the problem.

I think Randall should look in his dsl router and see what MTU is set to.
That might explain why he can't traceroute as well.

Randall if you are reading try this, try pinging something near you on the
internet with a ping command

ping 216.144.8.1 -l 1024

see that last number, try 512, 1024, 2048 and find which works then cut the
difference between that and the next bigger one in half until you find the
exact maximum size you can ping with. My bet is it will be somewhere
between 1400 and 1500

Geo.

Geo.

--- BBBS/NT v4.01 Flag-5