Hi! I'm trying to enable VPN access via PPTP, as long as it should work 'out of the box' - first time doing this. I enabled dynamic address assignment, but what's happening is that VPN clients do get the ip address, but when I run ipconfig on a client PC I get a default gateway equals their own client IP address. Seems to be sort of a loop. I thought that their initial default gateway would be VPN server's IP address. Apparently it's not. I try to ping the domain controller from the vpn client. Ping is ok by IP address, but the name cannot be resolved. I tried to define a DNS server explicitly on TMG 2010, still no change. Could please anyone make some suggestion? Thanks, Eugene
Thanks for the reply, Jason. I have enabled DHCP relay agent on TMG Server, following the article, but seems that I still cannot address the server by its name, only by IP address, from the VPN client. The server name is not resolved when I open remote desktop connection on VPN client. Any suggestions what I'm doing wrong?
Oops! It seems that VPN clients do get the correct DNS server address. And I can connect to servers using their FQDN. But is there a way to get access without using the domain suffix? I.e. just type SERVERNAME, instead of SERVERNAME.DOMAIN.COM. My remote PC is not a member of that domain. It's a member of another domain with its own DNS server.
I'll explain why I'm asking. We have partners and we can access one of their servers on their VPN. After I establish VPN connection, I use only server name, without domain suffis to connect to it. I did not do any configurations on my DNS to search for servers on their domain, I just get access without using FQDN. The only difference I can see with ipconfig /all between my and their VPN is that when I connect to their network, I get a WINS server assigned. Might this be the answer? Unfortunately, I cannot talk to their sysadmin to find out how they did this.