In addition to chengtmskcc's recommendation of checking your firewall ports (see this article for on-premises ports: On-Premises Configurations, Network and Security Requirements), please see this article ( Troubleshooting Workspace ONE Assist) which may give you some ideas on what can be misconfigured.
#Workspace one Offline#
I would also verify, as described above, that your table shows your server and shows it as active, otherwise, Assist will be reaching out to the incorrect server or assuming the entire server is offline and cannot be contacted. In a single server deployment where everything is on one server, I would verify that IIS is installed and properly listening to your configured ports for the Core/App services (443 by default). This could be firewall or routing issues, could you please verify that the target server(s) can reach each other over the intended ports? In a multiple server deployment where your Connection Proctor (CP) and Core/App/Portal (CAP) servers are separated, this is likely caused by the other services being unable to reach the DTP (Data Tier Proxy) service which resides on the server where the Core/App services are installed. If you query all entries (SELECT * FROM ), do you see an entry for your target server? And if so, does the active column report as true or false?
I have a few questions to help understand where the issues may be arising from: Hello FelipeSilvaFelipeSilva1 and iamtonystark,
0 kommentar(er)
