Re: two problems of two trusted ad domains
- From: "mmccaws2" <mmccaws@xxxxxxxxxxx>
- Date: 13 Jul 2005 14:13:19 -0700
I'm not sure what ./share does for me. is there a knowledge link about
that option?
how do you use it your network?
Mike
Kevin D. Goodknecht Sr. [MVP] wrote:
> In news:1121190503.365625.85040@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
> mmccaws2 <mmccaws@xxxxxxxxxxx> posted this:
> > Read below
> >
> > Kevin D. Goodknecht Sr. [MVP] wrote:
> >> In news:1121109706.287131.299560@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
> >> mmccaws2 <mmccaws@xxxxxxxxxxx> posted this:
> >>> Sort of unusual DNS problem:
> >>>
> >>> Two forests domains are, AD1.here. and AD2.here.
> >>>
> >>> AD1.here. trusts AD2.here.
> >>>
> >>> host1.AD2.here tries to resolve host-1.AD1.here. and gets the
> >>> correct ip address however it resolves as host-1.AD1.here.
> >>>
> >>> also
> >>>
> >>> cannot create host1.AD2.here. Apparantly, even though the unrelated
> >>> organizations, other than they reside on the same network behind a
> >>> firewall, and one organization built their desktop with novell
> >>> client the other didn't, the only relationship is WINS and core
> >>> 'here' domain. Also, there is not DNS server at 'here' domain.
> >>>
> >>> Why is AD2.here. claiming that hose host-1.AD1.here. is actually
> >>> host-1.AD2.here.?
> >>
> >> Probably because AD2.here and AD1.here are both in the DNS suffix
> >> search list.
> > So I changed the dns search list to the following
> >
> > AD1.here
> > and
> > somerealdomainname.com
> > the search dns servers were
> > ip address of primaryAD1dnsserverip.AD1.here
> > and
> > ip address of primarydns.somerealdomainname.com
> >
> > then I searched for a servername at somerealdomainname.com
> > with debug on
> > it showed that it appended AD1.here to servername and didn't find an
> > answer, then appended somerealdomainname.com and correctly resolved it
> > correctly as servername.somerealdomainname.com. So by your logic it
> > should have incorrectly given the name servername.AD1.here because it
> > was in the search list.
>
> If host1 exists in both AD1.here and AD2.here which ever suffix that was
> searched first would resolve the name.
>
> >
> > So help me out here, why would two AD forest domains setup seperately
> > with only a one-way trust report names incorrectly belonging to
> > another domain. Is there some option to prevent this? Isn't there a
> > option somewhere to require FQDN in the answer? Is this a behavior
> > only in non-native AD forest?
>
> You can set up shares with the FQDN of the server it is on e.g
> \\host1.AD1.here.\share (notice the trailing "." in the server name) The
> trailing "." prevents the DNS client from appending the DNS suffix search
> list.
>
>
>
>
>
> --?
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
.
- References:
- two problems of two trusted ad domains
- From: mmccaws2
- Re: two problems of two trusted ad domains
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: two problems of two trusted ad domains
- From: mmccaws2
- Re: two problems of two trusted ad domains
- From: Kevin D. Goodknecht Sr. [MVP]
- two problems of two trusted ad domains
- Prev by Date: Re: DNS IP settings
- Next by Date: Re: Can't Ping GUID--AD replication problems
- Previous by thread: Re: two problems of two trusted ad domains
- Next by thread: DNS Error 6702
- Index(es):
Relevant Pages
|
