XP & ME--- ICS problems

  • Thread starter Thread starter harvey roman
  • Start date Start date
H

harvey roman

I have had my 2 computers networked for almost 2 years with
no problems until now. Recently my client Computer(ME) lost
thr residential gateway connection with the host
computer(XP). I still have them networked and I can use the
internet on the XP. After trying several methods to get
the Internet working on the client(ME) and failing on all
attempts, I decided to re-use the Network Setup Wizard that
comes with XP. I intalled the floppy into the ME computer
to setup the ICS connection. Everything appeared ok until I
retarted the computer (ME). I get the following error
messages: An error occured loading
C:\windows\system\upnp.dll has not been installed or
corrupted. When I hit ok I get the next error message:
error loading C:\window\system\hnetwiz.dll a routine
initialization failed. Needless to say I still can't get
on to the net with my client(ME). I use a dial up
connection and D-link to network my computers.
Also on my client, if I use the RUN command and type in
"winipcfg" i get the following error: Failed to initialize
WINSOCK.
Thanks for any help that you can supply
...
 
I think the IP stack is fine. First is \windows\system\upnp.dll really
missing? Does running the Network Setup Wizard add it?
 
Easy enough to verify. First, try to ping 127.0.0.1 and
see if there is a response. If that does not work, the IP
stack has serious problems. If it does work try to ping
the IP of your machine (ex. 192.168.02) and see if there
is a problem there. Next ping the machine that you are
trying to connect to.

If those are working fine, I would try to manually
configure the IP info for the machine. Check the IP info
for the host machine. Get its IP address and netmask. On
the client machine, pick an IP address where only the last
number is changed, set the subnet the same and put the IP
address of the host as the gateway. For DNS servers you
should just be able to put in whatever DNS servers you
normally use or the host machine IP, and it should forward
DNS queries.

I am not intimately familiar with the interdependencies of
the DLL system and it may infact be possible for ipconfig
to rely implicitly on universal plug and play and the home
networking wizard, but somehow I doubt it.

Sean Davis
-----Original Message-----
I think the IP stack is fine. First is
Click to expand...
\windows\system\upnp.dll really
missing? Does running the Network Setup Wizard add it?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


It sounds like the IP stack on the windows ME machine is
corrupted. First I would go and remove tcp/ip from all
the network configurations and reboot the machine. After
that, reinstall tcp/ip on the connections and reboot.
Unfortunately, this does not work very often, but
sometimes it will rebuild the corrupted files...

