> Hello PhilTeale,
>
> How did you connect the domains? Can you also post and unedited ipconfig
> /all from both.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm >
>
> > Hi Meinolf
> >
> > Thanks for your reply.
> >
> > We would love to rename the domain, but unfortunately it is not under
> > our control.
> >
> > I have followed the steps in the document you linked to, and although
> > the secondary zones work, we still have the same problem; we cannot
> > ping the "domain" or "domain." domains from the WAN domain.
> >
> > nslookup of "domain." on the WAN domain does resolve to the domain
> > controller on the LAN domain, but still the AD Trust Wizard fails on
> > the WAN domain because it is not able to contact the LAN domain.
> >
> > Do you have any other ideas?
> >
> > Cheers
> >
> > Phil
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello PhilTeale,
> >>
> >> See here for DNS setup for a trust:
> >>
http://searchwinit.techtarget.com/expert/KnowledgebaseAnswer/0,289625> >> ,sid1_gci1101656,00.html
> >> Also your domain names should look like "domain.local" instead of
> >> using single lable domain names like domain. See here:
> >>
http://support.microsoft.com/kb/300684> >>
> >> Did you ever thought about renaming the domain?
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm> >>> Hi
> >>>
> >>> I am trying to establish a trust from a WAN domain to a domain on a
> >>> LAN. Network connectivity is established and confirmed.
> >>>
> >>> The problem I am experiencing is that I cannot ping the domain name
> >>> from the domain on the WAN. I have configured forwarders on the WAN
> >>> DNS and can ping individual servers on the LAN domain, but not the
> >>> domain name itself.
> >>>
> >>> Eg. I can ping server1.contoso. but not contoso. itself
> >>>
> >>> (To complicate matters, the LAN domain does not use RFC compliant
> >>> naming; it is called "contoso" (or "contso.", I am not sure of the
> >>> difference). I don't think that it is a problem as both are AD
> >>> domains, but I thought it best to point out.)
> >>>
> >>> I suspect the problem is actually with the LAN domain itself, as
> >>> when I log onto the domain controller server.contoso. I cannot ping
> >>> either "contoso" or "contoso."
> >>>
> >>> My question is, what records need to be present in DNS to allow me
> >>> to ping the domain name from the domain controller? In all our
> >>> other domains, we can ping the domain name, eg example.com or
> >>> example.zone.
> >>>
> >>> If run nslookup on the LAN domain controller ("server1.contoso") and
> >>> enter "contso" it returns non-existant domain, however if I enter
> >>> "contso." then it returns the IP address of the DNS server. This
> >>> demonstrates that DNS is somewhat working.
> >>>
> >>> I understand that we will not be able to establish the trust until
> >>> both servers can contact a domain controller on the other domain by
> >>> resolving the domain name.
> >>>
> >>> I hope someone is able to help.
> >>>
> >>> Regards
> >>>
> >>> Phil
> >>>
>
>
>