Dageeza -
What you are seeing is by design and is the same behavior that existed in previous versions of Exchange. What initiates the client to use the OpenFlags.AlternateServer routine is receiving the error "MAPI_E_NETWORK_ERROR". In your scenario, by simply dismounting the public folder store, the client is not getting the network error, but ecLogonFailed instead. Because it is hard to tell (on the client) if the ecLogonFailed is due to the PF store being dismounted vs. some other error that won't be solved by going to a different PF server, the alternate server routing is not initiated.
Ross
What you are seeing is by design and is the same behavior that existed in previous versions of Exchange. What initiates the client to use the OpenFlags.AlternateServer routine is receiving the error "MAPI_E_NETWORK_ERROR". In your scenario, by simply dismounting the public folder store, the client is not getting the network error, but ecLogonFailed instead. Because it is hard to tell (on the client) if the ecLogonFailed is due to the PF store being dismounted vs. some other error that won't be solved by going to a different PF server, the alternate server routing is not initiated.
Ross
Published Jan 11, 2011
Version 1.0