Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

RDP into Server 2012 Standard Issue

Posted on 2013-12-11
5
Medium Priority
?
456 Views
Last Modified: 2013-12-17
I have a new 2012 standard server, set up as a DC, not a part of my domain nor will it be. I have enabled Remote Desktop access, firewall is off, and I believe I have correctly configured RDP services on the machine (it will primarily be a "terminal server"). I can RDP to other machines on my domain from it. RDP services appear to be started and running appropriately, or at least the ones I am familiar with.

But no matter what I do or configure, I can NOT rdp into the 2012 server from my Win7 machine or any other machine on my domain.

The server came from a software company who actually performed the install and configuration, and from what I can tell/find, they did nothing to prevent RDP access into the server.

I'm at a loss at this point as to why I can't rdp into this thing.
0
Comment
Question by:tjwo94
  • 4
5 Comments
 
LVL 15

Assisted Solution

by:achaldave
achaldave earned 2000 total points
ID: 39712776
There can be anything from changed default RDP port, custom firewall, some other application listening on same port or encryption requirement.

Since the server came from software company, is it running any proprietary application on it? It is possible they don't want you to login using RDP, you might want to check if enabling RDP breaks any license agreement.

you can use netstat -anb or netstat -ano command to identify application listening to port 3389 (default RDP)

Check TDP-TCP properties under Remote desktop configuration for SSL and network configuration, check security for any deny permission.

To check if RDP is listening on non default port or not open regedit
check PortNumber under HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\tds\tcp

Also make sure fDenyTSConnections is set to 0 under
HKLM\System\CurrentControlSet\Control\Terminal Server\
0
 

Author Comment

by:tjwo94
ID: 39714129
I have checked the registry locations, both are fine.
No applications are currently listening on port 3389.
No encryptions exists, nor custom firewall policy.

Not sure where to look for the TDP-TCP properties you mentioned.
0
 

Author Comment

by:tjwo94
ID: 39714333
So I called the software company to verify if they changed something I can't find to prevent me accessing this port. They did.

They changed the default port from 3389. However, when I check this in the registry, it says the port is 3389. What gives?
0
 

Accepted Solution

by:
tjwo94 earned 0 total points
ID: 39714342
Ah, this is why.

The appropriate registry key to check for default RDP port is this:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

Thank you for the help!
0
 

Author Closing Comment

by:tjwo94
ID: 39723479
Splitting points for both efforts to diagnose issue. Had to do some more of my own leg work to find the correct issue, but you definitely pointed me in the right direction, and helped to eliminate some other causes.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Working from home is a dream for many people who aren’t happy about getting up early, going to the office, and spending long hours at work. There are lots of benefits of remote work for employees.
Measuring Server's processing rate with a simple powershell command. The differences in processing rate also was recorded in different use-cases, when a server in free and busy states.
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

886 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question