4 Operator

 • 

1.8K Posts

December 16th, 2005 20:00

Just a thought..

Pathping from one server to the other, visa versa, are than any lost packet along the way ?

Cisco equipement ?

4 Operator

 • 

1.8K Posts

December 18th, 2005 21:00

"The other strange thing that happens is when you try to connect to the server remotely through RDC occasionally half of the login screen will appear, and then just lock.  When this happens the server stops responding to ping for up to 10 seconds."

two cents on this...

if the MTU at the router is not set properly, packets are dropped , and symptoms like this appear. Pathping from the remote to the RDP endpoint, if the MTU is good you will have few if any lost packets. The MTU may need to be set at the office and at the remote endpoints, each broadband connection can have a different MTU size needed.

 

 

8 Posts

December 18th, 2005 21:00

One possibility is duplex settings mismatch, particularly for 100mb, at gigabit things usually sort themselves out properly. We have seen upgrades via windows update (never mind upgrading to 2003!) reset the manual settings for speed and duplex on Intel nics on 4400/2500 triggering off this problem. The server does not see errors but copying files can be 10 times slower and reliability suffers (typically lumpy). The switch sees load of errors usually on the port however so you can confirm by checking on the switch. You are getting collisions on the half duplex end which the full duplex end cant recognise (how could there be any?) so lost packets. IP will then back off due to poor link......
 
For negotiation with switches to work both the switch and the nic must be set to auto. If this negotiation fails and you end up with different duplex on the switch and nic then above goings on will occur, sometimes this negotiation can work most of the time but fail if you reboot the switch before the server etc etc.
 
We have found there are combinations of switches and nics for which you need to set both manually to 100 full.
 
If you do then 3 things to be careful of.
Dont move the connection to a swith port set to auto, later by mistake.
Recheck nic is still set to 100 full after any reinstall or update of driver by whatever means
If you change the nic or motherboard make sure you recheck as sometimes settings held in on board nvram.
 
 
I guess the same need to check would apply to any of the nic advanced settings after an upgrade.
 
Hope this helps

2 Posts

December 20th, 2005 19:00

I set the NIC to Auto-negotiate 1000Mbps, and ever since I have not had a single problem!
 
Thanks for the help!
No Events found!

Top