Re: Remote connection to domain over VPN problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance




The router at the remote end "is" providing DHCP as their is no other device
there to provide DHCP, but as mentioned I have setup the dns manually to
point to the SBS server via the TCP/IP settings on the desktops located at
the remote location. So DNS setting is not an issue. Since the REMOTE
machines are on a different subnet, it is not possible for DHCP requests to
be supplied by the SBS server (that I am aware of) and if the VPN is down I
want the remote machines to still be able to connect to the network and be
able to access the internet.

I can ping the SBS and all workstations on either side of the VPN.

VPN passes ALL IP traffic.

Will try to append the domain name under the settings you reccomended
tomorrow and see what happens.



"Leythos" wrote:

In article <2486D5E2-1BD5-47DE-B1D1-58F406750D8A@xxxxxxxxxxxxx>,
PaulS@xxxxxxxxxxxxxxxxxxxxxxxxx says...

I have manually configured the devices to use the DNS of the SBS server.

Yes I can ping every device on both networks.

If a computer is not a member of a domain and the logged on user has the
same username and password as a domain user they can access the SBS server
and all the file shares that they need too, but ideally I would like to force
them to use the domain so that the machines can be better managed.

If the remote computer has DNS properly setup, meaning the ONLY DNS is
that of the SBS Server at the main office, (normally this means that
your ROUTER at the remote end is not providing DHCP as you can't tell it
to properly ISSUE the same DHCP Scope items).

In the TCP IP settings, you need to enter the DNS domain name of the SBS
server domain in each remote computers settings.

If you can pint the SBS Server by it's short name, then you can also
point any workstation at the main office by its short name, then you
have DNS properly setup (as well as local DNS) on each of the remote
computers.

You also need to ensure that the tunnel between remote office and main
office passes ALL traffic.

We do this all the time and you have to manually add the DNS:

Under Advanced TCP/IP Settings, DNS tab, setup APPEND for the SBS domain
name path, then setup DNS SUFFIX as the SBS domain name...

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@xxxxxxxxxx (remove 999 for proper email address)

.



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: 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)
  • RE: vpn and joining remote computers
    ... Windows XP is not configured to use a local DNS server. ... Use remote Small Business Server as DNS of this client: ...
    (microsoft.public.windows.server.sbs)