sukh Posted March 16, 2011 Posted March 16, 2011 My reasonsing, is that I am trying to rule out CAS server and try and focus on the issue. If we can point to the other CAS server and perform some tests, this will at least indicate an issue with the CAS rather than users. There's a few tests we will have to do, from the client end as usual, new user, new PC, exisiting user, existing PC etc..
adamf Posted March 17, 2011 Author Posted March 17, 2011 Pointing to the other CAS server hasn't fixed the issue. In terms of tests at the client end, there isn't much we can do, it seems to be effecting most staff and we have a variety of different hardware that we are seeing the problem on.
adamf Posted March 17, 2011 Author Posted March 17, 2011 This error message has started to appear on machines today (see screenshot) http://i51.tinypic.com/ddgab4.jpg Any ideas?
sukh Posted March 18, 2011 Posted March 18, 2011 (edited) can you up the logging to at expert/verbose on the CAS and reproduce the problem. Then check event logs. MSExchange OWA\Core MSExchange OWA\Configuration MSExchange OWA\Proxy Few other things you can try. 1. Start Windows in safe mode with networking and test OWA. 2. Disable Add-ins in IE 3. Start IE in safe mode 4. Run test-owaconnectivity for a problem user several times and check latency/errors. 5. If all fails, I think it may be worth doing a network capture. Use Netmon to perform the capture, on the server and client and reproduce problem. Edited March 18, 2011 by sukh
adamf Posted March 18, 2011 Author Posted March 18, 2011 I've changed the diagnostic logging on the above to expert, the problem has been reproduced by staff but I am seeing nothing of any significance in the event logs. I haven't tried all of the above steps yet, but running test-owaconnectivity a few times produced figures between 78ms and 93ms but occassionally spiked to 350 or 400ms then returned to around 78-93ms
sukh Posted March 18, 2011 Posted March 18, 2011 That spike is normal and expected. Any chance of doing the other tests? Also, the latest error you sent (jpg) is this the only error the users are getting now or is it an addition to the original errors?
adamf Posted March 18, 2011 Author Posted March 18, 2011 Both errors still occur... I will get to the other tests. I'm trying to capture some network traffic between my laptop and the server. I can't get the filter correct in wireshark to display what I want to see. Does anybody know what the filter should be to display traffic between client and server (when it's web based)? I've tried ip.addr==sourceip and ip.dst==destinationip but when using OWA nothing is displayed
ful56_uk Posted March 18, 2011 Posted March 18, 2011 whats the ping response time if you ping from a client to the server you are trying to use owa on
sukh Posted March 18, 2011 Posted March 18, 2011 you still have to set-up the protocol captures, like "HTTP is Request” and “HTTP is Response"
ful56_uk Posted March 18, 2011 Posted March 18, 2011 did you say you are using policy central enterprise, have you seen this? Update to PCE Client software to address issues with Microsoft Internet Explorer versions 8
adamf Posted March 18, 2011 Author Posted March 18, 2011 I've managed to capture and filter that data now. It appears that even with the autoritive dns zone requests are still going via our ISA server, so I changed my proxy to go straight to our ISPs proxy - the error still occur. One thing I did notice is that every request that goes out has the following: Header checksum: 0x0000 [incorrect, should be 0x2dc5] the figure in bold is always different. [Good: False] [bad: True] [Expert Info (Error/Checksum): Bad checksum] [Message: Bad checksum] [serverity level: Error] [Group: checksum] What does that mean (if anything)?
adamf Posted March 18, 2011 Author Posted March 18, 2011 did you say you are using policy central enterprise, have you seen this? Update to PCE Client software to address issues with Microsoft Internet Explorer versions 8 Yep. We are well above that version....
adamf Posted March 18, 2011 Author Posted March 18, 2011 I don't have it installed on my laptop and I still get the errors.
ful56_uk Posted March 18, 2011 Posted March 18, 2011 have you tried browsing to the site using the ip address of the server instead of the dns name?
sukh Posted March 18, 2011 Posted March 18, 2011 your laptop which you used, is that a vanilla build or standard build within your env? Have you had a chance to do the other tests?
RabbieBurns Posted April 30, 2012 Posted April 30, 2012 Hi I am having this error now since moving to exchange 2010. Did you find a solution?
RabbieBurns Posted May 11, 2012 Posted May 11, 2012 Hi I am having this error now since moving to exchange 2010. Did you find a solution? this error is still happening for me
sukh Posted May 11, 2012 Posted May 11, 2012 Just re-read the post again, which errors are you getting and for what users/pc's? Have you narrowed down the issue?
RabbieBurns Posted May 12, 2012 Posted May 12, 2012 Just re-read the post again, which errors are you getting and for what users/pc's? Have you narrowed down the issue? Server timed out, Server busy errors in OWA. Have had it from a random number of users its not consistent or repeatable that Ive seen. we use the same FQDN for both internal and external owa access (mail.blah.com) Most of the reports are from folk accessing from external as we use outlook 2010 internal (no problem with outlook either internal or external)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now