|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Exchange 2003 Outage IssuesI have a Windows 2003 network with (2) domain controllers, both setup as a
global catalog & DNS server. However one has all the FSMO roles. Lsat week, when the primary DC/DNS server with the FSMO roles went down, all mail functionality ceased to work. I found this kind of odd since the other DC/DNS server was still up, and we could still reach the Internet. Once we got the main DC up and running, all was fine. However I'm worried that I may be missing something. Should we have seized the FSMO roles back to the backup DC/DNS server? Would this have kept us running? FYI, the primary DC has gone down before without any loss in mail functionality. Any thoughts? Thanks There will always be a delay for Exchange to switch to a different domain
controller. How long did you wait? -- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "circulent" <circul***@discussions.microsoft.com> wrote in message news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... >I have a Windows 2003 network with (2) domain controllers, both setup as a > global catalog & DNS server. However one has all the FSMO roles. > > Lsat week, when the primary DC/DNS server with the FSMO roles went down, > all > mail functionality ceased to work. I found this kind of odd since the > other > DC/DNS server was still up, and we could still reach the Internet. > > Once we got the main DC up and running, all was fine. However I'm worried > that I may be missing something. Should we have seized the FSMO roles back > to > the backup DC/DNS server? Would this have kept us running? FYI, the > primary > DC has gone down before without any loss in mail functionality. > > Any thoughts? > > Thanks The outage began at 7:30 AM. By 6 PM Exchange was still out of commission
even though the 2nd DC/DNS server was always up and running. Weird huh? Thoughts? Show quoteHide quote "Ed Crowley [MVP]" wrote: > There will always be a delay for Exchange to switch to a different domain > controller. How long did you wait? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... > >I have a Windows 2003 network with (2) domain controllers, both setup as a > > global catalog & DNS server. However one has all the FSMO roles. > > > > Lsat week, when the primary DC/DNS server with the FSMO roles went down, > > all > > mail functionality ceased to work. I found this kind of odd since the > > other > > DC/DNS server was still up, and we could still reach the Internet. > > > > Once we got the main DC up and running, all was fine. However I'm worried > > that I may be missing something. Should we have seized the FSMO roles back > > to > > the backup DC/DNS server? Would this have kept us running? FYI, the > > primary > > DC has gone down before without any loss in mail functionality. > > > > Any thoughts? > > > > Thanks > > > Well, that's not good. Are both DCs in the same AD site? Same domain?
-- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "circulent" <circul***@discussions.microsoft.com> wrote in message news:A8076AA6-0296-4086-9E32-5E98E3410933@microsoft.com... > The outage began at 7:30 AM. By 6 PM Exchange was still out of commission > even though the 2nd DC/DNS server was always up and running. > > Weird huh? > > Thoughts? > > "Ed Crowley [MVP]" wrote: > >> There will always be a delay for Exchange to switch to a different domain >> controller. How long did you wait? >> -- >> Ed Crowley MVP >> "There are seldom good technological solutions to behavioral problems." >> .. >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... >> >I have a Windows 2003 network with (2) domain controllers, both setup as >> >a >> > global catalog & DNS server. However one has all the FSMO roles. >> > >> > Lsat week, when the primary DC/DNS server with the FSMO roles went >> > down, >> > all >> > mail functionality ceased to work. I found this kind of odd since the >> > other >> > DC/DNS server was still up, and we could still reach the Internet. >> > >> > Once we got the main DC up and running, all was fine. However I'm >> > worried >> > that I may be missing something. Should we have seized the FSMO roles >> > back >> > to >> > the backup DC/DNS server? Would this have kept us running? FYI, the >> > primary >> > DC has gone down before without any loss in mail functionality. >> > >> > Any thoughts? >> > >> > Thanks >> >> >> yes sir
Show quoteHide quote "Ed Crowley [MVP]" wrote: > Well, that's not good. Are both DCs in the same AD site? Same domain? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:A8076AA6-0296-4086-9E32-5E98E3410933@microsoft.com... > > The outage began at 7:30 AM. By 6 PM Exchange was still out of commission > > even though the 2nd DC/DNS server was always up and running. > > > > Weird huh? > > > > Thoughts? > > > > "Ed Crowley [MVP]" wrote: > > > >> There will always be a delay for Exchange to switch to a different domain > >> controller. How long did you wait? > >> -- > >> Ed Crowley MVP > >> "There are seldom good technological solutions to behavioral problems." > >> .. > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... > >> >I have a Windows 2003 network with (2) domain controllers, both setup as > >> >a > >> > global catalog & DNS server. However one has all the FSMO roles. > >> > > >> > Lsat week, when the primary DC/DNS server with the FSMO roles went > >> > down, > >> > all > >> > mail functionality ceased to work. I found this kind of odd since the > >> > other > >> > DC/DNS server was still up, and we could still reach the Internet. > >> > > >> > Once we got the main DC up and running, all was fine. However I'm > >> > worried > >> > that I may be missing something. Should we have seized the FSMO roles > >> > back > >> > to > >> > the backup DC/DNS server? Would this have kept us running? FYI, the > >> > primary > >> > DC has gone down before without any loss in mail functionality. > >> > > >> > Any thoughts? > >> > > >> > Thanks > >> > >> > >> > > > fyi, I rebooted the main DC today (since its back up and running), and
exchange was still working fine since the 2nd DC/DNS server was still up. odd huh? Show quoteHide quote "Ed Crowley [MVP]" wrote: > Well, that's not good. Are both DCs in the same AD site? Same domain? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:A8076AA6-0296-4086-9E32-5E98E3410933@microsoft.com... > > The outage began at 7:30 AM. By 6 PM Exchange was still out of commission > > even though the 2nd DC/DNS server was always up and running. > > > > Weird huh? > > > > Thoughts? > > > > "Ed Crowley [MVP]" wrote: > > > >> There will always be a delay for Exchange to switch to a different domain > >> controller. How long did you wait? > >> -- > >> Ed Crowley MVP > >> "There are seldom good technological solutions to behavioral problems." > >> .. > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... > >> >I have a Windows 2003 network with (2) domain controllers, both setup as > >> >a > >> > global catalog & DNS server. However one has all the FSMO roles. > >> > > >> > Lsat week, when the primary DC/DNS server with the FSMO roles went > >> > down, > >> > all > >> > mail functionality ceased to work. I found this kind of odd since the > >> > other > >> > DC/DNS server was still up, and we could still reach the Internet. > >> > > >> > Once we got the main DC up and running, all was fine. However I'm > >> > worried > >> > that I may be missing something. Should we have seized the FSMO roles > >> > back > >> > to > >> > the backup DC/DNS server? Would this have kept us running? FYI, the > >> > primary > >> > DC has gone down before without any loss in mail functionality. > >> > > >> > Any thoughts? > >> > > >> > Thanks > >> > >> > >> > > > What shows in Exchange System Manger, in the server's Direcotry Access
properties page? Also there's a periodic event log message (MSExchangeDSAccess 2080) that Exchange writes showing what domain controllers it is using with some code numbers that tell what roles it sees and whether they're in-site or not. You might want to look for that and go backward in time and see if there are any changes. -- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "circulent" <circul***@discussions.microsoft.com> wrote in message news:D92BCE13-022B-4284-9A0A-AEAC4FED7A6F@microsoft.com... > fyi, I rebooted the main DC today (since its back up and running), and > exchange was still working fine since the 2nd DC/DNS server was still up. > > odd huh? > > "Ed Crowley [MVP]" wrote: > >> Well, that's not good. Are both DCs in the same AD site? Same domain? >> -- >> Ed Crowley MVP >> "There are seldom good technological solutions to behavioral problems." >> .. >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:A8076AA6-0296-4086-9E32-5E98E3410933@microsoft.com... >> > The outage began at 7:30 AM. By 6 PM Exchange was still out of >> > commission >> > even though the 2nd DC/DNS server was always up and running. >> > >> > Weird huh? >> > >> > Thoughts? >> > >> > "Ed Crowley [MVP]" wrote: >> > >> >> There will always be a delay for Exchange to switch to a different >> >> domain >> >> controller. How long did you wait? >> >> -- >> >> Ed Crowley MVP >> >> "There are seldom good technological solutions to behavioral >> >> problems." >> >> .. >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... >> >> >I have a Windows 2003 network with (2) domain controllers, both setup >> >> >as >> >> >a >> >> > global catalog & DNS server. However one has all the FSMO roles. >> >> > >> >> > Lsat week, when the primary DC/DNS server with the FSMO roles went >> >> > down, >> >> > all >> >> > mail functionality ceased to work. I found this kind of odd since >> >> > the >> >> > other >> >> > DC/DNS server was still up, and we could still reach the Internet. >> >> > >> >> > Once we got the main DC up and running, all was fine. However I'm >> >> > worried >> >> > that I may be missing something. Should we have seized the FSMO >> >> > roles >> >> > back >> >> > to >> >> > the backup DC/DNS server? Would this have kept us running? FYI, the >> >> > primary >> >> > DC has gone down before without any loss in mail functionality. >> >> > >> >> > Any thoughts? >> >> > >> >> > Thanks >> >> >> >> >> >> >> >> >> Also see this KB:
http://support.microsoft.com/kb/316300 -- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "circulent" <circul***@discussions.microsoft.com> wrote in message news:D92BCE13-022B-4284-9A0A-AEAC4FED7A6F@microsoft.com... > fyi, I rebooted the main DC today (since its back up and running), and > exchange was still working fine since the 2nd DC/DNS server was still up. > > odd huh? > > "Ed Crowley [MVP]" wrote: > >> Well, that's not good. Are both DCs in the same AD site? Same domain? >> -- >> Ed Crowley MVP >> "There are seldom good technological solutions to behavioral problems." >> .. >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:A8076AA6-0296-4086-9E32-5E98E3410933@microsoft.com... >> > The outage began at 7:30 AM. By 6 PM Exchange was still out of >> > commission >> > even though the 2nd DC/DNS server was always up and running. >> > >> > Weird huh? >> > >> > Thoughts? >> > >> > "Ed Crowley [MVP]" wrote: >> > >> >> There will always be a delay for Exchange to switch to a different >> >> domain >> >> controller. How long did you wait? >> >> -- >> >> Ed Crowley MVP >> >> "There are seldom good technological solutions to behavioral >> >> problems." >> >> .. >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... >> >> >I have a Windows 2003 network with (2) domain controllers, both setup >> >> >as >> >> >a >> >> > global catalog & DNS server. However one has all the FSMO roles. >> >> > >> >> > Lsat week, when the primary DC/DNS server with the FSMO roles went >> >> > down, >> >> > all >> >> > mail functionality ceased to work. I found this kind of odd since >> >> > the >> >> > other >> >> > DC/DNS server was still up, and we could still reach the Internet. >> >> > >> >> > Once we got the main DC up and running, all was fine. However I'm >> >> > worried >> >> > that I may be missing something. Should we have seized the FSMO >> >> > roles >> >> > back >> >> > to >> >> > the backup DC/DNS server? Would this have kept us running? FYI, the >> >> > primary >> >> > DC has gone down before without any loss in mail functionality. >> >> > >> >> > Any thoughts? >> >> > >> >> > Thanks >> >> >> >> >> >> >> >> >> I will take a look and see what I come up with. thanks Ed
Show quoteHide quote "Ed Crowley [MVP]" wrote: > Also see this KB: > http://support.microsoft.com/kb/316300 > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:D92BCE13-022B-4284-9A0A-AEAC4FED7A6F@microsoft.com... > > fyi, I rebooted the main DC today (since its back up and running), and > > exchange was still working fine since the 2nd DC/DNS server was still up. > > > > odd huh? > > > > "Ed Crowley [MVP]" wrote: > > > >> Well, that's not good. Are both DCs in the same AD site? Same domain? > >> -- > >> Ed Crowley MVP > >> "There are seldom good technological solutions to behavioral problems." > >> .. > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:A8076AA6-0296-4086-9E32-5E98E3410933@microsoft.com... > >> > The outage began at 7:30 AM. By 6 PM Exchange was still out of > >> > commission > >> > even though the 2nd DC/DNS server was always up and running. > >> > > >> > Weird huh? > >> > > >> > Thoughts? > >> > > >> > "Ed Crowley [MVP]" wrote: > >> > > >> >> There will always be a delay for Exchange to switch to a different > >> >> domain > >> >> controller. How long did you wait? > >> >> -- > >> >> Ed Crowley MVP > >> >> "There are seldom good technological solutions to behavioral > >> >> problems." > >> >> .. > >> >> > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> news:B0CD4D58-B1C3-44E6-BF7C-3F070F06BC7D@microsoft.com... > >> >> >I have a Windows 2003 network with (2) domain controllers, both setup > >> >> >as > >> >> >a > >> >> > global catalog & DNS server. However one has all the FSMO roles. > >> >> > > >> >> > Lsat week, when the primary DC/DNS server with the FSMO roles went > >> >> > down, > >> >> > all > >> >> > mail functionality ceased to work. I found this kind of odd since > >> >> > the > >> >> > other > >> >> > DC/DNS server was still up, and we could still reach the Internet. > >> >> > > >> >> > Once we got the main DC up and running, all was fine. However I'm > >> >> > worried > >> >> > that I may be missing something. Should we have seized the FSMO > >> >> > roles > >> >> > back > >> >> > to > >> >> > the backup DC/DNS server? Would this have kept us running? FYI, the > >> >> > primary > >> >> > DC has gone down before without any loss in mail functionality. > >> >> > > >> >> > Any thoughts? > >> >> > > >> >> > Thanks > >> >> > >> >> > >> >> > >> > >> > >> > > > 
Other interesting topics
Exch 2K d:/M: drive fills up, contracts and fills up (over and ove
Not able to route smtp outboud traffice from exch 2003 server via Ignore an SMTP address in the domain body of email message gets converted to txt attachement Ex2007 sp1 Exchange 2003 with OWA and Verisign Digital ID's How to notify users of the result of the mailbox policies run? Some email not received Bad page link error Exchange 2003 - SMTP quota Exchange 2007 Managed Content Settings Exclude sub folders |
|||||||||||||||||||||||
