How to Check Rdp Port Is Open or Not
- Home
- Windows
- Windows Server
Our Windows 2003 File Server will no longer allow RDP it seems. I can RDP to our other servers, but no longer into this box.
Any suggestions on what to check to remedy this situation?
At present I'm using another tool for remote access to this box, but would prefer the more secure RDP.
Thanks,
Spacewalker
Disable Vipre and try to rdp in. This will tell you if your software firewall is the blame.
Also check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp >> PortNumber
for your port number.
The help desk software for IT. Free.
Track users' IT needs, easily, and with only the features you need.
22 Replies
We had that happen to us once. It was after an update and the local firewall turned back on. If you normally have your local firewall on, I would check the settings to make sure it is still allowing RDP through.
Check that that the windows firewall is allowing rdp port 3389.
Check that any other firewall you have in place has a hole in it for rdp.
If you are going through a router you may need to set up a port redirect.
Is it consistent? I just had that happen, it was due to a 333 error, would not allow RDP, turning off TOE on the NIC seemed to help me.
If not that, I agree with the firewall either turning back on due to an update....
If you can remotely access the registry, check the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
Check that the value for fDenyTSConnections is set to 0.
Hello all - here's what I've found so far.
1) We don't use the Windows Firewall, we use VIPRE Business Premium.
2) I checked anyway, and the Windows Firewall is OFF.
3) I DID find that I had this server in question (call it 02), had a slightly different firewall rules profile, so I moved it into the profile that all the other servers had, but I still CANNOT RDP into it.
Any other ideas at this point?
Any services in particular to check?
This is our file server and an application server, so I'd really like to get this working.
Thanks,
Spacewalker
Oh, and I checked the registry value that Brian mentioned, and it was set to zero.
All I continue to get is this error (screenshot link)
http:/
(By the way, JING from TechSmith, is a nice free tool to have.) That's how I took that screenshot.
JING also allows for some markup (arrows, boxes, text boxes, highlighting, and up to 5 minutes of video with sound.)
Is the Terminal Services service running?
Can you ping the box?
Is it possible that the listening port of TS has changed? The default port is 3389.
can you telnet to that server on port 3389. If you can't the remote desktop service is either not running or a firewall is blocking it.
If telnet succeeds, then it's security related- GPO?
Brian - The "Terminal Services" service is Started and is set to manual for some reason.
The "Terminal Services Session Directory" is set to disabled.
Should I change either of these?
Hi Joe - I can ping the server.
Hi M.C. - perhaps I'm not trying the telnet command correctly, but it fails on server name and IP, even though I can ping the box. I know this means their could be a firewall issue, but I can RDP to the other servers that use the same exact FW settings.
C:>telnet -a ServerName 3389
Connecting To ServerName...Could not open connection to the host, on port 3389: Connect failed
C:>telnet -a 192.168.5.11 3389
Connecting To 192.168.5.11...Could not open connection to the host, on port 3389: Connect failed
When I try this telnet (by ServerName) to another server than I CAN RDP to, then I don't get the "Connect failed" message (just an empty CMD window with a blinking cursor).
Is there something else I'm missing here?
spacewalker wrote:
Brian - The "Terminal Services" service is Started and is set to manual for some reason.
The "Terminal Services Session Directory" is set to disabled.
Should I change either of these?
In 2003, terminal services is defaulted to manual. This service, although it is set to Manual, will start if Remote Desktop for Administration is enabled.
I believe the "Terminal Services Session Directory" is used if you are using clustered Terminal Servers.
Is this a Dell Server? or Virtual Server?
I've had the issue in the past had to do with a video driver causing my issues.
Updated / downgraded and issue was resolved.
Disable Remote Desktop and then re-enable it. I've seen the same thing on 2003 a few times.
Have you tried Telneting to the box using Manish Chacko's suggestion? If the box is not listening on port 3389 the default port then you will get this issue.
I have often changed the listening port on TS to make it less vulnerable to prying eyes.
Have you checked the event logs for any errors that getting logged when you try to connect to the box using RDP?
TO Check/change the listening port check this site:
http://support.microsoft.com/kb/306759
If this is set to default and you still can't connect - I would look back at some firewall type issue that is blocking access to TS.
Disable Vipre and try to rdp in. This will tell you if your software firewall is the blame.
Also check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp >> PortNumber
for your port number.
Hi spacewalker,
this means that either you dont have RDP enabled or it's listening on another port. Make sure that remote connections are enabled-see screenshot provided by philipmjr.
If it is enabled, try Joe925's suggested article by MS.
Good luck
Manish
First - thanks to everyone for the suggestions.
*** I finally got in! ***
Philipmjr - RDP was enabled.
Max M - I tried disabling and re-enabling a couple of times, still no go.
B-C - This is a Dell Server, and the exact same as 4 other servers we have here with same OS and hardware. And it is a Dell R710.
Joe925 - I did try telneting. See earlier post when it didn't work. I didn't check the error logs yet. I didn't check the articel 'cause I didn't think I'd changed the listening port.
Trigg Gayle - Thanks for the link straight into the registry to find the listening port. That turned out to be the key! (Sorry Joe925 - I'd have found this on your suggestion if I'd checked it first too!)
It was set to some large odd number...wait a minute...I know what that number is. It's a special day in my family! (Resist urge to insert Phineas and Ferb quote here about doing something like Doof!)
I totally forgot that I was the one that changed the RDP port after a hacker attack and server rebuild that I did.
Wow! It sure was secure! Even I couldn't get in!
Thanks everyone for helping me to figure this one out!
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
How to Check Rdp Port Is Open or Not
Source: https://community.spiceworks.com/topic/208601-rdp-to-server-not-working
0 Response to "How to Check Rdp Port Is Open or Not"
Post a Comment