kendon
15-08-2004, 13:36
Started having intermittent issues from Friday on my main machine - losing connection, and getting a 169. IP. Called technical support who have arranged an engineer visit for Monday. If I disabled the connection in network connections and then re-enabled it this was resolving the problem, sometimes.
Decided today to hook up to the wife's machine with the cable modem, picked up an IP straight away and I'm typing this message on her machine now.
Tech support seemed to think there is a fault with the SACM, my typing this message seems to suggest that there is an issue somewhere on my machine rather than with the modem.
So, my question is, what would cause my machine to not resolve an IP address. Trying ipconfig /renew results in a "DHCP server could not be resolved. The process timed out". Obviously the DHCP can be found as the wife's machine picked up the IP within 20-30 seconds.
Thoughts? Suggestions?
The OS on both is WinXP Professional.
Decided today to hook up to the wife's machine with the cable modem, picked up an IP straight away and I'm typing this message on her machine now.
Tech support seemed to think there is a fault with the SACM, my typing this message seems to suggest that there is an issue somewhere on my machine rather than with the modem.
So, my question is, what would cause my machine to not resolve an IP address. Trying ipconfig /renew results in a "DHCP server could not be resolved. The process timed out". Obviously the DHCP can be found as the wife's machine picked up the IP within 20-30 seconds.
Thoughts? Suggestions?
The OS on both is WinXP Professional.