R
Robb Pierce
I tried the below and still having issues on 1 other
computer, still gets 169 addy. I have replaced the
cable, moved to a new port in the switch that was working
for another computer, tried another netowrk card and also
performed the following, still gets 169 addy. This is a
problem that happens, then all of the sudden starts
working again, next week, does the same thing. Its been
up for over a week now, but quite frequently will just
loose it's IP and obtain one when it feels like it, maybe
a day later. Please Help, thanx.
-------------------
Go here:
Microsoft Knowledge Base Article - 817571
http://support.microsoft.com/default.aspx?scid=kb;en-
us;817571&Product=winxp
-------------------
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.
NOTE: You may want to print out these instructions or
save them to your
hard disk before starting.
1. Backup and delete the following registry keys
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso
ck
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso
ck2
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.
--------------------
computer, still gets 169 addy. I have replaced the
cable, moved to a new port in the switch that was working
for another computer, tried another netowrk card and also
performed the following, still gets 169 addy. This is a
problem that happens, then all of the sudden starts
working again, next week, does the same thing. Its been
up for over a week now, but quite frequently will just
loose it's IP and obtain one when it feels like it, maybe
a day later. Please Help, thanx.
-------------------
Go here:
Microsoft Knowledge Base Article - 817571
http://support.microsoft.com/default.aspx?scid=kb;en-
us;817571&Product=winxp
-------------------
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.
NOTE: You may want to print out these instructions or
save them to your
hard disk before starting.
1. Backup and delete the following registry keys
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso
ck
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winso
ck2
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.
--------------------