Graphical Connections Troubleshooting

When trouble shooting Graphical Connections some of the things to look for are:

• Is “Ignore Certificate Errors” selected on the Graphical Authentication Settings. (Very often overlooked)
• Is the ConsoleWorks Host Firewall properly configured? Or turned of completely.
• Is the Firewall on the Target machine appropriately configured for the Graphicals to communicate with ConsoleWorks?  (See this article Default ports used by ConsoleWorks)
• Are any Firewalls between ConsoleWorks and the Target properly configured (See above)
• Can you ping the Target machine from the Gui Gateway Command line? (Enabling ICMP may be necessary). If not there may be a routing problem
• Is the Target host machine running?
• Is the Target CPU Bound?
• Are Remote Connections enabled on the Target?
• Is the Target “out of available connections”? (May require connecting via direct RDP to determine)
• If NLA, (Network Level Authentication), is enabled, is it also enabled in the Graphical configuration in ConsoleWorks?
• Log into the Host System for the Graphical Gateway and run the /opt/gui_gateway/tail_messages.sh to see what the errors are

• Try using RDP to the Target OUTSIDE of ConsoleWorks as a quick test to be sure the machine is capable of connecting
• Try some of the other Authentication methods and see if that helps too.  With and without pre-loaded Username and Passwords
  
   
   

See this article for troubleshooting the Gui Gateway
http://knowledgebase.tditechnologies.com/content/guigateway-troubleshooting
See this article for examples of connecting to Windows 10 Pro targets
http://knowledgebase.tditechnologies.com/content/graphical-connections-w...