Replication and licening

Hi guys n gals,

I is having a problem with a new network i have setup. It is a second DC in a 2000 domain. The new server is on a different private lan. It has its own internal lan, which all of its local clients live on. It had an ip on the other office network, which is provided through RRAS (there is NAT providing general web access). Through this link i was able to join the remote server to the existing domain and perform all of the initial accounts replication.

We have now put all of the client pc's in on the remote network, and it basically works. Every now and again tho a user gets a message about not being able to access a file or other networked resource. This i have traced to a licening issue. The remote server doesn't have a list of all the licences that have been purchased. If i add some CAL licences on the remote server the licences appear in the domain, but this information is not on the remote server, despite it being the server that i added them from.

There are a lot of messages in the event log of the local DC along the lines of

Source: NTDS KCC
Category: Knowlege Consistency
Event ID: 1265
Computer DC1


The attempt to establish a replication link with parameters

Partition: DC=edu2000,DC=com
Source DSA DN: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=edu2000,DC=com
Source DSA Address: 2eb3d943-f107-4aef-b5f6-9fdf69a61cc0._msdcs.edu2000.com
Inter-site Transport (if any):

failed with the following status:

The RPC server is unavailable.

---

Does anyone know what i can do to fix this problem?

Thanks in advance.

Richard

 

How do you have yoru active directory configured? Do you have seperate sites defined with different subnets? With your type of connection, I would and use SMTP to allow the KCC to work properly. SMTP will ensure messages get acrossed the link eventually, where RPC could fail for hours on end, and maybe never work.
You may also want to consider moving the the connections between the 2 sites to a hardware configuration, i.e. cisco VPN solution. This may help to ensure the link stays up, even if the server is down.

 

Multi-homedness

Turns out to be fairly simple in the end. Problem was caused by the fact that the DC at one end was multi-homed (always a bad idea) and poor routing tables. Correct these and bobs your mothers brother!

Thanks for the ideas Bursley.

Some guy-you know?!