Exchange 2003 Enterprise sp1 on proliant FE Server Exchange 2003 Enterprise on Dl360 w/MSA 500 Cluster A/P Windows 2000 Domain Please help My outlook users on remote subnets lose the ability to connectwith excange BE after I reboot domain controllers in the Hub network. The resolution is that I have to manually move the exchange services to the backup node. this resolves the problem immediately. I have changed my replication schedule on my remote DC's to be more fequent to try to resolve the problem. This has helped in my metro private hard wired bgp4 T1 circuits. The problem is still prevalant with wan links connected with ipsec tunnels. DC's are running in all subnets Please Help KP
That was Dl380 w MSA500 Cluster Sorry KP kp wrote: > Exchange 2003 Enterprise sp1 on proliant FE Server > Exchange 2003 Enterprise on Dl360 w/MSA 500 Cluster A/P > Windows 2000 Domain > > Please help > > My outlook users on remote subnets lose the ability to connectwith excange BE > after I reboot domain controllers in the Hub network. > > The resolution is that I have to manually move the exchange services to the > backup node. this resolves the problem immediately. > > I have changed my replication schedule on my remote DC's to be more fequent to > try to resolve the problem. > > This has helped in my metro private hard wired bgp4 T1 circuits. > > The problem is still prevalant with wan links connected with ipsec tunnels. > > DC's are running in all subnets Please Help KP > >
On Sat, 13 May 2006 22:20:31 -0700, kp wrote: >That was Dl380 w MSA500 Cluster >Sorry >KP > >kp wrote: > >> Exchange 2003 Enterprise sp1 on proliant FE Server >> Exchange 2003 Enterprise on Dl360 w/MSA 500 Cluster A/P >> Windows 2000 Domain >> >> Please help >> >> My outlook users on remote subnets lose the ability to connectwith excange >BE >> after I reboot domain controllers in the Hub network. >> >> The resolution is that I have to manually move the exchange services to the >> backup node. this resolves the problem immediately. >> >> I have changed my replication schedule on my remote DC's to be more fequent >to >> try to resolve the problem. >> >> This has helped in my metro private hard wired bgp4 T1 circuits. >> >> The problem is still prevalant with wan links connected with ipsec tunnels. >> >> DC's are running in all subnets > >Please Help > >KP >> >> This isn't an Exchange question. Talk this through with your network boys. They will go through what addresses and MAC's are being registered with DNS. Why is is that you're rebooting your DC's anyway? What have you got on them that's causing the reboot and do you have to reboot them at the same time?
