DNS problem across subnets

Discussion in 'DNS Server' started by Woodberg, Jun 6, 2008.

  1. Woodberg

    Woodberg Guest

    I recently setup a remote site which is connected to our main location with
    a dedicated T1. We setup the new site with its own subnet which is
    different than the main site. The networks are talking and I can ping
    resources across both networks. However, I don't think internal DNS is

    When I am on the remote subnet, I can't map a drive to a server on the
    primary network subnet.

    What are some things I can look for to make sure everything is configured
    across the 2 subnets.

    My network is a very basic, Windows 2003 Server AD. The internal DNS server
    is setup on the Windows 2003 server.
    Woodberg, Jun 6, 2008
    1. Advertisements

  2. Hi Woodberg,

    I have a theory that it's actually the Windows Firewall (on the client)
    blocking this. The default rule prevents File Sharing access on subnets
    outside of the local one.

    We shoudl check Name Resolution though. If you open up the command prompt
    and run nslookup or ping for the server name, does it resolve? If it gives
    you an IP DNS is done and can be ruled out as the cause.
    Chris Dent [MVP], Jun 6, 2008
    1. Advertisements

  3. Woodberg

    Herb Martin Guest

    Chris' theory of firewalls is almost certainly correct.

    It can be any of the firewalls on the client, server or between them.
    Herb Martin, Jun 7, 2008
  4. Woodberg


    Jan 28, 2011
    Likes Received:
    Re:Mapping across subnets

    On the Windows server go to Firewall,Exceptions. Hilight File & Printer Sharing, Select Edit, Change Scope. Select "Any Computer". That should fix your problem.
    fetz, Jan 28, 2011
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.