We just did a migration from Windows server 2003 sp2 to Small business server 2008. The migration did not, and is not going well. There are global catalog issues, specifically the following errors repeat every hour on the 2008 server:
Active Directory Domain Services has located a global catalog in the following site.
Global catalog:
\\SERVER.domain.local
Site:
Default-First-Site-Name
-----------------------------------------
Active Directory Domain Services attempted to communicate with the following global catalog and the attempts were unsuccessful.
Global catalog:
\\SERVER.domain.local
The operation in progress might be unable to continue. Active Directory Domain Services will use the domain controller locator to try to find an available global catalog server.
Additional Data
Error value:
1722 The RPC server is unavailable.
-----------------------------------------------------
Active Directory Domain Services was unable to establish a connection with the global catalog.
Additional Data
Error value:
8430 The directory service encountered an internal failure.
Internal ID:
3200ce6
User Action:
Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the nltest utility to diagnose this problem.
--------------------------------------------------
There do not appear to be any error messages relating to the GC on the 2003 server. I have follow the diagnostics per this document
Both servers can communicate on port 389 but not 3268. There are no firewalls between them. All other replication is working fine.
On the 2008 server if you ping it by name you get a response like this:
Pinging SERVER.domain.local [fe80::7ce7:57fd:8dea:2e8a%10] from fe80::7ce7:57
fd:8dea:2e8a%10 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.
Ping statistics for fe80::7ce7:57fd:8dea:2e8a%10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
The server does not respond to itself with an ipv4 address.
Pinging from the other server gets this response:
Pinging server.domain.local [10.0.0.25] with 32 bytes of data:
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Ping statistics for 10.0.0.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Starting over is not an option at this time as one of our techs removed exchange from the old server before testing what would happen if the server was disconnected from the network. We had to manually recreate the GC on the new server (53 users).
SO as you can see this is a real CF.
Any serious suggestions?
Active Directory Domain Services has located a global catalog in the following site.
Global catalog:
\\SERVER.domain.local
Site:
Default-First-Site-Name
-----------------------------------------
Active Directory Domain Services attempted to communicate with the following global catalog and the attempts were unsuccessful.
Global catalog:
\\SERVER.domain.local
The operation in progress might be unable to continue. Active Directory Domain Services will use the domain controller locator to try to find an available global catalog server.
Additional Data
Error value:
1722 The RPC server is unavailable.
-----------------------------------------------------
Active Directory Domain Services was unable to establish a connection with the global catalog.
Additional Data
Error value:
8430 The directory service encountered an internal failure.
Internal ID:
3200ce6
User Action:
Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the nltest utility to diagnose this problem.
--------------------------------------------------
There do not appear to be any error messages relating to the GC on the 2003 server. I have follow the diagnostics per this document
Both servers can communicate on port 389 but not 3268. There are no firewalls between them. All other replication is working fine.
On the 2008 server if you ping it by name you get a response like this:
Pinging SERVER.domain.local [fe80::7ce7:57fd:8dea:2e8a%10] from fe80::7ce7:57
fd:8dea:2e8a%10 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.
Ping statistics for fe80::7ce7:57fd:8dea:2e8a%10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
The server does not respond to itself with an ipv4 address.
Pinging from the other server gets this response:
Pinging server.domain.local [10.0.0.25] with 32 bytes of data:
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Reply from 10.0.0.25: bytes=32 time<1ms TTL=128
Ping statistics for 10.0.0.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Starting over is not an option at this time as one of our techs removed exchange from the old server before testing what would happen if the server was disconnected from the network. We had to manually recreate the GC on the new server (53 users).
SO as you can see this is a real CF.
Any serious suggestions?
