Looks like your DNS settings are probably the culprit, you never want to
point your Domain Controllers (or your clients for that matter) to an ISP
for DNS, then you won't have any SRV (Resource DNS Records) registered, you
will be looking to the internet to find your Domain Controllers, this will
cause slow bootups and logins and definitely cause a problem setting up
trusts.
Setting up and configuring DNS resolution in Windows 200x domains is very
important.
1. Verify that you have DNS running on your Windows 2000 Domain Controllers
and that they have a forward lookup zone for their domain. So one would
have a forward lookup zone of DHS.ORG.ZA and the other would have
DURBANHIGHSCHOOL.CO.ZA
2. Point all Network Adapters in the servers to themselves for DNS only and
verify it is registering it's records (not only host records but resource
or srv records in the _msdcs, _sites, _tcp and _udp folders.
3. Create secondary zones for each other and load the zone.
4. If you use DHCP for your clients, configure your DHCP Option 006 DNS
Servers to point to the Domain
Controller for DNS only. So that when your clients obtain an IP address,
they also get the address of the internal DNS server only.
5. Configure Forwarders to your ISP DNS servers inside DNS, on the
properties of the server. This way anything your internal DNS server
doesn't know the IP address of, it can go ask your ISP on behalf of your
clients.
Anything you need to know about DNS but were afraid to ask can be found at
www.microsoft.com/dns. Good luck!
Best Regards,
Kristin Thomas, MCSE, MCP
Microsoft Enterprise Network Support
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.
--------------------
| Thread-Topic: Tale of Two Domains
| thread-index: AcQNd5Id8/aOBrABRk+t/Et+3gXAaQ==
| X-Tomcat-NG: microsoft.public.win2000.networking
| From: "=?Utf-8?B?R3JhaGFtIEZsZWlzY2hlcg==?="
<
[email protected]>
| References: <
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
| Subject: RE: Tale of Two Domains
| Date: Thu, 18 Mar 2004 22:01:07 -0800
|
| Still does the same thing - our settings are as follows and we have tried
different combinations:
The one system is as follows:
Computer Name: SERVER
DNS Host Name: SERVER.DHS.ORG.ZA
DNS Domain Name: DHS.ORG.ZA
System info : Windows 2000 Server (Build 2195)
The other older system is
Computer Name: DHS
DNS Host Name: DHS.DURBANHIGHSCHOOL.CO.ZA
DNS Domain Name: DURBANHIGHSCHOOL.CO.ZA
System info : Windows 2000 Server (Build 2195)
Server we assigned an IP of 192.168.0.100
DHS we assigned an IP of 196.168.0.100
The servers failed to see each other under these conditions and would not
connect via Domains & Trusts
We then tried putting them on the same IP range Server: 196.168.0.101 &
DHS: 196.168.0.100
Still this did not help but at least they could see each other and the
shares. I have installed all components such as dns and wins and set them
up using default settings - have I done something wrong in these possibly?
What components are necessary to establish a trust relationship
successfully? On both computers the subnet is 255.255.255.0; the gateway is
196.168.0.200; and the DNS is our service provider 196.22.196.3 could there
be a problem with one of these settings?
We have also been trying to setup group policy on the DHS server without
much success and suddenly after installing WINS the other day to solve this
problem the Group Policy started to function - was it the WINS that did
this? Could this be a symptom of a larger config problem? I didn't think it
would be this difficult to make two servers talk to each other but boy am
learning a lot about servers at the same time!
I hope that you can help because my brain is somewhat mussshhhy from this.
Thanks,
Graham
|
