Extremely Slow Event Explorer Login
I've heard slow login's are common with Event Explorer but on all of our machines we are seeing in excess of 10 minutes to login. Since we are using SSL I not able to fully explore the packet data.
I am on the same LAN as the AS so I do not believe bandwidth is the issue.
It's more than likely caused by your internal corporate proxy configuration settings.
In our case we route all internal client web traffic (both 80 and 443) through proxies. Most places do. Once the get request arrives at the proxy the proxy routes it accordingly... unless... you have "Bypass proxy for local addresses" enabled AND you have your internal DNS suffix listed as an internal address.
So in your browser you'd need to
1. enable the "bypass proxy for local addresses" option.
2. ensure you have yourinternaldnsdomainname.com as an internal address.
Then when you launch event explorer, make sure your connection entry looks like this:
This makes a world of difference. Your proxy will route you direct to your enVision appliance and not out and back in. We've observed that this also speeds up the webGUI immensely!
hope this helps,
YEah thats just not right. I'd go insane waiting that long too. What does the traffic look like when you put a snifer up on your client while attempting to connect?
In the meanwhile, I'd definately get a case opened up with support if you haven't already.
I immediately ran tcpdump on my machine to see what it was that was slowing things down but the traffic is all encrypted. I can however see 'full' (1500) packets streaming from the AS to my machine. I spoke with someone that support yesterday and they suggested opening a ticket since that had not heard of this issue before.
I'll keep looking and let you know what I find out.
Thanks for the responses Ryan!
When you are running SSL for EE it proxies through the AS which is doing the encryption. So you will notice a diff in speed due to this nature. The Dsrv is not actively serving the data straight to you. There is a middle man. Also, verify items to improve speed such as memory, Proc allocation, etc. Also, ensure you are on fastest possible link (gb pipe). Can you limit how many hops you are away from the AS? Common thing I see is a Terminal Server that sits on same VLAN and network segment as enVision. Then users RDP (RDP is a light protocol) to the Terminal Server and run EE from there. Much faster, even an ESX server with multiple XP workstations for EE....
Thanks for the reply /db.
Resources i.e. memory/proc/disk (see specs below) aren't an issue as I am on a very powerful workstation. There are three hops from me to the AS and DS. Floor Switch - Core Switch - Rack Switch - Appliance, unfortunatley I am only connected at 100Full although we have verified that the link is nowhere near saturated.
Dual, Quad core 2.8ghz Processor
10gb 667mhz RAM
Dual 7200RPM striped disks