Details about aVPN and computer trying to get back to the SBS 2011 standard server
I'm new to this. SBS 2011 domain at 192.168.1.0/24. There's a VPN to a remote office with ip 192.168.2.0/24
At the remote location I am setting up a desktop. In hosts file on this new computer, I added the server IP 192.168.1.3 pointing to server.domain.local ; server ; domain.local.
Tried running http://connect and that didn't work. I added connect as an entry in hosts and that still didn't work. I googled and found that the dns on this new machine should point to the server. so I added that (the router at the remote location is doing DHCP and DNS normally.
Going forward, to be able to access shares on the server, etc. can the dns be the local router? it's a sonicwall. is there something I need to do on the sonicwall to have it know to check with the server / dns at the home office.
is there anything else I need to do to be able to have this remote computer act / think it's in the home office on the other subnet?
thanks!
At the remote location I am setting up a desktop. In hosts file on this new computer, I added the server IP 192.168.1.3 pointing to server.domain.local ; server ; domain.local.
Tried running http://connect and that didn't work. I added connect as an entry in hosts and that still didn't work. I googled and found that the dns on this new machine should point to the server. so I added that (the router at the remote location is doing DHCP and DNS normally.
Going forward, to be able to access shares on the server, etc. can the dns be the local router? it's a sonicwall. is there something I need to do on the sonicwall to have it know to check with the server / dns at the home office.
is there anything else I need to do to be able to have this remote computer act / think it's in the home office on the other subnet?
thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Unfortunately this a common mistake with DNS. DNS in Windows does not act as one would expect. It does not contact the primary DNS and when that fails, the secondary. It responds to the first DNS server that 'answers'. On a LAN this constantly causes slow logons and name resolution issues as the ISP, which forwards to the ISP, will often respond first. In a VPN situation the ISP will almost always respond first and the alternate will not be contacted until a time out period when the ISP cannot resolve the internal name.
The link I provided includes the DNS configuration.
I agree not joining the domain can have some advantages, maybe more so with with Windows 8, but not doing so requires 2 step authentication (PC and server), and does not allow group policies and drive mappings to be pushed out.