I manage a network with 3 sites in multiple cities, I have a domain controller is Site C that after a reboot, it will talk over the WAN (VPN to Sites A and B) for about 5 days, then just stop. It won't replicate, answer any requests from any of the other sites, it will how ever answer requests from anything on it's network.
When I try to RDP into it from over the WAN, it gives me the blue screen before the login box pops up, hangs, then disconnects, backupExec will send e-mails via the exchange server with the attached error log during those 5 days, then stop, AD replication also works during these days, then stops as well.
Here is a quick layout of the network
Site A
2 domain controllers
Site B
1 domain controller
Exchange
Site C
1 domain controller
Terminal Server
VPN between each site so:
Site A VPNs to Sites B and C
Site B VPNs to Sites A and C
Site C VPNs to Sites A and B
It's not a WAN issue as I can RDP into the terminal server from over the WAN and then hop into the Domain Controller.
Scott Heath
AIM: orange7288
SprintPCS ReadyLink? IM ME
When I try to RDP into it from over the WAN, it gives me the blue screen before the login box pops up, hangs, then disconnects, backupExec will send e-mails via the exchange server with the attached error log during those 5 days, then stop, AD replication also works during these days, then stops as well.
Here is a quick layout of the network
Site A
2 domain controllers
Site B
1 domain controller
Exchange
Site C
1 domain controller
Terminal Server
VPN between each site so:
Site A VPNs to Sites B and C
Site B VPNs to Sites A and C
Site C VPNs to Sites A and B
It's not a WAN issue as I can RDP into the terminal server from over the WAN and then hop into the Domain Controller.
Scott Heath
AIM: orange7288
SprintPCS ReadyLink? IM ME
