2003 PDC emulator and Routing issues

[Achillesx]

Hi all,

wonder if anyone can help.

We have a 2003 Domain with 2003 servers dotted around in different locations in the UK.
Our PDC emulator is in location A.
We have a Domain controller in Location B.
We have another site - Location C with a minor DC present.

The DC's in location A and B can see each other and are working fine.
The DC in Location C can see the DC in location B but CANNOT see the DC (or the network) in Location A - this is due to network infrastructure issues that cannot be resolved.

My question..
As the DC in location C cannot see the PDC emulator we are a bit stuck. Basically it isnt working properly.
Is there any way to use the DC in location B to either forward requests to location A or to mimic the PDC emulator role (Without actually moving the PDC emulator role).
Or can anyone see a way around this without actually moving the PDC emulator role.
I repeat that this routing issue cannot physically be resolved so we need a workaround.

Hope this makes sense

Cheers

N

 

[ntinlin]

Can't think of any workaround.

What would be the problem with moving the role? In a W2003 network all PDC emulator role does pretty much is take all password changes and act as last lookup if the local DC can't match the password.

Doesn't take a lot of bandwidth.

Neill

 

[Achillesx]

Hi, thanks for the reply.

If we move the role some other sites will stop working.

I am planning to move the role - however we will have to make (rather, get BT to make) some routing changes on our networks.
Which will probably take time.

I was seeing whether there was some sort out a workaround in the meantime!

Cheers

N

 

[MTVW]

How are your sites and services setup?

 

[Achillesx]

The Server has been put into the correct site in AD (with the correct IP Address range) however, as the DC at location C cant see the PDC Emulator it doesnt synchronize.