Our DNS/DHCP/AD server died and I've finally got everything back up and running with a new server. I have one weird issue I can't quite figure out how to solve.
A client will VPN in to the network and connect just fine (local group, local logon). The only real problem is when they look for remote computers they have to use a FQDN to find the computer itself. This personally doesn't bug me, but all the sales clowns freak out. After VPN'ing into the network they can't remote to <computername> they have to use <computername>.internal.my-domain-name.com what the internal DNS server is designed to resolve. Even using the remote suffix thing on the firewall DNS will not resolve <computername> correctly. ipconfig /all displays without including the suffix name on the vpn connection. The new DNS/DHCP/AD server doles out internal addresses and resolves things correctly according to the internal DHCP setting just fine when on the internal network. It's just the folks VPN'ing in that have this problem.
What's weird is if the remote computer is part of the domain and you logon accordingly everything works just fine. Even ipconfig /all displays the suffix as appropriate. I only noticed this problem myself when setting up a brand new computer to connect in. Old computer, on the domain, VPN, DNS is fine. New computer not on the domain, VPN, DNS doesn't work. Old computer logon is <domain/name>, new computer logon is just <name>, new computer not officially attached to the domain.
I can logically understand why this may be a problem, but what I don't understand is the inability to get the remote suffix stuff to work with DNS on a VPN connection with a computer not on the domain. This really has me scratching my head. Of course as an IT guy I just tell the sales clowns to suck up and deal, but it is still a question I must answer.
Tim
This thread was automatically locked due to age.