Citrix admins and the ExtraHop crew had a lot of laughs at this year’s Citrix Synergy in Las Vegas, poking fun at how users blame Citrix technology for slow performance when really it’s a problem somewhere else (often the infamous Layer 8).

Citrix administrators understand how the blame game works: It’s a “guilty until proven innocent” proposition, where Citrix is assumed to be the cause of poor user experience until the admin can prove otherwise.

We asked some ExtraHoppers who had formerly been Citrix administrators what real causes of slow performance had been blamed on Citrix. Here were some of their responses:

  • A corrupted database index
  • QoS reprioritizing ICA
  • An overcrowded hypervisor
  • A slow web server
  • A full WebSphere queue
  • An I/O-constrained client due to Windows Update or SEP Updates
  • A teleworker’s neighbor’s cheap 2.4GHz phone interfering with their Wi-Fi
  • A dead Wireless Access Point
  • The company discontinuing Cisco TAC support and missing latest firewall firmware that prevented a freezing/rebooting issue
  • 10Mb/s of data on a 6Mbps MPLS link
  • 37 people at the Starbucks Wi-Fi (high user latency on a non-RFC1918 address)
  • A multi-homed system with dual default routes
  • IS-IS routing “gone wrong”
  • The local exchange carrier made “improvements” over the weekend
  • A logon script ported over from the Novell Netware days that had a drive letter removed
  • A user in Cincinnati logging into a domain controller in Haiti
  • Gogo in-flight wireless
  • Subnet IP being taken by someone’s HPUX box (“Oh, that was your IP address?”)
  • A user bypassing the web content filters and streaming movies
  • A user storing 2GB of photos on his roaming profile

The ExtraHop platform analyzes all data in flight so that Citrix admins and architects can not only verify user complaints but also show exactly where the source of latency is coming from.

Quote from the network guy: "Just because the servers can't ping each other does not mean it's a network issue."
Quote from the network guy: “Just because the servers can’t ping each other does not mean it’s a network issue.”

To learn more, download the white paper: Citrix Troubleshooting Guide: How to Stop The Blame Game.

See what other stories people shared by checking out the #StopITShaming stream on Twitter.

Synergy Banner