TCP/IP screwed

[Colin Walker]

My XP pro laptop is connected to a win2k network but
cannot pick up a DHCP address. I have followed knowledge
base article 817571 but still get the same issue when
trying to ipconfig /renew: "An operation was attempted on
something that is not a socket"

In NT4 or win2k we could reinstall IP. Anyone any ideas
what i should try now?

Cheers
colin

 

[Matthew Kaess]

I am assuming that you verified that TCP/IP is in fact
working. What is returned when you do an IPCONFIG /all
and ping the local host (127.0.0.1)? If the latter
returns a reply - TCP/IP is function on that adapter.
Given that - Is the DHCP client service running?

 

[Ken Wickes [MSFT]]

I have traced several of these problems to improperly configured winsock
LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and uninstalling the
owning program might help.

If that fails or your provider list is empty, you may need to rebuild the
catalog from scratch. The following instructions will rebuild your catalog
for TCP/IP. If you are using any other transports (If you don't know, then
you probably aren't) then you will have to reinstall them as well.


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

 

[colin walker]

Thanks,

I shall try this.

-----Original Message-----
I have traced several of these problems to improperly configured winsock
LSPs. Run "winmsd" and go to

Components/Network/Protocol. Look at the

names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and uninstalling the
owning program might help.

If that fails or your provider list is empty, you may need to rebuild the
catalog from scratch. The following instructions will rebuild your catalog
for TCP/IP. If you are using any other transports (If you don't know, then
you probably aren't) then you will have to reinstall them as well.


1. Backup and delete the following registry keys

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Wins ock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Wins

ock2

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.

I am assuming that you verified that TCP/IP is in fact
working. What is returned when you do an IPCONFIG /all
and ping the local host (127.0.0.1)? If the latter
returns a reply - TCP/IP is function on that adapter.
Given that - Is the DHCP client service running?

.

 

[colin walker]

Thanks for your reply Matthew, you assumed correctly and
the answer is yes on all counts. I will try another
solution suggested by MSFT.

Regards