IT Employment

Ask something
Discussion Locked

Windows 2000 DNS Problem

0 helpful
2 replies

by aplustoz

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

I was called to a small (two computer) network running 2000PRO on one and Win98 on the other. Internet connection is local cable through a switch. Win98 machine connects perfectly. Win2000 connects every other time. Reboot allows connection, but next reboot does not. System was loaded with Nimda, Nimda.D, Weird.10240 viruses which seem to be cleaned now. Discovered keystroke memorizing executables on the root directory (which I renamed and moved to another directory).

Any suggestions asto what files may have been damaged that would still affect the TCP/IP WAN connection so that it would work perfectly on 50% of the boots and not at all on the other 50%?

2 replies

by expertpc

I am questioning why you would not wipe after all the problems and potential damage as well as the key capture app.

If you have no choice, start by removing all the networking components. Then reboot. After a good reboot, reinstall all the ip components:

Client for Microsoft Networks
Internet Protocol (TCP/IP)
File and Printer Sharing for Microsoft Networks-(if you dare)

Now to your "switch". Is it actually a cable router? Is it doing DHCP? If it is not a router, then do you have multiple IPs from the ISP?

Good luck and please answer the q's proposed above.

by aplustoz

Thanks for your help, but those were performed prior to the posting.

I had already uninstalled and reinstalled the networking components. That did not solve the problem.

The switch is a switch, not a router. They have persistent IP addresses assigned by the cable provider.

The following day, the Windows98 machine crashed, requiring a rebuild of the OS. No viruses had shown up on the virus scan with two antiviruses using current virus definitions, but in addition to the corrective reinstall (renaming the win.com and system.dat files), re-writing the master boot record and flashing the bios on the Windows98 machine, the problem on the Server went away.

I'm not certain which file or program may have been the culprit this time, but again thanks!

This discussion is closed to new replies.