Can't connect to terminal server

We have a terminal server setup which is working well.
We can connect to this server when we use the normal host name HL-VENUS

We have created an alternate A record in the Domain DNS which is called venus.ourdomain.co.nz.

We can ping this address and also an NSLOOKUP confirms that the address is valid and pointing to the correct IP address.

However, when we try to connect to this terminal server using the alternate A record as the host name, the authentication fails and only the local administrator is able to connect.

We are positive this is possible - does anybody know how to achieve this.
LVL 1
lemonvilleAsked:
Who is Participating?
 
lemonvilleAuthor Commented:
This was due to using several servers that had been cloned in VMWare.
The servers had not had sysprep run so all had the same Server SID.

Because of this, we were not able to add domain users to any local group including the Remote Desktop Users group.
0
 
simpsolCommented:
If this is a member server, then you will have to use the NetBiosName\Username in the login box for eg let say the Netbois name of the server is HL-Server then you will have to use
HL-Server\Administrator in the user name
0
 
lemonvilleAuthor Commented:
Perhaps I should have been more specific with our request - we are wanting domain users to login using the alternate A record address - is this not possible?
0
Live Q & A: Securing Your Wi-Fi for Summer Travel

Traveling this summer? Join us on June 18, 2018 for a live stream to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
lemonvilleAuthor Commented:
Hi there,

I thought I should elaborate more.

The issue isn't to do with specifying the right Net-Bios name for login at all. The issue is that when we are using an alternate FQDN (which we need to use externally) to connect to the Terminal Server.
If we use the NetBios name with RDP locally, we can login using domain user credentials and local or domain admin credentials alike.
But if we attempt to use a FQDN (remote.ourdomain.com) it will not allow use to login with domain credentials (admin or user). However, local administrator will work.

Any ideas, let use know.
0
 
simpsolCommented:
What happens if you try to login with IP Addrss instead of the FQDN from outside your LAN? One question I want you to clarify is are you trying to Login with the FQDN from inside the LAN.
0
 
lemonvilleAuthor Commented:
For simplicity.
We are unable to login using the external IP as the server is not operational at the moment.
We want users to be able to use the same address while they're inside the LAN and outside the LAN.

Obviously users will predominantly be using it outside the LAN but it doesn't work regardless.
0
 
lemonvilleAuthor Commented:
I can confirm that connecting to the terminal server from outside the lan with our external IP doesnt work for domain users, only the local admin.
0
 
lemonvilleAuthor Commented:
We have chosen this as the answer as there were no other valid answers.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.