Did it ever happen to 1 of you that your cablemodem suddenly stopped working while you were connected the .net?
Mine decided to act that way.......un-and reinstalling TCP/IP protocol or network card didn't help....releasing and renewing IP didn't work,winblows 2k and XP both refused it,leaving me with that bad 169.x.x.x IP.......unplugging the cablemodem for a few hours or resetting the d*mn thing didn't work,nor did changing the connection cable.
No ISP probs,no DNS probs......so I thought the modem died on me......,in a desperate attempt to get my connection back,I plugged out everything and connected my laptop to the cablemodem.
Surprise 1 :I could release and renew my IP
Surprise 2 :My cablemodem woke up
My question:
Why????
I mean,I followed standard procedure to wake up a suspended connection,but the ipconfig commands didn't work on my main machine....on my laptop they did......program setup is almost identical....
Mine decided to act that way.......un-and reinstalling TCP/IP protocol or network card didn't help....releasing and renewing IP didn't work,winblows 2k and XP both refused it,leaving me with that bad 169.x.x.x IP.......unplugging the cablemodem for a few hours or resetting the d*mn thing didn't work,nor did changing the connection cable.
No ISP probs,no DNS probs......so I thought the modem died on me......,in a desperate attempt to get my connection back,I plugged out everything and connected my laptop to the cablemodem.
Surprise 1 :I could release and renew my IP
Surprise 2 :My cablemodem woke up
My question:
Why????
I mean,I followed standard procedure to wake up a suspended connection,but the ipconfig commands didn't work on my main machine....on my laptop they did......program setup is almost identical....