Problem entering computer name for remote acc

October 7, 2010 at 10:14:09
Specs: Windows XP
I use a TightVNC to remotely access my client machines to diagnose problems. When I enter the computer name it can't connect but if I use the IP address it connects. Why doesn't it work when I use the computer name?


See More: Problem entering computer name for remote acc

Report •

October 7, 2010 at 13:01:55
because you are not connected to a dns server that knows these computer names and their associated ip addresses.

You should be able to create a hosts file with the names and ip addresses and then using the name should work

Report •

October 7, 2010 at 13:20:57
I have DNS server setup. Does this mean DNS is not functioning correctly?


Report •

October 7, 2010 at 14:45:29
If you are running a lan based dns server it will only know about the pcs on your lan that you entered into dns or are dynamically updated via dhcp server.

Maybe this will make it clearer to you what the issue is.

I have a local lan with internet connection
You have a local lan with internet connection.
On my lan I have a pc called Bread
On your lan you have a pc called Toast

My lan only knows about Bread but not Toast
Your lan only knows about Toast but not Bread


Because the local lan resolves local names by broadcast and each pc builds a list.

Your local lan has a dns server but again it only knows of your local lan Toast since you either manually entered its host and ptr records in dns or you configured the dhcp server to dynamically update the dns server. Not having done either Toast also is resolved by broadcasts.

Broadcasts don't go past your router.
The internet dns servers don't know of either Toast or Bread

Make sense?

By creating a hosts file containing the entries of ip address and host name these are cached upon bootup. You type the name in TightVNC and it should look at the local dns cache to resolve the name to a ip address.

Update: just occured to me that perhaps when you say "remote clients" you really mean clients on your lan. If this is the case then yes your dns server is not configured properly.
Usually I refer to remote clients as those accessed via the internet and router port forwording.

Report •

Related Solutions

October 8, 2010 at 06:35:24
Yes, when I said "remote" I meant clients on my LAN. Sorry for the confusion. I have DNS and DHCP running on a Windows 2003 server.


Report •

October 8, 2010 at 08:21:28
Then it would appear you have not entered the host and ptr records statically into dns concerning your host pcs or you have not configured dhcp to autoupdate dns.

Report •

Ask Question