Exchange Admin

Dear Sir,

I had requested many questions for help regarding our Exchange server 2003 w/sp2 is not able to push staffs' email to their mobile device, smartphone, ipad, and iphone via Exchange Active Sync.  I also ran Exchange Remote connectivity test for Exchange Active Sync, and test is failed due to TCP port 443 is blocking or not lisening.   We do not use SSL Port 443 to sync the email to mobile device, and Exchange server Active Sync was working very well to all our staffs' mobile phone and ipad for past 2-3 years.  Staffs have no problem to receive emails from their smartphones for past 2-3 years.  After 8/18/2012, Exchange server started to have problem to sync emails to mobile device, either no message or email is not up to date in staffs smartphones.  There is no error message in the server application log.

Exchange server 2003 is running in the Windows server 2003 w/SP2, I discover the Windows's TEMP folder, C:\Windows\Temp, starts to fill the TEMP files, $ETXXXX, very quick, it looks like users inbox information. Because this $ETXXXX temp files are filling into Windows Temp folder so quick and use a lot C drive space.


Do you think because our Exchange server Active sync is not working properly and fill out all outgoing emails to mobile device to windows temp folder?

Please help!  All I requested questions before, please check my open questions, I have no solution to fix this Mobile Syn problems.    We all use http port 80 to sync our mobile devices for many years, just don't know why the sync is not working now?   Why TCP port 443 involved?  

Thank you,
Paul
paul_linAsked:
Who is Participating?
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Is teh SSL bit checked on Active Sync Virtual Dir in IIS ?

- Rancy
0
 
Exchange_GeekCommented:
Please check on the site https://testexchangeconnectivity.com to see what are the errors being faced for Active Sync.

Regards,
Exchange_Geek
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Do you have a firewall or Router ... if so check if they are accepting port 443 communication and allowing it to flow inside.

- Rancy
0
 
Exchange_GeekCommented:
Could you please mention what was the solution that helped you?

Regards,
Exchange_Geek
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.