I am trying to connect to my work desktop computer through a VPN connection using Microsofts Remote Desktop Connection at home. I get a successful VPN connection but when I enter my work computers name, userid, and password through Microsofts Remote Desktop Connection I get a "Cannot find Computer" error message. If I use the IP address instead of the computer name I am able to successfully log into my work desktop computer. How come my remote VPN connection cannot see my work computer's name but the IP address works fine? Also when VPN connected I cannot see other computers on the work network. I am able to remote desktop connect using my computers name when I am at work on the same LAN. I know many would say what's the problem, just use the IP address. However, I am trying to set up a remote desktop access proceedure for other employees in the company who are not that computer literate. I can easily find my remote computers IP address but it is not that simple for others. I am running Windows 7 Professional on our work desktops and VPN through our Windows 2008 R2 Server. Any ideas?
Given that you can connect by IP address, the problem is one of name resolution and is likely to be a NETBIOS/DNS issue
At work, your machines are probably on a domain such as "company.local" so when you connect to, say a machine called WORKSTATION its FQDN (Fully Qualified Domain Name) is actually WORKSTATION.company.local
At work you will likely have a fully operational DNS/WINS/NETBIOS system up and running so both the short and long versions work
At home, I suspect that the VPN is not picking up the correct name servers.
If you try connecting to e.g. WORKSTATION.company.local i.e the long name, does it work? If so then its a WINS/NETBIOS problem but if not it is a DNS issue
Do you have split tunnelling enabled over your VPN connection? If yes, read on. If no, ignore this advice!
Perhaps your VPN client is sending DNS requests to the local side of the tunnel rather than the remote side. AFAIK, some VPN clients will try a request on one side of the tunnel, and if this fails, the client tries the other side. It it tries the local side first and your configured DNS server doesn't respond properly with an error when it doesn't find the address (perhaps it's configured to redirect you to adverts etc.) then that might break it.
If possible (and if you have a split tunnel) try disabling your split tunnel. They're a pretty bad idea from a security point of view anyway...
If this isn't possible, when you're at home try changing your home DNS settings to Google's public DNS http://code.google.com/speed/public-dns/ these servers shouldn't issue redirects, so you should get a proper error response...