Winsock Error?

[Guest]

I have a WinXP home machine with a linksys 802.llg wireless card that I am
attempting to connect to my network. Each time I attempt to connect, the
adapter fails to obtain an IP address, but if I manually set the ip config
info, the system connects just fine.

Running ipconfig /renew returns "an operation was attempted on something
that is not a socket". I found numerous KB articles pertainin to this and
followed the instructions for resolution, all to no avail. After taking the
recommended steps, I still receive the same message when running ipconfig
/renew.

The wiers thing is, the adapter does pick up the DNS server, domain, and
other info from the DHCP server, it just will not take the IP address info.

The system has Symanted AV 2004, and The comcast security center installed.
I have ran numerous scans for spy ware and the like with no results or
successful cleaning of anything that was detected.

Other similar systems have no trouble receiving their IP address at all.

Thanks in advance for any suggestions.

 

[Guest]

here is the link that wsa sent to me the other day. i had the same problem
after installing XP home with SP2. this fixed it and cthe computer now runs
flawlessly.

http://support.microsoft.com/?id=811259

 

[Hans-Georg Michna]

I have a WinXP home machine with a linksys 802.llg wireless card that I am
attempting to connect to my network. Each time I attempt to connect, the
adapter fails to obtain an IP address, but if I manually set the ip config
info, the system connects just fine.

Running ipconfig /renew returns "an operation was attempted on something
that is not a socket". I found numerous KB articles pertainin to this and
followed the instructions for resolution, all to no avail. After taking the
recommended steps, I still receive the same message when running ipconfig
/renew.

The wiers thing is, the adapter does pick up the DNS server, domain, and
other info from the DHCP server, it just will not take the IP address info.

The system has Symanted AV 2004, and The comcast security center installed.
I have ran numerous scans for spy ware and the like with no results or
successful cleaning of anything that was detected.

Other similar systems have no trouble receiving their IP address at all.

Please use http://www.michna.com/kb/wxnet.htm to solve this
problem.

Hans-Georg

 

[Guest]

Thanks Tom,

That KB article is one that I had found and followed instructions from. The
items listed under protocol are nonexistent and do not appear after follwoing
the instructions for resolving the issue.

<Sigh>

 

[Guest]

Thanks, That helped....some.

I have this to add.

I installed a wired NIC and expereince the EXACT same behavior. Statick IP
all is good, cannot get IP via DHCP. One other thing of interest. My DHCP
server IS handing this system an IP address!! I saw 2 entries for this
machine in my DHCP server lease table. I deleted them and they immediately
appeared the next time I rebooted the system, so the problem is definitely
software related, but where? I can even ping the addresses asigned and
receive returns, yet on the system itself, it indicates IP 0.0.0.0 for each
NIC.

Any other suggestions?

 

[Guest]

Found the Problem!!

The DHCP server was not checking for existing static addresses, thus causing
and IP address conflict.

Thanks for all the help!