Remote Desktop to non Domain Controller

Toggle sidebar Toggle sidebar
M

mbuck218

Reputable
Mar 13, 2015
3
0
4,510
I am trying to enable users to be able to remote in to one of our servers without having to use the VPN. Currently, when I try to have them use windows RDP to the server it connects them to the Domain Controller which has already reached its terminal service limits. The DC is a windows server 2003 machine, and the server I need them to connect to is running 2008 R2 which is referred internally as "server4" on the same network.

The domain (mydomain.com) connects to the DC pc, but when i try to connect to server4.mydomain.com it still accesses the domain controller pc.

How could I get remote access to server 4 without vpn. Should I run two domains, mydomain.com / mydomain.net and have server 4 be the DC for the .net?

Any advice would be appreciated.
 
Sort by date Sort by votes
M

mbuck218

Reputable
Mar 13, 2015
3
0
4,510
Not sure what you mean as exposed to the internet. So the domain points to the domain controller which will allow you to rdp into that particular server. All the other servers are on the internal network controlled by the DC but they can get out to the internet, not sure if that helps or not.

I can rdp to any of the other servers while connected to VPN, including server 4.
 
Upvote 0 Downvote
M

mbuck218

Reputable
Mar 13, 2015
3
0
4,510
Yes the DC acts as the RDP gateway, and is actually our internal DHCP. It is a virtual windows server 2003, as well as two other virtual machines and one virtual xp machine. Those 4 virutal servers are ran on w7 physical machines. "server4" is a windows 2008 physical machine and they are all connected to the domain.

This may be a point of interest, and the community may be able to help me resolve. I get an error message saying server4 could not verify license compliance, if the server is joined to a domain make sure it can connect to the domain controller..

Is there a simple way to check the connection? Im pretty confident in the domain policy settings, but not sure why I always get that error and if it is related or not.

Thanks for the advise.
 
Upvote 0 Downvote
D

DerekVGH

Honorable
Jul 23, 2013
84
0
10,660
If you can connect to your domain controller without a VPN by using your domain name in the Remote Desktop Connection box, then you likely have a rule in place in your firewall that routes all incoming requests on port 3389 (which is the port used by RDP) to your domain controller. If you want to access another server in this way, then you'll need to create a rule in your firewall (likely a port forwarding rule) that uses a different port, like 3390, and then directs those requests to the IP address of your other server. It would be easiest if the firewall could also translate the port 3390 request to port 3389 (known as port translation) so that you don't have to modify the server to listen on port 3390.

Once the rule is in place, you would access the second server by using an address of yourdomain.com:3390 to instruct your RDP client to use port 3390 for the request. The router will see this request, translate it to port 3389 and direct it to the proper server. If you use yourdomain.com for the request, then it would still be routed to your domain controller.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom