Why when i fix or format someones computer for them after my ethernet cable has been plugged into their pc then they take their pc back home and now their internet isnt working? I don't remember this being a problem a while back but i have fixed 3 pc's in past 2 weeks, all of these people had comcast cable, i fixed one and formatted the other two pc's. i have att uverse internet which shouldn't make a difference. i have no problem getting their pc's to connect at my house. Is the problem like the IP not getting released or something? they all had the same problem: no connectivity/limited. i had them power down modem for 3 minutes and computer, check auto detect settings in LAN settings, even run network and internet connect wizards again and finally throw in their comcast CD to reinstall comcasts software, none of this helped all 3 times. i just want to know why and what is happening here. I did some research today on this forum and is this what needs to bet done each time? Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog then reboot.

Usually a release and renew of the IP address will fix the connectivity problem. "So won’t you give this man his wings What a shame To have to beg you to see We’re not all the same What a shame" - Shinedown

so to release and renew you would: just power down modem & router for a couple of minutes then reboot? or Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog then reboot? or is there another way to release renew? thanks

None of the above. At a command prompt: ipconfig /release Then, ipconfig /renew This is pretty basic knowledge. I'm surprised that if you're working on computers for people that you don't already know this. "So won’t you give this man his wings What a shame To have to beg you to see We’re not all the same What a shame" - Shinedown

thanks for the reply, i had never run into this problem before, until just recently.