Any networking-related issues can often be the most difficult to get to the bottom of. Wherever possible, ensure that you work closely with your networking team to ensure there is suitable end-to-end monitoring in place.

While your users are connecting on a LAN, you would hope there would be plentiful bandwidth, latency would be low enough, and therefore connectivity would be reliable. If you are struggling on a LAN, consider the following:

• Has anything on the network changed?
• Is the user connecting via a wired or wireless network?
• Have you configured PCoIP for QoS on your switches?
• Is the network currently reliable?
• Are you seeing any dropped packets between any of the following?
  • Clients to the core switching
  • Clients to servers
  • Clients to VDI desktops
• Is the latency as expected?
• Even on the LAN in larger environments, bandwidth could be an issue—have you considered the sum of the bandwidth required from your client devices to VDI desktops?
• Are you routing between networks? Do the routers work at a suitable level of performance?
• Are the load balancers sized correctly for your environment?

When your users are connecting over a WAN, it can sometimes be more difficult to troubleshoot or guarantee connection quality.

For remote or branch offices, ensure that the internet connection is suitably sized; wherever possible, ensure that you have configured QoS for the PCoIP protocol from end to end, and ensure that you have suitably configured the PCoIP policy to cope with the reduced bandwidth.

When troubleshooting issues, investigate the relevant logs on the client and on the View Connection Servers, as well as any intermediary components, such as the load balancers and routers.

The following list contains some of the more common faults that a user will report:

• Black screens: This is commonly caused by ports blocking the PCoIP Protocol somewhere in the chain. Check that the PCoIP port are open; namely, port 4172.
• Disconnections: High latency and dropped packets will cause the users to be disconnected from their desktops. Ensure that you allow enough time for users to reconnect before refreshing desktops.
• Poor resolution images: Due to the nature of the protocol if there is low bandwidth, users may complain about low-quality images. Consider limiting the image build options in the user policy.

The following screenshot shows an example of information for the PCoIP protocol recorded by Liquidware Stratusphere UX:

In the next section, we are going to look at compute resources.