Yesterday evening we patched a number of servers as we where running behind on our normal patch cycle. Everything went well but this morning I got a call from our UK users that their OWA system was not working.
Our infrastructure is running exchange 2003 with one Front-End in our central datacenter and two back-end’s one in each country UK / BE.
The exchange servers are all members of the root domain but the UK users are still part of a child domain.
Belgian users where having no problem accessing there OWA, syncing the Windows mobiles,… But I got a call from UK telling me they couldn’t logon to the webmail.
1. My first reaction was to review all patches and to check if Front-End and Back-End where all running at the same patch levels,… This didn’t seem to be a problem.
2. My second thing to check was if i could actually reach the back-end OWA interface from the front-end server. To my surprise this was also giving me the auth prompt’s and ending in an Access denied.
3. My third step was to access OWA on the Back-End from a local UK client, this was working without a problem :-(
4. After checking the firewall rules between front-end / back-end I decided to fire up my trusted Wireshark and see what the f*ck was going one. And yes within seconds I had my answer.
Packet 360 gave me what I needed to know => there was a +10 minutes time skew between the Front-End and the Back-End server that was causing Kerberos to error out.


6. After updating the firewall rules to allow NTP traffic a quick net time update and kazaaam, everything was back to normal
grtz
Tom