Question
August 13, 2007 at 09:55 AM
thedpa

Windows 2000 Server and Symantec Client

by thedpa . Updated 18 years, 11 months ago

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.

This discussion is locked

All Comments