Discussion Locked

Win2K TCP/IP Weirdness

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Got a W2k Pro Wkstn joined to a W2k Server-based domain through a Linksys router backbone.
All TCP/IP settings are at install default: nothing crazy custom here. Here's the deal:
occasionally, such as after a re-start or even just spontanaeously, the connection will just drop out. I can reinstall the protocol and all is well for a while, but it will crap out eventually
and just can't be trusted. Again, all the TCP/IP
config settings are default and I'm not doing anymore tweaking to the stack. Any ideas short of a re-build?
Thanks,
Phil

5 replies

by chorito

Is the connection dropped and never comes back..by itself?

Try installing the latest driver for the NIC ... or using another NIC (Not from Linksys)

by lordinfidel

A: What do you mean by connection will just "drop Out" (the little computer lights by the time only light up when there is traffic, if they are black does not mean anything bad)

B: If you get a big red x thru the connection, then check your cables. That would be the best culprit.

C: What do you mean by defaults. Defaults mean to me that you did not set up any IP adressing and the nic is getting a APIPA (169.x.x.x.) address. Which 10 to 1 odds will not be able to talk to your router.
(Side note, the linksys router is not a backbone, it is merely your hub/switch)

Again, Check your netwk cables. Also the port on the switch may be bad. Plug something else into it.

If all else fails, replace the NIC with a different one. Iprefer 3COM 3c905c (not b).

This discussion is closed to new replies.