Hello

Mainstream End Date: Apr 14, 2009
Extended End Date: Apr 8, 2014

The fact that a company still uses Windows XP on workstations at all is an absolute imposition, especially with regard to security / patch management, etc.

The cryptography support on Windows XP alone and the browsers supported on it is so outdated that not much will work on other modern systems with current cipher suites, crypto challenges, etc. either.

Then the customer has until he finally has a decent working environment just use an email client for Windows XP and forget the web interface.

I'm sorry I can't give you a better answer here, but the customer's IT infrastructure has probably been armored 20 times already, and you'll quickly find alternative hardware at the specialty store next door.

In the short term you can also simply install Ubuntu Linux everywhere or provide a USB boot stick per workstation, then they have a tiptop running environment in the meantime.

Im glad its not supporting Windows XP anymore, its time to move on.

Supporting very old and outdated technology is costly and risky.  

You're likely facing blank screens in multiple browsers because Windows XP is unable to support the TLS/SSL protocols in use currently. TLS 1.0/1.1 and SSL v2/v3 have been deprecated in Windows Server environments and this is likely what XP requires. You may be able to find a process to implement support for the newer versions in the existing XP environment, but your best bet is to get those outdated clients up to date. 

Thanks Kyle.

Would the TLS / SSL issue still affect webmail if its running in an insecure environment.  (HTTP instead of HTTPS).  I agree they need to update their computers.  

You're very welcome. I know all too well how hard it can be to get some environments to upgrade. Usually it takes an event like this one ;-) 

On your question; no, TLS/SSL versions won't come into play when using an HTTP binding. Most modern browsers redirect to HTTPS automatically though so maybe its doing that? 

You may be able to get Fiddler Classic installed on one of the problematic clients too and that should at least provide some clues on what is failing "behind the scenes" possibly!

Wow... I mean, it's been almost a decade since M$ dropped XP, I cant believe anyone in IT would allow, let alone support someone on XP. There is no need to even bother wasting time in Fiddler, the 23 year old OS is the problem.