XP no longer talks to ADSL router

  • Thread starter Thread starter Neil Shadrach
  • Start date Start date
N

Neil Shadrach

Original set up ( was working for a week ):

Vigor 2600 ethernet router: default IP 192.168.1.1
Fixed IP address and ISP details set in router config.
Windows XP picking up IP address via DHCP from router (
typically 192.168.1.10 )

Two days ago the pc stopped talking to the router - no IP
address via DHCP so pc defaulted to a private address on a
different subnet. I set the IP address manually and I
could then 'ping' the router.
However I could not telnet to it, the router configuration
software cannot discover the router and the web
configuration option ( http://192.168.1.1/ ) no longer
works either. Borrowed another pc
yesterday and it connected first time no trouble so the
problem is clearly with mine.

I shutdown the firewall ( McAfee ) and checked that the XP
firewall ( ICF ) was not enabled. Running low on ideas.
I've been through most of the variations of
DHCP/manually setting addresses/automatic private
addresses with no luck.

The telnet failure message is as follows:

"Connecting to 192.168.1.1 ...
Could not open connection to the host, on port 23.
The requested service provider could not be loaded or
initialized"

I've looked this up as "10106 The requested service
provider could not be loaded or initialized.
WSAEPROVIDERFAILEDINIT"

Any thoughts?
 
Neil,

have you tried to communicate with anything else beside the
router? It could be that the entire Ethernet adapter or cable or
driver is down.

Can you ping the router, for example? If yes, can you ping any
other valid IP address? If no, can you ping anything else?

Once you have Ethernet going and IP working and still have
problems, please have a look at
http://www.michna.com/kb/WxNetwork.htm, but as long as the
low-level communications don't work, you have to work on these
first.

Hans-Georg
 
Hans-Georg,

Thanks for the prompt reply.
I can ping the router if I set the IP address of the pc
manually but I cannot telnet to it or access it via http (
it has a web interface ). I don't currently have any other
devices at home to try things out ( I borrowed a laptop
for a coiple of hours to check the router but didn't think
of trying direct pc to pc comms to check the ethernet card.

Regards

Neil Shadrach
 
Neil Shadrach said:
I can ping the router if I set the IP address of the pc
manually but I cannot telnet to it or access it via http (
it has a web interface ). I don't currently have any other
devices at home to try things out ( I borrowed a laptop
for a coiple of hours to check the router but didn't think
of trying direct pc to pc comms to check the ethernet card.
Click to expand...

Neil,

OK, if you can ping the router's IP address, then the Ethernet
and IP are working.

Could it perhaps be that everything works, as long as you enter
IP addresses, rather than host names? For example, the IP
address of one of Microsoft's servers is 213.161.82.43. Can you
ping that? Can you get to the page when you enter that IP
address in your Web browser?

When you don't get an IP address through DHCP, you also don't
get the DNS server addresses, so you cannot reach anything
outside your own network. You could enter a working DNS server
IP address into your computer's IP settings for a test, but
that's not the normal procedure.

So far we only guess that something in your computer hinders the
access or the processing of DHCP. Perhaps a service
malfunctioned and was stopped, perhaps your computer caught a
virus. Can't hurt to run a virus checker.

Next step is to check the system event log, particularly around
the dates when the error first occurred. You get to that in
control panel, administration, event logs.

You could also check http://www.michna.com/kb/WxNetwork.htm for
possible causes.

Hans-Georg
 
-----Original Message-----
card.

Neil,

OK, if you can ping the router's IP address, then the Ethernet
and IP are working.

Could it perhaps be that everything works, as long as you enter
IP addresses, rather than host names? For example, the IP
address of one of Microsoft's servers is 213.161.82.43. Can you
ping that? Can you get to the page when you enter that IP
address in your Web browser?

When you don't get an IP address through DHCP, you also don't
get the DNS server addresses, so you cannot reach anything
outside your own network. You could enter a working DNS server
IP address into your computer's IP settings for a test, but
that's not the normal procedure.

So far we only guess that something in your computer hinders the
access or the processing of DHCP. Perhaps a service
malfunctioned and was stopped, perhaps your computer caught a
virus. Can't hurt to run a virus checker.

Next step is to check the system event log, particularly around
the dates when the error first occurred. You get to that in
control panel, administration, event logs.

You could also check
Click to expand...
http://www.michna.com/kb/WxNetwork.htm for
possible causes.

Hans-Georg
Click to expand...

Hans-Georg,

I'm only using IP addresses in all my testing so as to
avoid name resolution issues at this stage.
I've run a full disk check with McAfee VirusScan .
I have looked at the logs but not noticed anything.
I think telnet is failing to run at all.
A colleague at the company where I work has pointed me at
Knowledge Base Article 817571 which he says sorted a
similar problem for him when his TCP/IP stopped working
after he removed a network bridge. I will check this out
tonight.

Thanks

Neil Shadrach
 
A colleague at the company where I work has pointed me at
Knowledge Base Article 817571 which he says sorted a
similar problem for him when his TCP/IP stopped working
after he removed a network bridge. I will check this out
tonight.
Click to expand...


I tried Method 1 of Knowledge Base Article 817571 since I
don't have a similar machine for reference.
( Essentially delete Winsock and Winsock2 entries from
registry nad run "netsh int ip reset resetlog.txt" to
reset TCP/IP )

Unfortunately it didn't work - though I now get a
different message when I try to run telnet:-
"The support for the specified socket type does not exist
in this address family"

I went back to the registry for a look - a Winsock2 entry
had been added but not a Winsock one.
Method 2 involves exporting Winsock and Winsock2 entries
for a "similar" machine but I don't have a spare.

I also removed a Network Bridge and it looks like this has
wrecked TCP/IP on the box.
So - any suggestions on how to repair this short of a full
rebuild which I really don't want to do?

Neil Shadrach
 
Neil Shadrach said:
I'm only using IP addresses in all my testing so as to
avoid name resolution issues at this stage.
I've run a full disk check with McAfee VirusScan .
I have looked at the logs but not noticed anything.
I think telnet is failing to run at all.
A colleague at the company where I work has pointed me at
Knowledge Base Article 817571 which he says sorted a
similar problem for him when his TCP/IP stopped working
after he removed a network bridge. I will check this out
tonight.
Click to expand...

Neil,

thanks for reporting. No new ideas from me at this time,
unfortunately.

Hans-Georg
 
Hans-Georg,

Tried uninstalling various things like Firewall and
VirusScan and reapplying 'fixes'. In the end I decided to
go for a full reinstall and within about an hour I had a
working system. Lots of software to reinstall but it's a
relief to have things working end-to-end again.

Thanks for the support!

Regards

Neil Shadrach
 
Tried uninstalling various things like Firewall and
VirusScan and reapplying 'fixes'. In the end I decided to
go for a full reinstall and within about an hour I had a
working system. Lots of software to reinstall but it's a
relief to have things working end-to-end again.
Click to expand...

Neil,

glad you made it. I would have liked to know what it was, but
sometimes we can't find out, so it gets archived in the
unexplained phenomena box. :-)

Maybe unmanageable complexity is the key word.

Hans-Georg
 
Back
Top