Issues on new WAN

  • Thread starter Thread starter James
  • Start date Start date
J

James

I am working on a few issues on a new WAN. If anyone can help with these I
would be appreciative.

I have 3 sites with their own domains. Native Win2000 domains named
office1.domain.com, office2.domain.com and office3.domain.com. Our external
presence hosted outside the company is domain.com

Each domain has its own WINS, DNS and DHCP servers. WINS is currently set
up with a push pull relationship between sites.

I can browse each domain through network neighbourhood and see the servers
on each. There are two problems. I cannot see any Win98 boxes even though
they are set up to register with the WINS server on their domain. Secondly,
and more importent, access is only possible for me as administrator since I
have not got any permissions accross domains. The reason for this is I
can't seem to set up any trusts. If I go into domains and trusts and try to
set up trusts I get the message that the domain cannot be contacted, even
though it appears in network neighbourhood ?

Thank you in advance.

Regards, James
 
The DNS per domains must have the other DNS from the other domains listed in
their Forwarder's List. Right now you have each Domain looking at its own
DNS which has no knowledge of the other domains.

There is something fishy with your names as well. What you indicated is that
they are all "child" domains (office#) with the same parent domain
(domain.com) yet it looks like you real have three distinct parent domains
that just *happen* to have the same name,...because, as you indicated there
is no "Trusts" in place,...meaning there is no
*single*,..*centralized*,...parent domain (domain.com).

If you had just normal independent domains at each site they would be
office1.com, office2.com, office3.com. Then you could setup a trust between
them.

I'm afraid you may be screwed by an improper AD design.
 
Thank you Phillip

And I thought I had planned naming well. But they were designed as 3
seperate networks that have only recently been able to be connected
together.

On the DNS side yes I have missed this although I can ping by both IP
address and machine name.

Is my naming going to bring me to a standstill with getting everything
working?

If I have to start from scratch at one of the smaller sites is it still best
to have seperate domains. This is what I was always taught but there must
be pros and cons for stick a remote network on the same domain.

Regards, James


Phillip Windell said:
The DNS per domains must have the other DNS from the other domains listed
in
their Forwarder's List. Right now you have each Domain looking at its own
DNS which has no knowledge of the other domains.

There is something fishy with your names as well. What you indicated is
that
they are all "child" domains (office#) with the same parent domain
(domain.com) yet it looks like you real have three distinct parent domains
that just *happen* to have the same name,...because, as you indicated
there
is no "Trusts" in place,...meaning there is no
*single*,..*centralized*,...parent domain (domain.com).

If you had just normal independent domains at each site they would be
office1.com, office2.com, office3.com. Then you could setup a trust
between
them.

I'm afraid you may be screwed by an improper AD design.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


James said:
I am working on a few issues on a new WAN. If anyone can help with these I
would be appreciative.

I have 3 sites with their own domains. Native Win2000 domains named
office1.domain.com, office2.domain.com and office3.domain.com. Our external
presence hosted outside the company is domain.com

Each domain has its own WINS, DNS and DHCP servers. WINS is currently
set
up with a push pull relationship between sites.

I can browse each domain through network neighbourhood and see the
servers
on each. There are two problems. I cannot see any Win98 boxes even
though
they are set up to register with the WINS server on their domain. Secondly,
and more importent, access is only possible for me as administrator since I
have not got any permissions accross domains. The reason for this is I
can't seem to set up any trusts. If I go into domains and trusts and try to
set up trusts I get the message that the domain cannot be contacted, even
though it appears in network neighbourhood ?

Thank you in advance.

Regards, James
Click to expand...
Click to expand...
 
Back
Top