Question Locked

Windows 2000 Server and Symantec Client

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

I just got a new client with a problem (maybe more than one) that has me stumped. The client runs a Windows 2000 Server for a small network (five computers; one shared printer). The computers all are mapped to a z: drive, which is the server's (partitioned) drive where common data are stored.

As of late last week, two of the computers are no longer connected to the server (that little red x over the z: drive and when trying to locate those computers from the server, they aren't there). I haven't been able to get these computers re-connected. The computers were connected as late as Tuesday or Wednesday last week.

I've been through the Windows network trouble-shooting options, and nothing seems to address the problem there; I refreshed the server services for this drive, and at least one other computer connects--but after rebooting and attempted reconnection, the two disconnected ones still do not.

On a maybe related subject: the server uses Symantec Client (corporate) antivirus, but it may have expired and no one knows the password to access the Symantec Server console. There has been a complete management-level turnover in the organization in the past year. I didn't set up the network and the guy who did cannot be reached. Further, the two computers in question have different antivirus: one Norton, expired 2003 (!) and the other AVG, not registered and not activated. Arghh. Symantec real-time protection process, however, is using the lion's share of the non-system-idle process (surprise) on the server.

And the server has a failed back-up, settings attempt daily backup from NTFS to FAT32 external drive. Aarrgghhhh.

Any and all suggestions are MUCH appreciated.

4 replies

by retro77

Backup what data they do have to a USB hard drive. Use robocopy or your favorite copy utility to copy over permissions as well.

Then reload that server with the OS. Contact Symantec and get a download for your software that you are licensed for and your serial numbers.

Recreate you domain and have the computers join the domain again. You have way to many errors going on to call that server reliable.

by thedpa

Sound advice. My client decided not to try to resuscitate the almost-ten-year-old server; just capture the data needed for a stand-alone station for now. Rebuild a much simpler network for common Internet access and limited file sharing.

Thanks!

by retro77

Your welcome. Hope it all works out to a better, more stable solution in the end.

This discussion is closed to new replies.