TCP/IP Stack broken by Home networking wizard on WinXP

  • Thread starter Thread starter Chris Sos
  • Start date Start date
C

Chris Sos

Howdy,

Trying to fix a corrupted TCP/IP stack on Win XP Pro.

I have already performed the steps mentioned in MS KB 817571 to remove the
Winsock entries in the registry and reset the TCP/IP stack using the "netsh
int ip reset logme.txt" command as detailed in KB 299357.

I'm a TechNet subscriber and tried querying for the error I get when I try
to join the domain from my XP Pro box. The error is "TCP/IP network
protocol not installed."

So, here's how I got there. I was trying to let my XP Pro machine share an
internet connection (ICS) with my Win 2003 Eval Server...

1 - I set the Win 2003 server to share its default dialup account. Worked
fine (set up DHCP scope to 192.168.0.x and gave the server a static
192.168.0.1). It dials up fine (did and still does) to the Internet.

2 - Ran the home networking setup wizard on my Windows XP Pro box. After
watching the animated home networking icon for 15+ minutes, I ended the task
thinking it locked up. Bad move. Ever since , I get the error message
above when I try to add the PC to the domain. Weird thing is that ping and
ipconfig still show everything as normal...EXCEPT that where in the ping
command it says "Pinging [hostname] [192.168.x.x], it has some funky ASCII
characters where normally it would have the host name. Same thing at the
end of the ping..."Ping statistics for [here is where the weird characters
would be]. The ping does report successful ping times though.

I'm REALLY frustrated with this and am appealing to the last pure source of
good information on the Internet...newsgroups.

Any ideas?

Supporting info:
Windows 2003 server on PII 500 / 256MB / 9 GB SCSI
Windows XP Pro SP-1 on AMD 1GHz / 512MB / 80GB
Network CAT5e into a 10 Mbit hub (temporarily)
TCP/IP on the server and XP Pro box was previously set to static 192.168.x.x
address.
 
1. Backup and delete the following registry keys

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

2. Reboot

3. Go to the network connections folder, right click the icon for your
network connection, and select properties.

4. Click install, choose "protocol", and click "add..."

5. Click "Have Disk...", enter "\windows\inf", click OK

6. Select "Internet Protocol (TCP/IP), click OK

7. When the process in complete, reboot
 
Ken,
I'll give it a shot and let you know. I thought you couldn't reinstall
TCP/IP on XP...we'll see!

Thanks for the quick response!

-Chris


[SNIP] - see prev. post
 
Chris,

this reminds me of a very old problem that occurred in Windows
NT 4.0. But try Ken's advice first, it seems to be a subset.

If you want to look at the old article, it is at
http://www.michna.com/kb/WnTcpNoInstall.htm. Most or all of the
registry keys may still be the same in Windows XP.

Hans-Georg


Chris Sos said:
Howdy,

Trying to fix a corrupted TCP/IP stack on Win XP Pro.

I have already performed the steps mentioned in MS KB 817571 to remove the
Winsock entries in the registry and reset the TCP/IP stack using the "netsh
int ip reset logme.txt" command as detailed in KB 299357.

I'm a TechNet subscriber and tried querying for the error I get when I try
to join the domain from my XP Pro box. The error is "TCP/IP network
protocol not installed."

So, here's how I got there. I was trying to let my XP Pro machine share an
internet connection (ICS) with my Win 2003 Eval Server...

1 - I set the Win 2003 server to share its default dialup account. Worked
fine (set up DHCP scope to 192.168.0.x and gave the server a static
192.168.0.1). It dials up fine (did and still does) to the Internet.

2 - Ran the home networking setup wizard on my Windows XP Pro box. After
watching the animated home networking icon for 15+ minutes, I ended the task
thinking it locked up. Bad move. Ever since , I get the error message
above when I try to add the PC to the domain. Weird thing is that ping and
ipconfig still show everything as normal...EXCEPT that where in the ping
command it says "Pinging [hostname] [192.168.x.x], it has some funky ASCII
characters where normally it would have the host name. Same thing at the
end of the ping..."Ping statistics for [here is where the weird characters
would be]. The ping does report successful ping times though.

I'm REALLY frustrated with this and am appealing to the last pure source of
good information on the Internet...newsgroups.

Any ideas?

Supporting info:
Windows 2003 server on PII 500 / 256MB / 9 GB SCSI
Windows XP Pro SP-1 on AMD 1GHz / 512MB / 80GB
Network CAT5e into a 10 Mbit hub (temporarily)
TCP/IP on the server and XP Pro box was previously set to static 192.168.x.x
address.
Click to expand...
 
I have also tried the steps in 817571. I have no idea how
the IP got corrupted, since this is not my computer. I'm
told it started with the installation of adaware. The
official fix does nothing.
 
1. Backup and delete the following registry keys

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

2. Reboot

3. Go to the network connections folder, right click the icon for your
network connection, and select properties.

4. Click install, choose "protocol", and click "add..."

5. Click "Have Disk...", enter "\windows\inf", click OK

6. Select "Internet Protocol (TCP/IP), click OK

7. When the process in complete, reboot


--

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


jims said:
I have also tried the steps in 817571. I have no idea how
the IP got corrupted, since this is not my computer. I'm
told it started with the installation of adaware. The
official fix does nothing.

-----Original Message-----
Howdy,

Trying to fix a corrupted TCP/IP stack on Win XP Pro.

I have already performed the steps mentioned in MS KB 817571 to remove the
Winsock entries in the registry and reset the TCP/IP stack using the "netsh
int ip reset logme.txt" command as detailed in KB 299357.

I'm a TechNet subscriber and tried querying for the error I get when I try
to join the domain from my XP Pro box. The error is "TCP/IP network
protocol not installed."

So, here's how I got there. I was trying to let my XP Pro machine share an
internet connection (ICS) with my Win 2003 Eval Server...

1 - I set the Win 2003 server to share its default dialup account. Worked
fine (set up DHCP scope to 192.168.0.x and gave the server a static
192.168.0.1). It dials up fine (did and still does) to the Internet.

2 - Ran the home networking setup wizard on my Windows XP Pro box. After
watching the animated home networking icon for 15+ minutes, I ended the task
thinking it locked up. Bad move. Ever since , I get the error message
above when I try to add the PC to the domain. Weird thing is that ping and
ipconfig still show everything as normal...EXCEPT that where in the ping
command it says "Pinging [hostname] [192.168.x.x], it has some funky ASCII
characters where normally it would have the host name. Same thing at the
end of the ping..."Ping statistics for [here is where the weird characters
would be]. The ping does report successful ping times though.

I'm REALLY frustrated with this and am appealing to the last pure source of
good information on the Internet...newsgroups.

Any ideas?

Supporting info:
Windows 2003 server on PII 500 / 256MB / 9 GB SCSI
Windows XP Pro SP-1 on AMD 1GHz / 512MB / 80GB
Network CAT5e into a 10 Mbit hub (temporarily)
TCP/IP on the server and XP Pro box was previously set to static 192.168.x.x
address.


.
Click to expand...
Click to expand...
 
Back
Top