• It is likely a Windows OS driver issue, i.e. the "Standard OpenHCD USB Host Controller" did not get installed. Or it may be the problem with generic USB device initialization in Windows. The driver was installed but disabled. Enabling it may solve the problem. Check if there's any exclamation (!) or question (?) mark in Device Manager.
• Be sure that USB device authorization is properly configured in the Administrative Web Interface for the Portal (see the USB section of the Administrative Interface Manual).
• Be sure the Host Card is firmly inserted in the host PC/workstation’s PCIe slot.
• If you are using the Host Card in Standalone mode (not inserted in a PCIe slot), audio and USB functions are not available.
• If your host PC uses Linux, be sure the OHCI driver is loaded.

• If you are using Windows Vista, be sure you are using the OS's native high definition audio driver.
• If you are using Windows Vista 64-bit, be sure the “Enable Microsoft Windows Vista 64-bit mode” option is enabled in the Host Card's Audio Permissions of the Administrative Web Interface.
• If you are using Windows XP or Linux, be sure you have installed the Realtek HD audio driver. This driver can be downloaded from Realtek’s website. After installing the Realtek driver, you have enabled the audio function on the Portal. Now you can simply enable the function on the Host before using audio function. In the "Initial Setup" webpage of the Configuration menu, ensure that the audio is enabled. Press "Apply" and then press "Reset". A popup windows appears to remind you that the PCoIP will reset on the next host system restart and your changes will take effect then.
• Be sure that audio is enabled for both the Host and Portal. Audio can be enabled or disabled using the Administrative Web Interface. For more information, please see the Audio section of the PCoIP Administrative Interface User Manual. You must restart the PC after enabling audio for the Host Card.
• Be sure the Host Card is firmly inserted to the host PC/workstation’s PCIe slot.
• Be sure your speaker’s audio cable is firmly connected to the Portal’s rear line-out or headphone jack.
• Windows Vista supports outputting audio to only one port at a time, either the headphone or the rear line-out jack. Be sure you set the desired audio-out jack as default in Sounds under Control Panel in your OS.
  For example, if you are listening music from the headphone jack but want to switch to the rear line-out jack instead, you need to enable the rear line-out jack by setting it as default in Sounds. Note that you may need to restart the audio application for the change to take effect.

Note: If you are using the Host Card in Standalone mode (not inserted in a PCIe slot), audio and USB functions are not available.

• Be sure the PC power supply is connected to AC power and is on standby.
• Be sure the Wake Configuration Header is properly connected for the desired Wake option.
• If a 2-pin jumper is set to pin 2-3 of the Host Card's Wake Configuration Header, be sure the Host Card Power Button Cable is connected between the Host Card's Power Button Cable Connector and the PC motherboard's front panel On/Off switch header.
• If a 2-pin jumper is set to pin 1-2 of the Host Card's Wake Configuration Header, be sure the Host Card is inserted to a PCIe slot.
• Be sure the Portal and Host are reachable on the network.
• Be sure the Portal's Remote PC Power Button setting is properly configured in the Administrative Web Interface. For more information, please see the Power section of the Administrative Interface manual.
• If DHCP is used to configure the IP address of the Host Card and remote power on no longer functions but did previously, the DHCP lease to the Host Card may have expired while the host PC was powered down. When this happens the Host Card appears to be unplugged from the network and messages sent from the Portal are not forwarded to the Host Card. The DHCP lease expiration time is a deployment specific configuration setting. To avoid this problem, ensure the DHCP lease time is longer than the amount of time a Host Card may be powered down or assign the Host Card IP address statically rather than using DHCP.

• Be sure all network cables are firmly connected and the network jack activity lights are On.
• Be sure that the Host and Portal are reachable on the network (e.g. subnets are not masked).
• If Connection Management and Host Discovery are disabled, be sure the Host Card's IP and MAC addresses are properly configured in the Session tab of the OSD, or in the Portal's Administrative Web Interface. Also be sure the "accept any peer" option is enabled in the Host Card's Session page in the Web Administrative Interface.

Be sure the Portal's power cable is firmly connected and plugged into a functioning AC outlet. Press the Portal power switch to ON. The Power LED should light. If the Portal is properly connected to a monitor, the OSD will appear on the monitor in approximately 10 seconds.

• Be sure the Host and Portal network cables are firmly connected and the network jack activity lights are lit on both the Host and Portal.
• Be sure the Host and Portal are reachable on the network (e.g. their subnets are not masked).
• Be sure the ports required for PCoIP are open and not blocked by IT administrators.
• Be sure the DVI cable(s) are properly connected between the GPU and the Host Card at the host PC/workstation.
• Be sure the DVI cable(s) are properly connected to the Portal.
• Be sure Connection Management is disabled in the OSD when a connection broker is not used.
• Be sure the Host Card’s and Portal’s Ethernet cable is connected to a LAN port but not a WAN port of a router when connected to a local network.

• Power cycle your host PC/workstation if you encounter this issue.
• Be sure the graphics card’s DVI output is connected to the Host Card at the host PC/workstation. Note that the Host Card is not compatible with VGA output.
• Be sure a PCoIP session has been connected.
• Be sure the DVI cables are firmly connected on the Host Card and Portal.
• Be sure that a DVI cable is connected between the graphics card's DVI port that is driving video signals and the Host card's DVI port.
• Be sure the monitors support the PCoIP supported resolution.
• Be sure the proper graphics card driver is installed.
• Be sure the default video output option in your BIOS is properly configured. Most BIOS lets you choose PCIe, VGA, or AUTO as default.
• Be sure your desired displays are enabled in display properties of your OS. (e.g. right click in Desktop --> Properties --> Settings --> “Extend my Windows desktop onto this monitor”) For instance, if you have on-board VGA and a DVI graphics card in your host PC/workstation, and video outputs only from your VGA but not DVI port, you can connect a monitor to your host PC/workstation using a VGA cable and then enable the monitors connected to your Portal by enabling them in display properties of your OS.

If the problem is still unresolved, try connecting a monitor directly to the DVI output port of the graphics card to verify that the graphics card is working properly.