B
Brian
Windows XP Pro running on my notebook PC that I use to
support multiple networks has lost its Winsock
configuration several times, and it seems to be associated
with points in time at which I lost network connectivity
in at least a couple of different situations:
1. I had an static IP conflict with another device on the
same (wired) network.
2. The SSID on a wireless access point was changed while I
was connected to it via wireless using the original SSID.
Wireless connectivity was restored with a simple
connection to the new SSID, but DNS function was greatly
impaired,and eventually DHCP was lost permanently (until I
did a System Restore).
These are the only two I can pin down, because
the "solution" I have thus far is painful enough that I
really don't care to try to duplicate the problem any more
than I already have, inadvertently.
Each time, the "remove & reinstall Winsock" option
provided in the knowledgebase article #817571 was not very
appealing, and I fell back on a System Restore.
The principle symptoms are two: loss of DNS & DHCP client
function (which, of course, affect EVERYTHING else).
1. Even before reboot, I lose some DNS functionality. Ping
acts strangely; it allows me to ping by IP address, but
reports that it is pinging ">" (except that this character
is filled in) instead of the IP address. "Ping statistics
for..." returns odd characters in place of IP address
also. The reply itself shows the correct IP address.
Pinging a hosts file entry resolves to the same character
but succeeds. Pinging by DNS host name works only as long
as there is no "." (i.e. only to host names on LAN; all
other fail with "Ping request could not find host
XXX.XXX.com, etc.)
2. After reboot, DHCP client request results in
message, "An operation was attempted on something that was
not a socket." Change to static IP returns some LAN IP
functions, but DNS remains lost.
Reconfiguration from static IP to dynamic or vice versa
seems irrelevant. This affected all network adapters, so
it is more basic than the NIC driver.
Any ideas on why this might happen, how to prevent it, and
a better fix than the Winsock install/uninstall or System
Restore?
Thanks.
support multiple networks has lost its Winsock
configuration several times, and it seems to be associated
with points in time at which I lost network connectivity
in at least a couple of different situations:
1. I had an static IP conflict with another device on the
same (wired) network.
2. The SSID on a wireless access point was changed while I
was connected to it via wireless using the original SSID.
Wireless connectivity was restored with a simple
connection to the new SSID, but DNS function was greatly
impaired,and eventually DHCP was lost permanently (until I
did a System Restore).
These are the only two I can pin down, because
the "solution" I have thus far is painful enough that I
really don't care to try to duplicate the problem any more
than I already have, inadvertently.
Each time, the "remove & reinstall Winsock" option
provided in the knowledgebase article #817571 was not very
appealing, and I fell back on a System Restore.
The principle symptoms are two: loss of DNS & DHCP client
function (which, of course, affect EVERYTHING else).
1. Even before reboot, I lose some DNS functionality. Ping
acts strangely; it allows me to ping by IP address, but
reports that it is pinging ">" (except that this character
is filled in) instead of the IP address. "Ping statistics
for..." returns odd characters in place of IP address
also. The reply itself shows the correct IP address.
Pinging a hosts file entry resolves to the same character
but succeeds. Pinging by DNS host name works only as long
as there is no "." (i.e. only to host names on LAN; all
other fail with "Ping request could not find host
XXX.XXX.com, etc.)
2. After reboot, DHCP client request results in
message, "An operation was attempted on something that was
not a socket." Change to static IP returns some LAN IP
functions, but DNS remains lost.
Reconfiguration from static IP to dynamic or vice versa
seems irrelevant. This affected all network adapters, so
it is more basic than the NIC driver.
Any ideas on why this might happen, how to prevent it, and
a better fix than the Winsock install/uninstall or System
Restore?
Thanks.