Re: Setting Up LMHost File? (DNS problem on VPN).

LMHOSTS really has no relationship to DNS. DNS knows nothing about Netbios names and the computer browser service. LMHOSTS is used with the Netbios naming service. The name server for this is WINS. The static file for DNS-style names is called HOSTS.

The remote user should be able to use the DNS service on your LAN. It should get the DNS server address as part of the VPN setup negotiation. Check if the client can resolve a LAN machine using its FQDN (eg servername.mydomain.lcl). If this works, DNS is working correctly. All you need to resolve names using just the machin name is to manually lcode your DNS suffix into the connection properties of the client. Then when you try to resolve servername, the DNS suffix mydomain.lcl will be added to the query and it should work.

"Andrew Staley" <andrew@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:8E92FD6E-E251-4805-83D7-0D79DDB6BE75@xxxxxxxxxxxxxxxx
I've not long taken a carrer change into IT, having always had an interest in computing. So I have a resonable grasp on computers, but still have a lot to learn about servers and networking it seems. So I appolgise for the long winded post.

Currently we have several remote offices connected to our domain on a private network setup by BT, after several bad incidences with BT we have decided to look at ditching them and setting up our own VPN system into the domain.

As things would have it, we are moving one of the remote offices and decided now would be a good time to trail the idea to see if it is workable and what sort of pitfuls we might full into.

So I've got a VPN setup between the remote office and our head office. Which is setup;

Remote Computer>Router/ADSL Modem (Netgear FVS318)>Internet>Router>Firewall (Prodigy P100)>Internal Network. Remote computer is on 192.168.30.0, internal network is on 192.168.1.0.

From the remote computer I can ping the servers via IP address, so the VPN is up and running. But I can't ping them via name (I.E Srv1), now I know this is a DNS issue, but I don't know how to resolve it. One suggestion that was made on another forum is to setup a LMHosts file with the details.

My question is, when I setup a LMHosts file is it enough just to enter;

192.168.1.100 Srv1 #PRE #DOM:DOMAIN_NAME

Or do I also need to enter the NetBIOS hex codes as well for the Master Browser and DC?

Thanks in advance, AStaley.

.

Relevant Pages

  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... Both firewalls are setup as 192.168.x.250, and have the subnet listed for each side. ... The remote site is on a standard ADSL line with static a IP and I've configured the Firewall/Router to take it's settings from the ISP, which includes the DNS. ... If you want to have Netbios name resolution you will need to have all machines using the same WINS server. ...
    (microsoft.public.windows.server.networking)
  • Re: Virtual LAN Problem
    ... Gateway device and MANUAL DNS settings to get it to work. ... connectivity with the remote LAN and from the remote LAN. ... Confirm a decent tunnel by pinging the remote site internal clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote connection to domain over VPN problem
    ... The router at the remote end "is" providing DHCP as their is no other device ... So DNS setting is not an issue. ... be supplied by the SBS server and if the VPN is down I ... If the remote computer has DNS properly setup, ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... We have around 17 remote sites so using a DC for each would be ... also the DNS server. ... which includes the DNS. ... We really need a lot more info about the setup. ...
    (microsoft.public.windows.server.networking)
  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... also the DNS server. ... The DCs in the remote offices don't have ... which includes the DNS. ... We really need a lot more info about the setup. ...
    (microsoft.public.windows.server.networking)