| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 106681 | 2010-01-19 01:28:00 | Server 2003 RDP has stopped working | aidanmaz (7180) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 849815 | 2010-01-19 04:05:00 | yes the reg key is set to 3389, the default port | aidanmaz (7180) | ||
| 849816 | 2010-01-19 04:10:00 | right.,..if it didnt show up in your netstat then something is stopping it from listening, hence the failed connection. I would start suspecting AV, Firewall and any recent windows updates applied to the box. Try disabling your AV / Firewall if enabled. I would also be suspicious if any windows updates were recently installed. Finally check that no group policy changes have been made that could effect it. THats about as much as I can think of without being in front of the box sorry. | Barnabas (4562) | ||
| 849817 | 2010-01-19 04:19:00 | Thanks, i have disabled the A/V and still no go. Win updates are done manually and like i said earlier, i havent done any for about 2 weeks. | aidanmaz (7180) | ||
| 849818 | 2010-01-19 04:26:00 | If you run firewall.cpl is the service running? | CYaBro (73) | ||
| 849819 | 2010-01-19 04:30:00 | What is listed under Terminal Services Configuration - Connections? Anything? You should have at least one listed, usually "RDP-Tcp" |
CYaBro (73) | ||
| 849820 | 2010-01-20 21:48:00 | Have you tried running netstat -an to check for open ports on the server? You'll get a list of ports that are listening on your computer. You should see "TCP 0.0.0.0:3389.........LISTENING". If you aren't then your PC isn't listening for remote connections. In the Services control panel, you should also see the "Terminal Services" service running. You should also see "Remote Procedure Call (RPC)" running. |
SolMiester (139) | ||
| 849821 | 2010-01-20 21:49:00 | Also check if Updates KB970430 & KB971737..They beef up the authentication requirement and may have stuffed up your access! | SolMiester (139) | ||
| 1 2 3 | |||||