M
marty
I forgot to add that this machine has AOL installed on it -
don't know if it's a factor.
don't know if it's a factor.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
K
Ken Wickes [MSFT]
You don't mention doing steps #3 - #7, have you?
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
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
M
marty
Ken, you are absolutely, totally "the man"! This worked!
Did I miss these steps in a KB somewhere? And what did I
just do - a repair install of TCP/IP? I had read that
the "netsh int ip reset.." command was the way to reset
TCP/IP since it couldn't be uninstalled and re-installed.
Regardless, my hat is off to you. If I was there I'd by
you a beer or 2.
Cheers, my friend!
Did I miss these steps in a KB somewhere? And what did I
just do - a repair install of TCP/IP? I had read that
the "netsh int ip reset.." command was the way to reset
TCP/IP since it couldn't be uninstalled and re-installed.
Regardless, my hat is off to you. If I was there I'd by
you a beer or 2.
Cheers, my friend!
-----Original Message-----
You don't mention doing steps #3 - #7, have you?
1. Backup and delete the following registry keys
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso ckck2HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso
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.
marty said:I forgot to add that this machine has AOL installed on it -
don't know if it's a factor.
.
K
Ken Wickes [MSFT]
Unfortunately these are not in a KB yet. I have suggested to the TCP/IP
team that they review the steps and publish them, but things move slowly
sometimes.
--
Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
team that they review the steps and publish them, but things move slowly
sometimes.
--
Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
marty said:Ken, you are absolutely, totally "the man"! This worked!
Did I miss these steps in a KB somewhere? And what did I
just do - a repair install of TCP/IP? I had read that
the "netsh int ip reset.." command was the way to reset
TCP/IP since it couldn't be uninstalled and re-installed.
Regardless, my hat is off to you. If I was there I'd by
you a beer or 2.
Cheers, my friend!
-----Original Message-----
You don't mention doing steps #3 - #7, have you?
1. Backup and delete the following registry keys
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso ckck2HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso
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.
marty said:I forgot to add that this machine has AOL installed on it -
don't know if it's a factor.
-----Original Message-----
I have seen similar posts on this newsgroup after doing a
search but have yet to see any new suggestions.
Scenario: For the general health of the computer I ran
windows update on a laptop running XP Pro, ran chkdsk,
ran
defrag, ran disk cleanup, and ran Ad-Aware to clean-up
adware/spyware.
The next day the user of that laptop could not connect to
shares on the network. After finding out it was using an
automatic private IP address, I tried "ipconfig /renew".
It returned message "An operation was attempted on
something that is not a socket."
I did everything that was suggested by postings here or
by
KB articles:
1. Run winmsd, look at components/network/protocol and
nothing was there.
2. deleted the winsock and winsock2 reg keys
3. Rebooted
4. ran "netsh int ip reset resetlog.txt to reset TCP/IP
since you can't uninstall it on XP Pro
5. Rebooted
6. Tried "ipconfig /renew" again - failed.
7. After finding an article saying that McAfee Personal
Firewall might have been uninstalled improperly, I
reinstalled it and then uninstalled it using the McAfee
uninstall tool. (I don't know when this was ever
installed, but it came with the laptop so I thought
someone might have installed it at one point).
8. Rebooted.
9. Tried to renew again - failed.
In my heart of hearts I know that the problem was caused
by some combination of the Windows Updates I downloaded
and installed. I updated every machine in our network
because of the recent worm threats and this is the 3rd
machine that has encountered a problem as a result of
that
process.
But that doesn't matter. I just want to get it fixed
without reinstalling Windows.
Any help would be appreciated...Thanks!
.
.