I realize that this is a question that has been asked before, but I've tried all of the suggestions I can find and nothing seems to work. Our database server for our medical system runs Windows 2003 server. Last month, suddenly, we were unable to RDP in to the server. However, our application server has been communicating with this server without difficulty and I can remote out from the database server to any location. My internet connection is also normal. No components have been changed (we use a Sonicwall firewall). I have removed our antivirus, freed up disk space, verified Remote Desktop is enabled, verified Terminal Services "Limit number of connections" Policy, verified Terminal Services RDP-Tcp properties, Checked the terminal service is listening on the port 3389, etc. Any suggestions woould be greatly appreciated. BTW, I am the administrator, but in name only. I do not have training in server administration, so I will need it kept fairly simple. Again, thanks for any help.
closed as off-topic by Esa Jokinen, kasperd, womble♦ Oct 20 '17 at 2:25
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions should demonstrate reasonable business information technology management practices. Questions that relate to unsupported hardware or software platforms or unmaintained environments may not be suitable for Server Fault - see the help center." – Esa Jokinen, kasperd, womble
Honestly, I've seen this happen on a 2003 server before but it wasn't my server and the person who ran it wasn't really interested in fixing it. Check the related registry keys (
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server) and see if anything in there looks hinky (particularly
fDenyTSConnections). Hopefully that'll help. If not, check the event logs for information, as TessellatingHeckler suggested.
That said, I'd feel irresponsible if I didn't encourage you to upgrade this server to an operating system that's still in mainstream support. You also haven't said what database server you're running, but hopefully it's one that's still supported. You can get that information here. As Joel Coel pointed out in the comments, Windows server 2003 no longer receives security updates. You have a responsibility to the patients served by your facility to keep their data private. I'd look at migrating to a new server before spending too much time fixing the old, out-of-support one.