View Single Post
Old 09-09-2005, 14:46   #3
rdhw
Inactive
 
Join Date: Oct 2003
Location: Cambridge
Posts: 567
rdhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation erardhw has entered a golden reputation era
Re: NIC settings changed to allow connection

Quote:
Originally Posted by Gervais
it connected again after changing the settings in the 'network connections' --> 'Configue' --> 'Advanced' tabs from auto setting (working for years with no problems) to '10BaseT Half Duplex'
This is a standard fix for ethernet auto-negotiation problems. "10Base T Half Duplex" is the safest option, that should work in most circumstances when auto-negotiation fails. When an ethernet link starts to go dodgy, it is usually auto-negotiation that fails first. Long ethernet cables are tricky for auto-negotiation: try a shorter one and see if that works. If a shorter cable solves the issue, look at the original long cable for any signs of damage.

"!0Base T Half Duplex" still provides more than enough throughput for your cable connection.
rdhw is offline   Reply With Quote