Quote:
|
Originally Posted by SuperHans
You are quite correct Just. Repairing the LAN connection will attempt to renew an IP address from the DHCP server. However you cannot get any information from that. If it cant renew a valid IP address it will just say that it cant repair the connection. But if the connection shows a PC generated IP address of 169.... and I renew from the command line I could get an error saying "An operation was attempted on something that is not a socket". That immediately tells me it is a WINSOCK error which is a PC related issue. Windows XP, use system restore and that will solve the problem. 3 minutes troubleshooting and a happy customer 
|
Bang on the money also not all customers are of the apparently high caliber that post here so for another example if the ip wont release from a 169 then that shows poss driver issues etc. Also the ip may just stay as 0.0.0.0 which highlights a poss issue with the DHCP client which I have experienced many a time.
Standard diags are there to help not only clear a problem to also give IMHO a degree of education to the person on the other end where and why the problem is.
also in response to ignition I have many a time sent a hit to the modem and rebooted to find the status/cable light is on and the connection restored so the point about booking a service call without even trying that is a bit moot considering the time a customer would take to reboot the cm
against waiting for a tech.