Second Server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have 2 windows2k spk4 in my company.
The first server is my main domain (quijano.local) and the second is (exchange.local).
When I installed the second server I put in the same forest of Quijano.local. I check dcdiag and netdiag and everything is ok.
From the second server (exchange.local) I can connect to the ADUC of the primary server (quijano.local), but when I try to connect to the ADUC of the second server (exchange.local) from the primary server (quijano.local) I received the message "The server is not operational".

Also, I can to do ping of qyaserver.quijano.local, but I can' to do ping of qyaexch.exchange.local, in another word I can't ping of FQDN of my second server, the name is not resolve. Why ?

The replication between domain is not working. Both DNS are Active Diretory Integration zone.

Please help me.
If you need more information please let me know.

Thanks.
Juab B.
 
In
Juan B. said:
Hi,

I have 2 windows2k spk4 in my company.
The first server is my main domain (quijano.local) and the second is
(exchange.local).
When I installed the second server I put in the same forest of
Quijano.local. I check dcdiag and netdiag and everything is ok.
From the second server (exchange.local) I can connect to the ADUC of
the primary server (quijano.local), but when I try to connect to the
ADUC of the second server (exchange.local) from the primary server
(quijano.local) I received the message "The server is not
operational".

Also, I can to do ping of qyaserver.quijano.local, but I can' to do
ping of qyaexch.exchange.local, in another word I can't ping of FQDN
of my second server, the name is not resolve. Why ?

The replication between domain is not working. Both DNS are Active
Diretory Integration zone.

Please help me.
If you need more information please let me know.

Thanks.
Juab B.
Click to expand...

AD Integrated zones ONLY replicate between servers that are part of the same
domain under W2k. This is because that info is stored in the Domain NC of
the AD database (one of 3 partitions in the database). In W2k3, there is a
feature to replicate this data to other application partitions in AD to
different domains.

You're best bet is to have a secondary zone copy of each other on each
other's DNS server since you have two separate domains.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thanks Ace for your answer.

Ok, I would like to explain more in what is my gold. I try to establish a redundant environment, when one server is down the other srever could replace and viceversa.
What is the best way to do that ?

When your said me that the best bet is to have a secondary zone copy of each other on each
other's DNS server, what is mean ? In my main server (quijano.local) I have the following in the Forward Lookup Zones:

QUIJANO.local ----> This is my main server.
_msds
_sites
_tcp
_udp
(same as parent folder) Satrt of Authority [70], qyaserver.quijano.local, admi......
(same as parent folder) Name Server qyaserver.quijano.local
(same as parent folder) Host 192.168.1.3

What I need to my main server (quijano.local) can see the second server (exchange.local) ?

Other suggestion can be that I set to my second server as a New DC, but in the same Tree of the Quijano.local ? This way both server can see and replicate it ? Please advice me what can I do.

Thank you for your help.

Juan B.

----- Ace Fekay [MVP] wrote: -----

In
Juan B. said:
Hi,
The first server is my main domain (quijano.local) and the second is
(exchange.local).
When I installed the second server I put in the same forest of
Quijano.local. I check dcdiag and netdiag and everything is ok.
From the second server (exchange.local) I can connect to the ADUC of
the primary server (quijano.local), but when I try to connect to the
ADUC of the second server (exchange.local) from the primary server
(quijano.local) I received the message "The server is not
operational".
ping of qyaexch.exchange.local, in another word I can't ping of FQDN
of my second server, the name is not resolve. Why ?
If you need more information please let me know.
Juab B.
Click to expand...

AD Integrated zones ONLY replicate between servers that are part of the same
domain under W2k. This is because that info is stored in the Domain NC of
the AD database (one of 3 partitions in the database). In W2k3, there is a
feature to replicate this data to other application partitions in AD to
different domains.

You're best bet is to have a secondary zone copy of each other on each
other's DNS server since you have two separate domains.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Juan B. said:
Thanks Ace for your answer.

Ok, I would like to explain more in what is my gold. I try to
establish a redundant environment, when one server is down the other
srever could replace and viceversa.
What is the best way to do that ?

When your said me that the best bet is to have a secondary zone copy
of each other on each
other's DNS server, what is mean ? In my main server (quijano.local)
I have the following in the Forward Lookup Zones:

QUIJANO.local ----> This is my main server.
_msds
_sites
_tcp
_udp
(same as parent folder) Satrt of Authority [70],
qyaserver.quijano.local, admi...... (same as parent folder)
Name Server qyaserver.quijano.local (same as parent
folder) Host 192.168.1.3

What I need to my main server (quijano.local) can see the second
server (exchange.local) ?

Other suggestion can be that I set to my second server as a New DC,
but in the same Tree of the Quijano.local ? This way both server can
see and replicate it ? Please advice me what can I do.

Thank you for your help.

Juan B.
Click to expand...

I think we have a little misunderstanding here. Even if a different tree,
they are still in a different domain, correct? Then AD Integrated zones will
NOT REPLICATE using Windows 2000 because it does NOT support this.

As far as the zones, on the server hosting the quijano.local zone, create a
Secondary Zone called exchange.local. Tell it in the wizard when you create
it that the Master Server's IP address is the server hosting the
exchange.local zone.

Then on the server hosting the exchange.local zone, create a Secondary Zone
called quijano.local. Tell it in the wizard when you create it that the
Master Server's IP address is the server hosting the quijano.local zone.

I hope this makes sense. This way you will have a copy of the zone on each
others' servers.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Juan B. said:
Thanks Ace for your help.

I resolved my problem.

Thanks a lot.

Juan B.
Click to expand...

Glad I could help out.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top