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.
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.
ASKER
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?
ASKER
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.
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.
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.
ASKER
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.
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.
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We have chosen this as the answer as there were no other valid answers.
HL-Server\Administrator in the user name