[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 345
  • Last Modified:

Can only ping by FQDN between two different domains

I have two different sites connected via an IPSec LAN to LAN VPN.  I am able to browse shares, printers, terminal services etc but only by IP and FQDN.  At each site there is a dns server and that resolves names for the internet and LAN resources local to each site.  the DNS set up has forwarders pointing to each office DNS server, and I have added secondary zones which are copies of the others primary zones, but still I can only ping by FQDN.  eg ping server1 timesout, ping server1.domain.com gets a reply.

I have trawled through other solutions all day, if there is a solution out there I can't see it and I am sure it's not too big a problem to someone!

Thanks
0
markithomas
Asked:
markithomas
  • 3
  • 2
  • 2
  • +1
1 Solution
 
Mark PavlakCommented:
is this tunnel using software or hardware?
0
 
camacho_marcoCommented:
Try and configure Reverse lookup zones also, and see how it goes.

CHeers
0
 
markithomasAuthor Commented:
the tunnel is a hardware tunnel
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
markithomasAuthor Commented:
I created reverse zone but can only create a stub zone, it won't create a secondary and still can only ping to the server.domain.com

Thanks
0
 
oBdACommented:
A reverse lookup zone won't help you anything here. Your problem is that the client doesn't know which DNS suffixes it should check.
One way is to add the DNS suffix of the respective other domain on the clients in the Advanced settings of the TCP/IP properties (in the DNS tab). Make sure you add the client's own primary domain suffix in the list as first entry. Test this on a client before you roll it out.
Another possibility, if the host names in both domains are unique, is to use a WINS server for each site (and let the clients point to it) and let them replicate with each other.
0
 
markithomasAuthor Commented:
thanks, that seems to work after a quick test, is there a way to update the dns suffixes automatically with dhcp?  I don't fancy changing all the machines individually.  I don't fancy the idea of WINS, it seems a bit retro, like going back to NT 4 but if thats what it takes then thats what it needs.
0
 
Mark PavlakCommented:
look in the settings of the Hardware and make sure icmp is turned on.
0
 
oBdACommented:
Not with DHCP, sorry; this applies to Server 2003, but might work with XP clients as well:
New group policies for DNS in Windows Server 2003
http://support.microsoft.com/?kbid=294785

If this doesn't work for XP, here's (among other methods) a VB script that you could use in a GPO as computer(!) startup script:
How to configure a domain suffix search list on the Domain Name System clients
http://support.microsoft.com/?kbid=275553

As for WINS, if you don't use it, make sure NetBIOS over TCP/IP is disabled, as  you'll have the NetBIOS name resolution broadcast traffic otherwise. If you're using Exchange, you might want to reconsider the use of WINS, though:
Exchange Server 2003 and Exchange 2000 Server require NetBIOS name resolution for full functionality
http://support.microsoft.com/?kbid=837391
0
 
camacho_marcoCommented:
split points :)
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now