Hi here's my problem first we got one domain ( domain men.local) another
domain not in the same forest (women.internal) both trust each other the user
log into domain women.internal and acces ressource in domain men.local
here's the config

men.local
fqdn of the 1 dc is server.men.local
ip adress 172.16.1.114
gateway 172.16.1.1
dns 172.16.1.114
dns 172.16.1.76 (locate in woman.internal)

2 DC server2.men.local
ip 172.16.1.140
gateway 172.16.1.1
dns 172.16.1.114
dns 172.16.1.76 (locate in woman.internal)

wkstation test.woman.internal
ip 172.31.149.19
gateway 172.31.148.1
dns 172.16.1.76
dns 172.16.1.124
wins 172.16.1.124




the workstation could ping and resolve server1 and server2 in domain
men.local
but they cannot acces the share \\server1\share

if we inverse the DNS he could resolve and acces the share but that cause
problem in my dc replication


any idea

Ron wrote:
> Hi here's my problem first we got one domain ( domain men.local)
> another domain not in the same forest (women.internal) both trust
> each other the user log into domain women.internal and acces
> ressource in domain men.local here's the config
>
> men.local
> fqdn of the 1 dc is server.men.local
> ip adress 172.16.1.114
> gateway 172.16.1.1
> dns 172.16.1.114
> dns 172.16.1.76 (locate in woman.internal)
>
> 2 DC server2.men.local
> ip 172.16.1.140
> gateway 172.16.1.1
> dns 172.16.1.114
> dns 172.16.1.76 (locate in woman.internal)
>
> wkstation test.woman.internal
> ip 172.31.149.19
> gateway 172.31.148.1
> dns 172.16.1.76
> dns 172.16.1.124
> wins 172.16.1.124
>
>
>
>
> the workstation could ping and resolve server1 and server2 in domain
> men.local
> but they cannot acces the share \\server1\share
>
> if we inverse the DNS he could resolve and acces the share but that
> cause problem in my dc replication

The problem is the servers and workstations in men.local must use only DNS
server in men.local, the servers and workstations in woman.internal must use
only the DNS servers in woman.internal. Don't mix DNS server in TCP/IP
properties that cannot resolve ALL names it needs. IOW, the men.local DNS
cannot resolve woman.internal, so don't use the woman.internal DNS on the
men.local clients.

Then you have to configure the DNS server in men.local to resolve the
woman.internal domain (and vice-versa) by either using a conditional
forwarder for woman.internal or a secondary zone from the woman.internal
DNS.

Conditional Forwarding in Windows Server 2003:
http://support.microsoft.com/kb/304491/en-us

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s
===================================
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/
http://support.wftx.us/
http://message.wftx.us/
===================================
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.oe.com/OEBackup/Default.aspx
===================================