Trust thru firewall

[TJM]

I am in the process of setting up a new office (DomainB) that is connected
to our main office (DomainA) thru a firewall (Watchgaurd at both ends). The
new office is a separate AD Domain. Ultimately we want both offices to be
the same domain but for now we need to get both linked as quickly as
possible. I want to setup a trust but am having problems.

We still have WINS running at both offices and have added each domains WINS
servers as replication partners. From the main office we can see both
domains when we browse the network, but the new office can't see the main
office. I can ping to from one offce to the other, but if I ping
server.domainB from domainA I get a response of server.domainA with the
correct IP address from DomainB.

If I try to setup the trust the DC on the other domain can not be found.

What am I doing wrong?

Tim

 

[tkid]

-----Original Message-----
I am in the process of setting up a new office (DomainB) that is connected
to our main office (DomainA) thru a firewall (Watchgaurd at both ends). The
new office is a separate AD Domain. Ultimately we want both offices to be
the same domain but for now we need to get both linked as quickly as
possible. I want to setup a trust but am having problems.

We still have WINS running at both offices and have added each domains WINS
servers as replication partners. From the main office we can see both
domains when we browse the network, but the new office can't see the main
office. I can ping to from one offce to the other, but if I ping
server.domainB from domainA I get a response of server.domainA with the
correct IP address from DomainB.

If I try to setup the trust the DC on the other domain can not be found.

What am I doing wrong?

Tim


.
Make sure that the domain is resolved in the hosts file.

Specifically, make sure that the domain controller of the
other domain is in the hosts file. I.E. The hosts file
itself has instructions on how to do this...

 

[straight]

You can disalbe the firewall to see if the firewall blocks some TCP/UDP
ports.

 

[Bob Qin [MSFT]]

Hi Tim,

Thanks for your posting here.

Please make sure that Windows Internet Name Service (WINS), Domain Name
System (DNS), or the LMHOSTS file is configured correctly to locate the
PDC, and that TCP/IP is configured correctly on all of the domain
controllers that are involved.

For additional information about DNS, click the article numbers below to
view the articles in the Microsoft Knowledge Base:

291382.KB.EN-US: Frequently Asked Questions About Windows 2000 DNS
http://support.microsoft.com/?id=291382

237675.KB.EN-US: Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/?id=237675

For additional information about the LMHOSTS file, click the article
numbers below to view the articles in the Microsoft Knowledge Base:

101927.KB.EN-US: The Lmhosts File for TCP/IP in Windows
http://support.microsoft.com/?id=101927

180094.KB.EN-US: How to Write an LMHOSTS File for Domain Validation
http://support.microsoft.com/?id=180094

For more information about WINS, type "WINS" (without the quotation marks)
on the Search tab in Windows 2000 Help, and then click the appropriate
topic.

For more information about configuring TCP/IP, type "TCP/IP" (without the
quotation marks) on the Search tab in Windows 2000 Help, click Configure
TCP/IP, and then click the appropriate topic.

Thank your for using our newsgroup.

Regards,
Bob Qin
Product Support Services
Microsoft Corporation

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.