Cannot logon to W2K server

And you have scanned this server for viri and malware?

oohh. this a good one. so is system totally hung finally or just those symptoms you described when you login and if you can't login how do you know that event logs are blank? are you saying you can login when rebooted and eventually this problem crops back up?
nothing changed eh? no new client pc's on the network...what else is running on this box. is it just a file server? does it backup to tape. like that.
since you can login sometimes, you right away backed up the exisiting repair folder and made ERD disk for this box yes? and a ntfs boot disk, yes?
and you can shutdown, reboot at will, yes?
when i searched 'blank event log' at support.microsoft.com i only got article that event logs can become corrupt on win2k. there is a hotfix (i am throwing up over here on your behalf) for it.
so that made me think: wonder if you could delete the log (well, rename it instead) and force a new one. also, we know there is a setting in win2k for how big to let the registry become. perhaps needs to be larger. ditto for the event logs. maybe try that stuff because it is easy and should have a look at it anyway...
i'd reseach the howto's for both in mskb at support.microsoft.com
since it used to work and now doesn't it could be weird problem with updates but that fails Occams razor imho. 1st suspect is space problem, either overfilling the logs the registry or the boot/system hard disk. 2nd suspect i would think 'needs defragging' 3rd suspect 'failed hardware' NIC is easy to replace. RAM might be easy to divide and try half...(performance monitor, look at paging for example)
so check for plenty of defragged free hd space.
and watch a reboot. RAM look right? hd's look right? any controller errors. any thing at all giving clues...
also i'd be looking at the bios(es) revision level(s) just because i am alredy there, looking.
then i would run chkdsk /f on all the drives and then i'd run windows update just to see if any new drivers and does it update ok?

I have narrowed the problem down somewhat. I got Event Viewer working. It just needed the logs cleared out, but I am still getting the "network request is not supported" when trying to log in to a remote desktop. Remote desktop will work fine for about 3-5 hours and then I will start getting the error message again and cannot log in from a remote desktop window, but I can from the console. I was going to reinstall Terminal Services, but the server locks up solid when I try to open add/remove programs. I have to cycle the power to get back to Windows. I thought it may be a hardware issue. I unplugged everything off the motherbaord that it didn't need to boot, swapped out the RAM also, but still having same problem.

I forgot to say in my last post that I did do a virus scan and a spyware scan. It found a minimal amount of spyware(couple of registry entries)and on the virus scan, no viruses.

Point value changed by question poster.

This question was closed by the author