Exchange 2k + Win2k PDC Problem
Greetings: Two boxes, both W2kServer SP2 + every update under the sun. They are both domain controllers, but server 1 was the server used to create the domain, so it's the PDC (although do we still use that term with W2K?).
Greetings:
Two boxes, both W2kServer SP2 + every update under the sun. They are both domain controllers, but "server 1" was the server used to create the domain, so it's the PDC (although do we still use that term with W2K?). Anyways, on "server 2" exists Exchange 2000.
Problem: When I reboot "server 1", I cannot connect to my Exchange server with Outlook until "server 1" comes back up.
The answer seems obvious, but it has eluded me. My AD is running in native mode, as is Exchange 2k... which I would think with that level of AD integration that there would be no issue with Outlook finding the server SOMEWHERE in the AD, but for some reason, it doesn't know to query "server 2" when "server 1" aint there. Again, both servers are domain controllers.
Yes, my DNS/WINS and DHCP settings are all perfect. Name resolution on my LAN is not a problem. Anyhoo.... thanks in advance.
Two boxes, both W2kServer SP2 + every update under the sun. They are both domain controllers, but "server 1" was the server used to create the domain, so it's the PDC (although do we still use that term with W2K?). Anyways, on "server 2" exists Exchange 2000.
Problem: When I reboot "server 1", I cannot connect to my Exchange server with Outlook until "server 1" comes back up.
The answer seems obvious, but it has eluded me. My AD is running in native mode, as is Exchange 2k... which I would think with that level of AD integration that there would be no issue with Outlook finding the server SOMEWHERE in the AD, but for some reason, it doesn't know to query "server 2" when "server 1" aint there. Again, both servers are domain controllers.
Yes, my DNS/WINS and DHCP settings are all perfect. Name resolution on my LAN is not a problem. Anyhoo.... thanks in advance.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
I believe the problem revolves around the FSMO roles that the "PDC" allocates to itself when you start a new network. There are five roles: More detail can be found here.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q197132
We were discussing this at a rescent MOC course. The FSMO roles can be placed on other DC's, I think that the Infrastructure role is at fault. Although I'm not qualified (yet!) to help you with the transaction, I'm sure there is information on MS.com regarding changing the roles.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q197132
We were discussing this at a rescent MOC course. The FSMO roles can be placed on other DC's, I think that the Infrastructure role is at fault. Although I'm not qualified (yet!) to help you with the transaction, I'm sure there is information on MS.com regarding changing the roles.
. However props to the guy at supercars.net for chosing such a kewl handle!
