Why I can't RDP to the remote machine by the name?


Hi Experts,

After VPN to office, I can't RDP my computer in office by the name. I can RDP  by the Ip Address. I checked the DNS and machine has an A record in DNS server. I also checked the Ip settings after VPN connected and the correct DNS has been assigned.

Is this related to my ISP?

Thanks!
JasminZAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob WilliamsCommented:
When you say you checked DNS, sounds like you only checked the server (the other end)? With many VPN's NetBIOS names are not broadcast over the tunnel, and with some it is not even possible. Often you can only use IP's. Then again it may be something misconfigured.
How have you created your VPN, i.e. hardware tunnel (what make) or software, Windows VPN, etc?
Can you connect to other items by name such as shares, map drives or browse the network?
Test the client end at a command prompt to see if the name resolves with  " nslookup  computername "

You can get around this by adding the computer name to the local LMHosts file  located on the workstation under %windir%\system32\drivers\etc\LMHosts   If you need help configuring please advise.

Shouldn't have anything to do with your ISP.
Keith AlabasterEnterprise ArchitectCommented:
The ISP will not even know what you are doing as the VPN will have created a tunnel between yourself and the VPN header devcice in your office. As Rob mentions, this is a simple case of being able to resolve the names.
Are you using split tunneling or is all traffic being pushed through the VPN tunnel?
Steve AgnewSr. Systems EngineerCommented:
You need to probably add the domain of your computer you are attempting to connect to to your DOMAIN SUFFIX SEARCH ORDER... or put in the FQDN when you attempt to connect to it..  You do this in advanced TCP/IP configuration in the DNS tab of the pc your attempting to use to connect.  Your computer you want to RDP to is (example) jones.conundrum.com you should put conundrum.com in your domain suffix search order.  Whenever you are using the name your pc doesn't know to add the conundrum.com name to it.. (where conundrum.com is whatever it's domain suffix is) thus you can't get to it.  If you do an IPCONFIG /ALL from a command window on the PC you want to connect to you will see it's PRIMARY DOMAIN, you can use this as a name to connect to whenver you connect, or put it in the domain suffix search order and windows will automatically 'tac it on' and search for it when you don't use a domain suffix.  This is also helpful if there are more machines you want to get to- and why the domain suffix search order exists since Microsoft uses netbios names instead of FQDN's like the internet was founded on.. a wonderful kludge to darken your day- but a necessary evil to be compatible with the history of Windows.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.