• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6288
  • Last Modified:

Cannot Reply using Outlook Web Access (OWA) , Windows XP and IE7

We had a Vista machine that had the red x problem with OWA so I installed the microsoft exchange patch and that fixed the problem,

However I have a problem with my laptop which is XP SP2 running IE7, using the premium client of OWA I can create a new message and send but when I reply to any message it hangs for a while, then asks for authenitcation again and finally comes up with an error "Unknown" - at that point the OWA session is pretty screwed.

From the same computer when I use firefox and the basic client I can send and reply perfectly.

Any thoughts .... this is very frustrating as I much prefer the premium client - and I dont fancy downgrading to IE6

TIA
0
nickbeentjes1
Asked:
nickbeentjes1
1 Solution
 
SembeeCommented:
Is the server fully patched? Not just Exchange 2003 SP2, but there are updates after that as well.

Simon.
0
 
nickbeentjes1Author Commented:
I will have to check - I have applied http://support.microsoft.com/kb/911829 
0
 
Tom-J-LaelCommented:
Nick,

with IE7 you can install the certificate.

http://www.law.uconn.edu/infosys/certificatedwa.pdf

scroll down to the "importing the certificate" section

see if that helps
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
SembeeCommented:
The SSL certificate should not been the problem - that would generate a different type of warning. I suspect there is a patch missing.
Use Microsoft Update to see if any updates are presented for Exchange.
Also check whether the problem follows - a lot of OWA issues are resolved by simply flushing the temporary internet files on the browser.

Simon.
0
 
nickbeentjes1Author Commented:
OK - will try the flush and check the server
0
 
SM17CHCommented:
Try this,

Open OWA and login. Go to Options and scroll down to 'email security'. Click to download the S/MIME Control Active X Control. Choose to run the control from its location. Once it installs, the webpage will ask you if you are sure you want to run the control. Click the yellow bar to let it run.

You can also add the OWA address to your trusted sites under internet explorer options to make it stop asking you about running the control everytime you use OWA.

Hope that helps
Smitch
0
 
SembeeCommented:
Adding OWA to the trusted sites zone is NOT a fix and should not be treated as one. It is a horrible fudge of a workaround. Exchange OWA is designed to work with a default configuration.
The S/MIME fix isn't really a fix either, it simply resets some of the components.

It is really important that the Exchange server is fully patched, as there have been updates for OWA released since Exchange e2003 SP2 which are required for IE7 to work correctly.

Simon.
0
 
nickbeentjes1Author Commented:
OK - Thx .... I havent had the opportunity to apply all updates yet, I will do so tonight.
0
 
nickbeentjes1Author Commented:
Well, done all the updates on Windows update but still no joy.....
0
 
SembeeCommented:
Does it work on the server?
Does it work with IE6?

Simon.
0
 
nickbeentjes1Author Commented:
Sorry been away ...

Here is the kicker - works perfect on the intranet using the local name for the server. and Fast (of course)

Butr when on the internet it is slow as all hell and just wont work well reply no good, cant send  - and have mixed results from different computer / browser combinations.

Our internet connection is very good so not the problem.

We are using a cisco ASA5505 I have port 80 and 443 going to the exchange server.
0
 
SembeeCommented:
If it works internally correctly, but doesn't from outside then I would be looking at the cause of the problem being outside of Exchange - firewall would be the number one culprit. Exchange doesn't care where the connection comes from - inside or outside, so the fact that it works fine inside should mean it works correctly outside. You have to look at what is different.

Simon.
0
 
nickbeentjes1Author Commented:
It has got to do with the firewall at home (Dlink) I am using a non-firewalled mobile card now and it works perfectly .... very strange.
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.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now