This post is more than 5 years old
4 Posts
0
152255
August 15th, 2013 21:00
RDSH Lag when going through Secure-IT SSL Gateway
Hi,
I have an opened ticket with Dell/Quest support but thought I would post this ongoing issue here in case someone can help.
Issue:
I am on vWorkspace version 8 and all servers are virtual Win2008R2 on ESXi 5. When Web Connector clients (Windows or Mac) connects to RDSH through the Secure-IT SSL Gateway, there is noticeable lag when typing, dragging windows, move mouse cursor around the start menu, etc. All of our pilot test users complained about this as it affects their normal day to day work.
This is in comparison to the standard Windows RDP client as well as when bypassing the Secure-IT. When bypassing the Secure-IT, the lag is completely gone. Also, the lag is noticable when comparing in the LAN only environment.
All EOP disabled except for EOP Extreme, EOP Flash, and EOP Printer. I also tested with ALL EOP features disabled, but it didn't make any difference.
All Windows features disabled (i.e. font smoothing, background, etc.)
My infrastructure:
Internet (Users) --> SonicWall Firewall --> LAN (Secure-IT, Web-IT, Connection Brocker, RDSH Servers)
The Secure-IT VM was in the DMZ, but to troubleshoot, I moved it inside the LAN which made no difference.
The Secure-IT VM has plenty of resources as I can see that the CPU and RAM hardly moved. And I am only testing with one or two connections anyway.
I tried the old Secure-IT executable from version 7.5 which makes the lag even worse.
At this point, this is a show stopper for us. Hopefully this can be resolved as vWorkspace is the best solution for us in terms of ease of use/login for our non-techie users.
Help!
push3r
4 Posts
0
August 16th, 2013 14:00
I found out what the problem was. I disabled logging on the Secure-IT and now the lag is completely gone. I found out about this on a post at the Quest vWorkspace forum back in 2010. http://en.community.dell.com/techcenter/virtualization/vworkspace/f/4827/t/19551509#1880
So, I think Dell/Quest should either document this, put it in a knowledge base, and/or fix the Secure-IT service (pnsslsvc.exe) as it would help a lot of people.