View Full Version : Lost IP address -
Windows XP - several years old - was getting a little slower the past few weeks. So I ran REG CURE registry cleaner. Told it to fix the problems it found... and now My computer doesn't know who it is anymore !!!
I cannot system restore back to ANY date.
Cannot connect to the internet (comcast cable) or local (home) network -- at all. No other computer can see this one anymore.
IP Address is 0.0.0.0. - so is Subnet Mask & Default Gateway.
I've tried Start/Run/ipconfig/release, it says already released.
Start/Run/ipconfig/renew says "RPC server not available".
I've reinstalled drivers for the network Interface Card. No help.
(Intel® PRO/1000 MT Desktop Adapter - [PRO2KXP_v13_3.exe])
I apparently don't know the right terms to search for... not finding the answer on the web... or is it that hard to fix such a problem?
It's starting to look like I wil have to do a complete re-install of Windows... and all software --- ACCKKK! I don't want to have to go through that! !!!
Can someone here help me...???
What I need, is to give this computer a new IP address or make it find the old one... and restore the network inerface card registry entries. Can that be done?
Everything else seems to be working -- just NIC is totally wacked.
thanks -
YvetteKuhns
12-8-08, 04:29 PM
First, at the command prompt type ipconfig /flushdns. This will purge the dns cache, then type ipconfig /registerdns. This will refresh your DHCP lease and re-register any DNS names.
After trying the ipconfig /registerdns command, wait for about 15 minutes, then check your status and see it your issue is resolved.
If not, try reinstalling your NIC drivers.
Have you run this registry cleaner before? If so, did you save the last version BEFORE you ran it and messed up your computer? You may be able to restore your computer to the last saved version.
Were you running Zone Alarm or another firewall or antivirus program while the registry cleaner software was running? You probably need to disable those programs when running the registry cleaner program.
You did say the ip address was wrong, so it isn't the networking workgroup configuration that is causing the problem. You aren't able to see the computer in the network but the network info appears to be correct, is that right?
No need to re-install just yet!
You have a home network - is it peer-to-peer or is their a local server hanging around?
My guess would be peer-to-peer.
Most home networks have IP addresses either:
1) IP addresses assigned to them, probably via the router
2) have an IP address manually set. Many are set in the 'private' range of 192.168.0.1 to 192.168.0.255 although could be from a few others.
Have you another machine on the 'home network'? If so, try and find out that one's IP address to help decide what number to manually assign it (if that is the route to go)
Make sure your computers are in the same workgroup, this can be messed up easily. That should then get your computers talking to each other.
Got a spare NIC? Or try reseating the existing one.
If it says RPC server unavailable when you're trying to renew your ip, that implies there's something wrong with the machine Remote Procedure Call (RPC). Is the service running? Go to start | run and type services.msc. Make sure the Remote Procedure Call (RPC) service is running. The Locator should be set to manual and probably won't be running, no big deal. Also check the Network Connections service (it should be started) and the Plug and Play service.
Also check the control panel. Open network connections. Is your NIC listed in here? Is anything listed in here? If nothing's listed, your entire networking stack is broken. If all those services are running and it's still not working things get a lot more complicated. It looks like your cleaner was a bit too effective.
Thank You everyone
for the replies!
Sorry I am a bit slow in answering - but my normal internet world is messed up.... a bit awkard using this secondary machine...
I have tried everything each one of you suggested....the only thing I didn't try yet was pulling the box out and opening it up and trying Doc C's suggestion of reseating the NIC.
Here is the progress I've made. I now have the local network working - but still no internet. There are 3 PC's on my home (peer-to-peer, wired router) network and they now see each other.
IanS, I follwed your advice and I manually entered the ip address on the problem machine. I saw what the other 2 machines IP addresses were 192.168.1.101 and 102. So I first made the problem machine the same number but ending with 100. That didn't seem to work - and in fact gave me a new error message on startup about a "IP address conflict on the home network". Then I changed it to 103 and that seems to have helped.
Satis - I have made sure the Remote Procedure Call (RPC) service is running...it appears to be - at least it says it is in services.msc. However I still get messages that say RPC server is unavailable.
For example when I use YvetteKuhns suggestion - ipconfig/flushdns works but ipconfig /registerdns returns a message that "RPC server not available".
So there is still something messed up here... any additional ideas ?
Thanks again - you guys are great !
Now that the machine has an IP address (and you know ...100 conflicts with one on the network) try setting the gateway for the internet to the .... 100 address. This is probably the router's IP address.
Another clue... I just noticed that in services.msc ---- my "DHCP Client' entry is listed as "starting". Not started or paused, but starting... looks like it cannot get started.
Try and stop it then restart it manually.
If that works, try setting it to automatic again.
Now that the machine has an IP address (and you know ...100 conflicts with one on the network) try setting the gateway for the internet to the .... 100 address. This is probably the router's IP address.
The Default Gateway is set to 192.168.1.1, which is the same as the other 2 machines that are still working properly. So, this one should be the same as the other two, right?
Try and stop it then restart it manually.
If that works, try setting it to automatic again.
Can't stop or restart, all four buttons Start-Stop-Pause-Resume are all ghosted out --- as it appears it thinks it is in the process of starting...
Under Startup Type, I could disable it but that appears my only option.
tpoynton
12-9-08, 12:22 PM
If the reg cleaning program made a backup of your registry, you might try reverting to the backup copy...then trying a cleaner that is perhaps a little less aggressive if the networking starts working again.
Can't stop or restart, all four buttons Start-Stop-Pause-Resume are all ghosted out --- as it appears it thinks it is in the process of starting...
Under Startup Type, I could disable it but that appears my only option.Try setting it to manual first (get as many settings as you can written down first) then restart the computer. That should mean it starts with the service off. You may then be able to manually start the service. If that works, reset the Startup type to automatic and restart your computer again.
YvetteKuhns
12-9-08, 04:25 PM
For example when I use YvetteKuhns suggestion - ipconfig/flushdns works but ipconfig /registerdns returns a message that "RPC server not available".
If it says RPC server unavailable when you're trying to renew your ip, that implies there's something wrong with the machine Remote Procedure Call (RPC). Is the service running? Go to start | run and type services.msc. Make sure the Remote Procedure Call (RPC) service is running. The Locator should be set to manual and probably won't be running, no big deal. Also check the Network Connections service (it should be started) and the Plug and Play service.
It sounds like satis has seen this problem before. ;)
I deal with crazier stuff on a daily basis, believe it or not. With DHCP client stuck in starting, that's probably a good indication of the issue. Something that it's attempting to start isn't working so the service hangs. I'd try what Ian says and set it to manual, then restart... if it gets stuck in starting again there's something wrong with the service or one of its dependencies (I'm gunning for the dependencies).
Still, you can get on the network at this point? That's good news and more than I would've guessed. Setting the default gateway to your router SHOULD work... I'm not sure why it wouldn't unless the router has a problem handing out NATing to IP addresses it didn't assign itself. No idea... that shouldn't be the case but you never know.
Personally, I'd just back up my important stuff to another machine on the network and wipe the drive/reinstall windows. I can get a clean copy of Windows with basic apps set up in 2-3 hours... I think it'd be faster than where you're going. :)
Last suggestion before the one satis suggests - If all else has failed.... Can you log onto the router to check settings on that? It could be that there are restrictions on the range of IP addresses for automatic/manual assignment in the setup there.
It doesn't explain why things have failed however.
Personally, I'd just back up my important stuff to another machine on the network and wipe the drive/reinstall windows. I can get a clean copy of Windows with basic apps set up in 2-3 hours... I think it'd be faster than where you're going. :)
I wanted to give a final reply here to Thank all of you for your help. I think it could have been tracked down and fixed eventually, just would of taken a who knows how long.
In the end, as Satis's said, it became obvious it was easier to just reinstall the OS. That's what I did!
vBulletin v3.6.0, Copyright ©2000-2009, Jelsoft Enterprises Ltd.