That failing, either go and try to restore to a previous
restore point (again, doesn't work all the time) or, the
more guaranteed answer, try to do a repair of the system
from the CD (over the top install basically with ME, 2000
and XP will actually just replace damaged files).
until
I
Click to expand...


.
Click to expand...
 
I should have read all the way to the bottom, it seems like there are
multiple problems.

Can you also post the results of typing "ipconfig /renew_all" at a command
line?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


Sean Davis said:
Easy enough to verify. First, try to ping 127.0.0.1 and
see if there is a response. If that does not work, the IP
stack has serious problems. If it does work try to ping
the IP of your machine (ex. 192.168.02) and see if there
is a problem there. Next ping the machine that you are
trying to connect to.

If those are working fine, I would try to manually
configure the IP info for the machine. Check the IP info
for the host machine. Get its IP address and netmask. On
the client machine, pick an IP address where only the last
number is changed, set the subnet the same and put the IP
address of the host as the gateway. For DNS servers you
should just be able to put in whatever DNS servers you
normally use or the host machine IP, and it should forward
DNS queries.

I am not intimately familiar with the interdependencies of
the DLL system and it may infact be possible for ipconfig
to rely implicitly on universal plug and play and the home
networking wizard, but somehow I doubt it.

Sean Davis
-----Original Message-----
I think the IP stack is fine. First is
Click to expand...
\windows\system\upnp.dll really
missing? Does running the Network Setup Wizard add it?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


It sounds like the IP stack on the windows ME machine is
corrupted. First I would go and remove tcp/ip from all
the network configurations and reboot the machine. After
that, reinstall tcp/ip on the connections and reboot.
Unfortunately, this does not work very often, but
sometimes it will rebuild the corrupted files...

That failing, either go and try to restore to a previous
restore point (again, doesn't work all the time) or, the
more guaranteed answer, try to do a repair of the system
from the CD (over the top install basically with ME, 2000
and XP will actually just replace damaged files).

-----Original Message-----
I have had my 2 computers networked for almost 2 years
with
no problems until now. Recently my client Computer(ME)
lost
thr residential gateway connection with the host
computer(XP). I still have them networked and I can use
the
internet on the XP. After trying several methods to get
the Internet working on the client(ME) and failing on all
attempts, I decided to re-use the Network Setup Wizard
that
comes with XP. I intalled the floppy into the ME computer
to setup the ICS connection. Everything appeared ok until
I
retarted the computer (ME). I get the following error
messages: An error occured loading
C:\windows\system\upnp.dll has not been installed or
corrupted. When I hit ok I get the next error message:
error loading C:\window\system\hnetwiz.dll a routine
initialization failed. Needless to say I still can't get
on to the net with my client(ME). I use a dial up
connection and D-link to network my computers.
Also on my client, if I use the RUN command and type in
"winipcfg" i get the following error: Failed to initialize
WINSOCK.
Thanks for any help that you can supply
...
.
Click to expand...


.
Click to expand...
Click to expand...
 
Guys,
Thanks for the tips . Here are my initial results:
When I try to ping my clent I get the following error
message:Unable to initialize windows sockets interface.
error code 0.
when I try to run: ipconfig/renew_all i get a not found
message. Also my client won't let me restore to a time
before my problems began. I will continue to perform the
other suggests you guys have supplied. Thanks. I will advise.
-----Original Message-----
I should have read all the way to the bottom, it seems like there are
multiple problems.

Can you also post the results of typing "ipconfig /renew_all" at a command
line?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


Sean Davis said:
Easy enough to verify. First, try to ping 127.0.0.1 and
see if there is a response. If that does not work, the IP
stack has serious problems. If it does work try to ping
the IP of your machine (ex. 192.168.02) and see if there
is a problem there. Next ping the machine that you are
trying to connect to.

If those are working fine, I would try to manually
configure the IP info for the machine. Check the IP info
for the host machine. Get its IP address and netmask. On
the client machine, pick an IP address where only the last
number is changed, set the subnet the same and put the IP
address of the host as the gateway. For DNS servers you
should just be able to put in whatever DNS servers you
normally use or the host machine IP, and it should forward
DNS queries.

I am not intimately familiar with the interdependencies of
the DLL system and it may infact be possible for ipconfig
to rely implicitly on universal plug and play and the home
networking wizard, but somehow I doubt it.

Sean Davis
-----Original Message-----
I think the IP stack is fine. First is
Click to expand...
\windows\system\upnp.dll really
missing? Does running the Network Setup Wizard add it?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


It sounds like the IP stack on the windows ME machine is
corrupted. First I would go and remove tcp/ip from all
the network configurations and reboot the machine. After
that, reinstall tcp/ip on the connections and reboot.
Unfortunately, this does not work very often, but
sometimes it will rebuild the corrupted files...

That failing, either go and try to restore to a previous
restore point (again, doesn't work all the time) or, the
more guaranteed answer, try to do a repair of the system
from the CD (over the top install basically with ME, 2000
and XP will actually just replace damaged files).

-----Original Message-----
I have had my 2 computers networked for almost 2 years
with
no problems until now. Recently my client Computer(ME)
lost
thr residential gateway connection with the host
computer(XP). I still have them networked and I can use
the
internet on the XP. After trying several methods to get
the Internet working on the client(ME) and failing on all
attempts, I decided to re-use the Network Setup Wizard
that
comes with XP. I intalled the floppy into the ME computer
to setup the ICS connection. Everything appeared ok until
I
retarted the computer (ME). I get the following error
messages: An error occured loading
C:\windows\system\upnp.dll has not been installed or
corrupted. When I hit ok I get the next error message:
error loading C:\window\system\hnetwiz.dll a routine
initialization failed. Needless to say I still can't get
on to the net with my client(ME). I use a dial up
connection and D-link to network my computers.
Also on my client, if I use the RUN command and type in
"winipcfg" i get the following error: Failed to initialize
WINSOCK.
Thanks for any help that you can supply
...
.



.
Click to expand...
Click to expand...


.
Click to expand...
 
Back
Top