Wow, got bit by this one big time.
Outlook Anywhere (aka HTTPS over RTP) or RWW wasn’t working for more than 1 concurrent user (and I use ‘working’ very loosely). RWW wouldn’t work if someone was already connected with Outlook and vice versa. In other words, only 1 https tunnel was ‘operational’ at a time.
Also, RDP through RWW wasn’t working – get a blank screen and then would error out. We thought this was totally unrelated, but discovered it working after this fix, so we actually killed 2 birds with 1 stone. Gotta find some kind of silver lining! 
So me and my technician lost some hair follicles trying to figure this one out. My hairline can’t afford this kind of treatment.
We suspected the SonicWALL TZ190 – not it. Got some good experience with the TZ’s though – nice boxes.
Microsoft was blaming the NIC’s in our laptops – nope. D630’s with Vista 64 – nice machines too.
Server is a T300 with Hyper-V, SBS 2008 and a 2003 member server running BES. Also a nice machine. And Hyper-V is a cool solution – READ THIS for more on Hyper-V and how it’s being used.
So with many hours of troubleshooting and frustrated clients later, the problem looks to be fixed, but I sure wish Microsoft had issued a patch.
So as the SBS team says:
“To resolve this issue we suggest that you remove the HttptoHttpsRedir module from the /RPC virtual directory only.”
Good suggestion, problem resolved (thankfully).
UPDATE: The Official SBS Blog has published a new fix:
New Resolution
- Open regedit with administrative permissions.
- Create the below DWORD and set its value to 5000 decimal to increase the limit of concurrent requests.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0\ MaxConcurrentRequestsPerCPU
Hopefully we’ll see Microsoft an email blast to all their Partners on this one. Perhaps even worth an out-of-cycle patch.
.png)
