What is the difference between a device being connected and online?
Currently I have probably 70+ devices being online but not accessible for remote control.
the devices are located in 4 different locations using 4 different internet connections.
Why would so many go offline like that?
Please try running the appropriate procedure to check connectivity and post the results here for Comodo support to help you further:
If the endpoints are using the US platform use https://scripts.comodo.com/frontend/web/topic/to-check-comodo-c1-itsm-urlips-and-ports-for-firewall-us
OR
For the EU https://scripts.comodo.com/frontend/web/topic/to-check-comodo-c1-itsm-urlips-and-ports-for-firewall-eu
Also, ensure all the endpoints are running the latest version of Comodo Communications Client 6.20…
Again, What is the difference between a device being connected and online?
Subdomain being my full subdomain for the comodo account?
Where do I find that?
Doesnt the Comodo clients update automatically?
Hello @smartcloud
If the device is connected, it means device communicates with portal almost at real time (portal-> agent direction) (HTTPS, XMPP) - GREEN Status.
If the device is just online with BLUE Status, Device communicates with portal via HTTPS but with some delay (HTTPS, NO XMPP)
As for Comodo Remote Control, XMPP connection between device and XMPP server is mandatory for it so you will not be able to remote control device that has
either BLUE or GRAY status on portal.
Please double check the network settings (firewall, proxy settings). XMPP should be allowed.
Inside ITSM module, click on IT & Security Manager and open it in new tab (this should do the trick)
By the way, for MSP that will be ‘subdomain-msp.cmdm.comodo.com’ and for Enterprise ‘subdomain.cmdm.comodo.com’
Comodo Client Communication should update automatically to the latest version according to the schedule from ‘Update’ tab in the [URL=“https://help.comodo.com/topic-399-1-786-10683-View-and-Manage-Profiles-Associated-with-the-Device.html”]profile
associated on your device.
Please tell us if this suffices your query.
Great answer Jay,
But I ran the script and it has no direct output as far as I can tell.
I can see the execution log and the results there but I assume I am not being asked to check all 115 logs to get the result?
This one is showing connected.
CCC is 6.20.xx
Here is the output.
Comodo Client - Communication (CCC) Success connecting to smartcloud-msp.cmdm.comodo.com.cmdm.comodo.com on port 443 HTTPS Success connecting to mdmsupport.comodo.com on port 443 HTTPS Success connecting to 54.93.214.133 on port 443 HTTPS Success connecting to plugins.cmdm.comodo.com on port 443 HTTPS Success connecting to smartcloud-msp.cmdm.comodo.com.cmdm.comodo.com on port 443 HTTPS Success connecting to xmpp.cmdm.comodo.com on port 443 HTTPS Success connecting to 18.196.72.222 on port 443 HTTPS Success connecting to 18.196.138.4 on port 443 HTTPS Success connecting to 18.197.8.210 on port 443 HTTPS Success connecting to one.comodo.com on port 443 HTTPS Success connecting to download.comodo.com on port 443 HTTPS Success connecting to download.comodo.com on port 80 HTTP Success connecting to 178.255.82.5 on port 443 HTTPS Success connecting to 178.255.82.5 on port 80 HTTP Success connecting to cdn.download.comodo.com on port 443 HTTPS Success connecting to cdn.download.comodo.com on port 80 HTTP Success connecting to 104.16.61.31 on port 443 HTTPS Success connecting to 104.16.61.31 on port 80 HTTP Success connecting to 104.16.60.31 on port 443 HTTPS Success connecting to 104.16.60.31 on port 80 HTTP Success connecting to ocsp.comodoca.com on port 80 HTTP Success connecting to crl.comodoca.com on port 80 HTTP Success connecting to patchportal.one.comodo.com on port 443 HTTPS Success connecting to 23.229.69.170 on port 443 HTTPS Success connecting to cescollector.cwatchapi.com on port 443 HTTPS Comodo Client - Security (CCS) Success connecting to fls.security.comodo.com on port 4447 UDP Success connecting to fls.security.comodo.com on port 53 UDP Success connecting to 199.66.201.16 on port 4447 UDP Success connecting to 199.66.201.16 on port 53 UDP Success connecting to fls.security.comodo.com on port 4448 TCP Success connecting to fls.security.comodo.com on port 80 TCP Success connecting to 199.66.201.16 on port 4448 TCP Success connecting to 199.66.201.16 on port 80 TCP Success connecting to valkyrie.comodo.com on port 443 HTTPS Success connecting to cdn.download.comodo.com on port 80 HTTP Success connecting to 104.16.61.31 on port 80 HTTP Success connecting to 104.16.60.31 on port 80 HTTP Success connecting to cdn.download.comodo.com on port 443 HTTPS Success connecting to 104.16.61.31 on port 443 HTTPS Success connecting to 104.16.60.31 on port 443 HTTPS Success connecting to download.comodo.com on port 80 HTTP Success connecting to 178.255.82.5 on port 80 HTTP Success connecting to download.comodo.com on port 443 HTTPS Success connecting to 178.255.82.5 on port 443 HTTPS Success connecting to s3-eu-west-1.amazonaws.com on port 443 HTTPS Success connecting to smartcloud-msp.cmdm.comodo.com.cmdm.comodo.com on port 443 HTTPS Success connecting to ocsp.comodoca.com on port 80 HTTP Success connecting to crl.comodoca.com on port 80 HTTP Comodo Remote Control Success connecting to xmpp.cmdm.comodo.com on port 443 HTTPS Success connecting to 18.196.72.222 on port 443 HTTPS Success connecting to 18.196.138.4 on port 443 HTTPS Success connecting to 18.197.8.210 on port 443 HTTPS Success connecting to stun.l.google.com on port 19302 UDP Success connecting to 18.196.107.208 on port 3478 UDP Success connecting to 52.29.123.206 on port 3478 UDP Success connecting to 34.232.133.48 on port 3478 UDP Success connecting to 18.208.23.45 on port 3478 UDP
The output of the procedure bears no sign of unsuccessful connection. However, we have alerted our Product Developers still of your report to urgently look on the issue.