Windows server 2003 unable to login as there is no Ctrl / Alt / Del option, just a yellow exlamation mark triangle
When starting our DC server (windows server 2003) it boots up as normal, but once you get to the login screen it only displays the "Windows server 2003" logo with a exclamation mark within a yellow triangle icon as well. All the services are running on the server, I can access the active directory and computer management remotely, it's also functioning as our printer server which is also working. We just can't login to it remotely (just displays a blank screen) or locally ?
Any ideas would be greatly appreciated as I haven't come across this one before
Any ideas would be greatly appreciated as I haven't come across this one before
Massimiliano Loi
What about the eventviewer? Are you able to see any warning/error?
thats odd. Like maxloi suggested I would start in the event log.
Also since when have you had this issue and have you made any changes recently to affect it?
Any changes to group policy?
Does your other servers and workstation work fine and you only have the issue on the DCs? is it all DCs or just one?
Have you installed any new print drivers that could be causing the issue?
Also since when have you had this issue and have you made any changes recently to affect it?
Any changes to group policy?
Does your other servers and workstation work fine and you only have the issue on the DCs? is it all DCs or just one?
Have you installed any new print drivers that could be causing the issue?
ASKER
Nothing has been changed on the server, no new bits of software either. I had a look in the event viewer but there are only a few warnings that are not related to anything we haven't known about for a while and was nothing serious anyway.
The only thing that has happen recently was the C: drive did fill up but we managed to clear some space on it ( removed unwanted files and windows update uninstall files. )
All the other servers are working fine and we only have the one DC in the domain. At the moment I'm starting to build a replacement just to be proactive.
The only thing that has happen recently was the C: drive did fill up but we managed to clear some space on it ( removed unwanted files and windows update uninstall files. )
All the other servers are working fine and we only have the one DC in the domain. At the moment I'm starting to build a replacement just to be proactive.
In my opinion your first priority should be to get another domain controller up and running and transfer all roles to it.
having just one DC in the domain and especially now that your only dc is giving issues this should be done asap.
Coudl it be that your Dc is always running out of space? perhaps you have auditing on and its making the log files fill up too fast, hence taking up all your disk space?
or is there anything else that could constantly be taking up your disk space or was that a once of occurance?
having just one DC in the domain and especially now that your only dc is giving issues this should be done asap.
Coudl it be that your Dc is always running out of space? perhaps you have auditing on and its making the log files fill up too fast, hence taking up all your disk space?
or is there anything else that could constantly be taking up your disk space or was that a once of occurance?
After having setting up the new DC that I also consider to be the first thing to do, could you also check for some automatic update did on that server on the last days, also considering drivers and software updates?
ASKER
Thanks for the suggestions chaps. I'll get the replacement sorted first then I'll concentrate on the current troublesome DC server.
Eugene: The server has run out of space once before, due to a printer going haywire and the print cue filling up.
Eugene: The server has run out of space once before, due to a printer going haywire and the print cue filling up.
Once your 2nd DC is up it may also be a good idea to perhaps move the print server from there to perhaps a file server etc. Because your DC,s are the foundation of your infrastructure , its best practice not to install anything else on them than their role. I do however understand budget constraints and it may not always be possible,but if you can , then do that.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Solution found on internet
Glad you got it sorted, weird though how it got like that in the first place . Hope you setup a second dc yet though.