[Darth_Tanion]

I fixed my brother's computer a while back using a command that I cannot remember. His computer was constantly coming up with "Limited or no connectivity" and no matter how many different NIC's I used (wired or wireless) I couldn't get an IP from my router. Eventually I tracked down a little helper on the net that told me to go to start->run and type in a command that I can no longer remember. This then brought up a list of programs that had something to do with my network. In this list was new.net. In some way new.net was different to the other entries (how it was different I also cannot remember.) Basically the fact that it was different meant that it had to be uninstalled and this solved my problem. My problem is that now I cannot remember what the command I typed in to the run dialog box was. It wasn't anything common like msconfig, regedit, services.msc or the like. If anyone can think of ANYTHING that might match this some what feeble description I would really appreciate it. Even if anyone knows of anywhere that I can find a list of windows commands that can be typed into the run dialog box and I will go through it one by one.

Thanks in advance,

Darth Tanion

[jocase]

Try http://www.microsoft.com/resources/d...loverview.mspx

Type command in the run line to get a DOS like window. Then use these commands.

Also, if you fixed it a short time ago, have your brother click the dropdown arrow in his run box and see what commands are there.

Another way... Type command in run box.
Type NET HELPMSG 3712

John

[Express1]

This is Limited no connectivity issue, 95% of the time its going to have to deal with Windows Service Pack 2. If you try to release/renew your IP and get a socket error, then you better scan your PC for viruses. You can also try to run this Dos command "netsh dump" and reboot your PC. This command will clear out all devices behind your cable modem. Meaning it will reset both your cable modem and router.

There is also a Windows patch that will also fix this issue "KB884020". Check micrososft.com. Also if you're running Zone Alarm firewall, it will also cause limited no connectivity. You can calso try reloaded the drivers for your NIC. More than likely with this Limited no connectivity you will be pulling a 169 IP address which means your NIC has no device behind it, whether it is a router or cable modem

[mindtab]

Sounds like you removed a service which had started with windows, and was messing up your connection.

Start>Run>cmd
Net start (shows running services)

Net stop [service name] stops a service