RPC over HTTPs connection properties change after Exch07 reboot
Hello!We are using RPC over HTTPs in a fully patchedExchange 2007/Outlook 2007environment, servers running W2K3 SP2. On two separate occasions after domain maintenance, when Exchange and the DCs (AD clustered, bothare Global Catalog servers) have been rebooted, Outlook stopsconnecting tothe mailbox cluster as the source for Directory Services via HTTPs and instead connects directly to the DCs via TCP.We suspect it is related to the reboot order of either the Exchange boxes as a group, or the Exchange boxes in relation to the DCs wherethe proxy servicesmay be gettingconfused.Can someone provide guidance on reboot order of the various Exch07 roles and Domain Controllers? Could a reboot ofthe primarynode of the AD cluster after the Exchange boxes are online cause this issue?
April 17th, 2009 4:21pm

Exchange should be fault tolerant but it depends on how many DCs and GCs you have. I would reboot DC1, wait about 20 minutes, reboot DC2, wait about 20 minutes and then reboot Exchange if neccesary.Question is, why are you rebooting the servers so often? What is your Exchange environemnt like? How many servers etc, what is clustered?BP
Free Windows Admin Tool Kit Click here and download it now
April 17th, 2009 6:23pm

Hi,Please first confirm whether any error message come up in the event log.Whether the Outlook Anywhere was working after reconfiguring the profile?ThanksAllen
April 21st, 2009 12:40pm

Hi, sorry for the delay in responding. We have confirmed that rebooting theprimary DC/GC server after Exchange was online caused the issue. RebootingExchange serverscorrected the problem. OWA and Outlook Anywhere were working in all cases. The Test Autoconfiguration box returned valid information in OLK2007. External to our subnets, Outlook 2007 connected all HTTPs. Internally, there was the mix of TCP and HTTPs noted above.There were no errorsin the event logs other than normal background messages, but there were unusual NSPI errors in client-server packet traces like below during the TCP/HTTPs mix of connections. 4612.014851199.999.999.92(EX1)199.999.998.91NSPINspiBind response, Status: Unknown MAPISTATUS error 0xbef61591Our environment is:MBX cluster of EX1 and EX2 for mailbox serverEX3 CAS/Hub TransportEX4 EdgeAD1 and AD2 are DC/GC serversExchange is on latest Update Rollup. Pretty much straight "recommended config" setup.
Free Windows Admin Tool Kit Click here and download it now
April 24th, 2009 9:37pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics