Troubleshooting Intel® Unite™
work
1.1 EnterpriseMode:PINNotDisplayed in progressConferenceRoom(Hubwilldisplay______insteadofaPIN)
InEnterprisemode,thePINnumberwilldisplaydashes“------“wheneverthehubisnotabletoestablishaconnectionwiththeIntel®Unite™PINserver.
Suggestedisolationstepsinclude:
ChecktheHub’sconnectiontothenetwork.
DidtheDHCPserverprovideanIPaddressfortheHub?
Suggestion:Tryrunningipconfig.exefromacommandpromptonthehub.
ChecktheHub’sconnectiontotheIntel®Unite™PINServer.
AreyouabletopingtheIntel®Unite™PINServerIPaddressorFQDNusingawindowscommandline?
Isthelocalfirewallornetworkinfrastructureblockingcertainports?
Suggestion:Tryopeningawebbrowser,andtypingintheFQDNoftheUniteServer: https://<yourservername>/unite/ccservice.asmx,whichshouldreturnavalidpage,hostedbytheIntel®Unite™Sever.
1.2 Collecting LogsforTroubleshooting:
Duringtroubleshooting,collectingalogfilecansometimeshelpyoutouncoverpotentialconfigurationproblems.TherearetwotypesofloggingactivitiestohelpyouisolateproblemsduringdeploymentoftheIntel®Unite™Hub,Client,orServer.
InstallationLogs:
Youcancollectinstallationlogsbyre-installingthesuspectedcomponentforserver/hub/clientusingthe“/l”commandlineoption,withthepathtologfile:
OpenaWindowscommandprompt,navigatetothedirectorywhereinstallationfileislocated(Hub,Client,orServer*.msifile),andlaunchtheinstallerpackageusingthefollowingcommandline:
<uniteinstallerfilename>/l<pathnameforyourlogfile>
RuntimeLogs:
YoucancollectruntimelogsbylaunchingtheHuborClientexecutable(afterinstallation)directlyfromthecommandpromptusingthe“/debug”commandlineoption,togetadditionalinformationonconnectionflow.
OpenWindowscommandprompt,navigatetotheProgramFilesdirectoryoftheHuborClientapplication,andthenlaunchtheIntelUniteapplication:
IntelUnite.exe/debug