?
Solved

Mstsc not connecting using IP, but works fine when using the name of the server

Posted on 2013-06-19
6
Medium Priority
?
403 Views
Last Modified: 2013-06-30
Ok, I have 6 servers for a customer platform. When I use the IP to connect using mstsc (microsoft terminal server client), it asks me user and password and after that says that credentials are not valid.

Attemping the connection using servername.domain, works fine. The nslookup translation works fine and the IP is correct. I'm not using IPv6. I experience the problem using the mstsc even between the servers.

Using windows xp attemping the connection using the IP works, but with w2008 server r2 or windows 7, it doesn't.

The problem is that the DNS is private and for the servers only. For external users the access is restricted using a dedicated IP for the client to connect.

Any ideas?
0
Comment
Question by:qualitex
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 1

Expert Comment

by:cpadm
ID: 39260192
On the first RDP connection to a Windows 2008 server, it usually prompts for the following format:

UN: <MyDomain\MyUsername>
PW: ******

If you don't place the domain before the username, it will attempt to use the domain prefix of the machine that you are currently logged on with. if you want to log in using a local user account use UN: <Servername\MyUsername>


To make sure that there aren't issues with DNS records, always try the following troubleshooting steps:

Ping <servername>
Ping <Server IP>
nslookup <servername>
nbtstat -a <Server IP>
0
 
LVL 11

Expert Comment

by:Pradeep Dubey
ID: 39260268
use this command to find out who have this IP nbtstat -a 192.168.19.101 change IP as per server IP.

also
open MSTSC and click on option save the user name and password then connect.
0
 
LVL 11

Expert Comment

by:Manjunath Sullad
ID: 39260971
Hi,

Try adding host entries  on client side.

Go to --> C:\Windows\System32\drivers\etc\ Open Hosts file with notepad.

Add IP address against hostname.

# For example:

102.54.94.97     rhino.acme.com    
38.25.63.10     x.acme.com
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 

Author Comment

by:qualitex
ID: 39261086
Tryed all of that, with the exception of the nbtstat -a, that of course checked after reading, and the names and ips match correctly.

I use DOMAIN\USERNAME ... ,

Well, I'll keep trying. Thanks
0
 

Accepted Solution

by:
qualitex earned 0 total points
ID: 39261126
I just made a new test. Downloaded the 2x client and configured a session using an ip and other with the name. First result: The same.

Then I checked the advanced options in the 2x connection manager and disabled the Network Level Autentication and it worked.

Two questions here,

How Network Level Authentication can be disabled:
* Server Side
* Client Side

I checked in the 2008 R2 mstsc, and didn't find anything. Also my server is configured to allow connections from computers running any version of Remote Desktop.
0
 

Author Closing Comment

by:qualitex
ID: 39287907
I reached an alternate solution to my problem. It is not the final answer. The community told me to try everything I tried and when asked for any other options, SILENCE.
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

For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
Suggested Courses

762 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