Sockets not being established

[Sean McClanahan]

I am having a difficult problem with Windows 2000 Pro.

Current set-up is Win2K, SP3. Using a Linksys LNE100TX
NIC.

I had installed SP4, and everything was working fine.
Returning home from work two evenings ago, I could no
longer obtain an IP address via DHCP.

If I enter a static IP address, I can ping remote PCs with
no problem. However - I cannot open web pages, telnet,
ftp, or anything that requires something more than an ICMP
connection. Has nothing to do with DNS, because I can ping
my Linksys router, for example, but I cannot access the
web configuration page using the exact same IP address I
just pinged.

If I go back to DHCP, it will not get an address from the
DHCP server (also the Linksys router, FYI.) All other PCs
on the network obtain their addresses, release and renew,
can access the web configuration page via IP address...
IOW, everything else on the network is working A-OK. The
address I get on this PC with the problem when I try to
use DCHP is the stock 169.254.x.x address. I cannot
release that when I try to do so.

I cannot telnet into mail mail server when using a static
address - I am told that a connection could not be
opened. (As in, it doesn't even try to establish a socket
to port 25.)

I thought maybe I had a file corruption, so I uninstalled
SP4 and went back to SP3. Did not solve the problem.

I have changed the NIC. No luck. Uninstalled and re-
installed TCP/IP. No luck. Not running IPSec or any
other firewall program like ZA, Neowatch, or BID.

I am at a total loss as to what else to try. I appreciate
any assistance that anyone might be able to provide.

Sean

 

[Vikas Ramnani]

Are there any weird errors you notice in your eventvwr?

 

[Sean McClanahan]

Oh my, yes. (Totally forgot about the Event Viewer - mea
culpa...)

Where do I start?

From the last reboot:

I'm getting a DCOM error - ID 10010
A Background Intelligent Transfer Service error - ID 7024
A TCPIP error, event 4191 - says "Interfaces on this
adapter will not be initialized" because of an inability
to open the registry key NDISWANIP.

Sounds like potentially, the last one could be related to
my problem...?

Sean

 

[Sean McClanahan]

OK, I researched what the 4191 code was. KB suggested
uninstalling and re-installing TCP/IP, which I had done
before. Did it again - still no go. Now I'm getting a
DHCP error, event 1006 - WSAStartup cannot function at
this time.

grrrrrrr.....

Sean

 

[Sean McClanahan]

GOT IT!!!

Here's a fix I found elsewhere on the 'net:

1.Uninstall TCP/IP protocol.(DO NOT restart after
uninstalling!!)
2.Delete following regestry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSo
ck2
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSo
ck
3.Restart
4.Install TCP/IP protocol again.

But I can't contact the originator of that tidbit. Too
bad - I'd buy him a drink.

Vikas - THANK YOU for pointing me in the direction of the
Event Viewer. I had totally forgotten about that.

Sean

 

[Helper]

In an effort to help save others time, this is what fixed it for me.
I installed something that corrupted my TCP/IP stack, so after a day
of hassle, the following articles came to light.

Disable Automatic Private IP Addressing (stops the auto assign of the
169.254 network):
http://support.microsoft.com/default.aspx?scid=kb;EN-US;244268

Delete the Corrupted Registry Entries:
http://support.microsoft.com/default.aspx?scid=kb;en-us;817571

Good Luck