tcp/ip mostly quit working

[Chris Richmond - MD6-FDC ~]

Hi,
I have a w2k pro workstation where most of the networking stuff
quit working. Its been running just fine for months, then quit.
Its in my son's room, and I don't think he messed with anything.
Anyway, its set up with a static address, I'm using a linux router
for DNS and gateway. There are other PC's that are working fine.

What works: ping internal nodes by IP address, network neighborhood
(I can browse peer systems), ping this host from the peers.

What's broken: ping by name, telnet interal nodes by IP address,
name resolution, anything over the internet, etc.

What I've tried: verifying all the tcp/ip properties, attepmting
DHCP (didn't get an address), uninstall reinstall tcp/ip, reboots,
etc.

What I don't want to do: reinstall from scratch!

What is this and what else can I try?

Thx, Chris

 

[Steven L Umbach]

Try entering an IP address in IE address bar such as 207.47.250.119 [Microsoft
website] to see if that works which if it does would indicate a dns problem. Tracert
can also be used to troubleshoot and will show where a bottleneck is in a routed
path. Often repairing winsock will solve the problem. See the link below for
hat. --- Steve

http://www.cexx.org/lspfix.htm --- LSP-fix

 

[Chris Richmond - MD6-FDC ~]

Try entering an IP address in IE address bar such as 207.47.250.119 [Microsoft
website] to see if that works which if it does would indicate a dns problem.

I didn't try this specifically, but I know it won't work. DNS (name
resolution) is certainly broken, but its more than that, because I
can't telnet by IP address to other local hosts. I tried a different
ethernet card, and that didn't make any difference.

Tracert can also be used to troubleshoot and will show where a bottleneck is in a routed
path.

tracetr works on the local net. I'm assuming it will work to the
internet since it uses ping (ICMP) and not UDP or TCP.

Often repairing winsock will solve the problem. See the link below for
hat. --- Steve

http://www.cexx.org/lspfix.htm --- LSP-fix

I'll try this later. Does Win2k still use winsock?

Th+ 70718 Re: tcp/ip mostly quit working [37] Steven L Umbach x, Chris

 

[Microsoft Support Desk]

get rid of linux - use microsoft products only

-----Original Message-----

Try entering an IP address in IE address bar such as 207.47.250.119 [Microsoft
website] to see if that works which if it does would

indicate a dns problem.

I didn't try this specifically, but I know it won't work. DNS (name
resolution) is certainly broken, but its more than that, because I
can't telnet by IP address to other local hosts. I tried a different
ethernet card, and that didn't make any difference.

Tracert can also be used to troubleshoot and will show where a bottleneck is in a routed
path.

tracetr works on the local net. I'm assuming it will work to the
internet since it uses ping (ICMP) and not UDP or TCP.

Often repairing winsock will solve the problem. See the link below for
hat. --- Steve

http://www.cexx.org/lspfix.htm --- LSP-fix

I'll try this later. Does Win2k still use winsock?

Th+ 70718 Re: tcp/ip mostly quit

working [37]
Steven L Umbach x, Chris

 

[Steven L Umbach]

Yes. Definitely uses winsock and nslookup can also be helpful in diagnosing dns. I
also suggest running netdiag on the broken computer. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;817571 -- repair winsock
manually if you want.
http://www.jsiinc.com/subh/tip3900/rh3968.htm --- how to install support tools
including netdiag.

Try entering an IP address in IE address bar such as 207.47.250.119 [Microsoft
website] to see if that works which if it does would indicate a dns problem.

I didn't try this specifically, but I know it won't work. DNS (name
resolution) is certainly broken, but its more than that, because I
can't telnet by IP address to other local hosts. I tried a different
ethernet card, and that didn't make any difference.

Tracert can also be used to troubleshoot and will show where a bottleneck is in a routed
path.

tracetr works on the local net. I'm assuming it will work to the
internet since it uses ping (ICMP) and not UDP or TCP.

Often repairing winsock will solve the problem. See the link below for
hat. --- Steve

http://www.cexx.org/lspfix.htm --- LSP-fix

I'll try this later. Does Win2k still use winsock?

Th+ 70718 Re: tcp/ip mostly quit working

[37] Steven L Umbach x, Chris

 

[Steven L Umbach]

Shouldn't you be with the family or counting your billions Bill ?? --- Steve

get rid of linux - use microsoft products only

-----Original Message-----

Try entering an IP address in IE address bar such as 207.47.250.119 [Microsoft
website] to see if that works which if it does would

indicate a dns problem.

I didn't try this specifically, but I know it won't work. DNS (name
resolution) is certainly broken, but its more than that, because I
can't telnet by IP address to other local hosts. I tried a different
ethernet card, and that didn't make any difference.

Tracert can also be used to troubleshoot and will show where a bottleneck is in a routed
path.

tracetr works on the local net. I'm assuming it will work to the
internet since it uses ping (ICMP) and not UDP or TCP.

Often repairing winsock will solve the problem. See the link below for
hat. --- Steve

http://www.cexx.org/lspfix.htm --- LSP-fix

I'll try this later. Does Win2k still use winsock?

Th+ 70718 Re: tcp/ip mostly quit

working [37]
Steven L Umbach x, Chris

.

 

[Chris Richmond - MD6-FDC ~]

get rid of linux - use microsoft products only

Well... let see... Once configured, it just runs.
How many years straight does the average Windows box
run? Months? Weeks? OK, how many days at a time?
Oh, sorry, hours...

And I don't what to lose my edge to the point that I
post to Usenet with useless suggestions, top posting,
and failing to edit the non-relevant parts to
save space and bandwidth.

And you could quit hiding behind a false ID.

sheesh...