Something unknown keeps failing to connect to IP address 192.168.1.1

[NickStiven]

I keep getting a message saying 'The server at 192.168.1.1 is taking too long to respond'. Can anyone suggest a way to determine what program or activity is responsible, please?

Background:

I used to have a LinkSys router (which uses the IP address 192.168.1.1). A year ago I changed to a NetGear router (that uses 192.168.0.1). Then, last month, when my C: drive with Windows XP Pro started to fail, I cloned it to a new HDD. Everything works nicely - except that I now often get this annoying message. At the same time, Firefox (my default browser) opens a tiny, blank window at the top left of my screen. I'm not consciously trying to look at my old LinkSys router, but it would seem that something in my machine is. Maybe as a result of the cloning process some service has been re-activated from an old profile, who knows? Anyway, it would be great to be able to identify what's responsible and get it to cease and desist!

 

[mscallisto]

for starters can you go to a DOS window e.g.:
Start > Run then type cmd then hit OK

then type ipconfig /all then hit the enter key to see what address is assigned to your IP Address.

 

[NickStiven]

Thank you for the suggestion. Unfortunately, no mention of 192.168.1.1 there.

 

[xwb]

Workaround: You could add an alias to the host table - when it looks for 192.168.1.1 alias it to 192.168.0.1

 

[goombawaho]

Do a search in the registry for 192.168.1.1

change each instance to 0.1

(backup the whole registry first please)

 

[NickStiven]

Thank you, everybody, for your suggestions.

I tried adding an alias to the host table and it made no difference, so I deleted the new entry.

I had already searched the Registry - there was nothing there.

Then I decided to grasp the nettle - try msconfig, disable all start up entries, and see if that made a difference. It did. But which one? Turning each one on in turn and rebooting took for ever, but three coffees and two sudokus later, it turned out to be Firefox Preloader.

Great. Remove Firefox Preloader and adjust msconfig so we had a normal start up. What could possibly go wrong?

When I re-booted, I nearly had a heart attack - I couldn't get anything to work properly. It turned out that every service in the computer had been disabled. Luckily, I have a spare laptop and a quick trip to Google established that msconfig sometimes does this to you. Apparently.

After rebooting into Safe Mode and even more coffees (doesn't it just take forever?), I manually changed every service back to Automatic and started those I could. A final reboot and everything seems to be working properly again.

Oh - and the irritating message that started it all off has finally gone ... .

 

[mscallisto]

Glad you fixed your problem, now maybe skip the coffee and have a cold beer.

sam

 

[Diancecht]

Next time, maybe TcpView could help. This utility shows connections associated to processes

Cheers,
Dian