Network Configuration and Deployment issues for Manage Engine Desktop Central
Hi there, I work in the IT department of a growing construction company. We started using Manage Engine Service Desk Pro in our Help Desk a few months ago. Now we are looking at possibly getting into Manage Engine Desktop Central to assist with RDP connections, patch management, and software deployment.
As some of our systems are not on our LAN but actually at remote job sites with internet access. I have setup a test system at one of the sites, and find that although it sends an initial report to our demo of Manage Engine Desktop Central, we can not connect to that system via RDP, perform new scans, or push patches to it. We've verified that the firewall is opened on both ends and ensured that the firewall is set correctly on the test system. The only thing we can think of that could potentially cause a problem, is that the test system (like all of our job site systems) are behind a standard router, thus all computers would be receiving a private IP vs a public IP. This is confirmed when I check the information that is received by MEDC and that it shows that the IP and gateway reported are not the public IP, but the private IP.
Is there anyway to get this to work the way we need it to, by traversing through remote systems behind routers.
As some of our systems are not on our LAN but actually at remote job sites with internet access. I have setup a test system at one of the sites, and find that although it sends an initial report to our demo of Manage Engine Desktop Central, we can not connect to that system via RDP, perform new scans, or push patches to it. We've verified that the firewall is opened on both ends and ensured that the firewall is set correctly on the test system. The only thing we can think of that could potentially cause a problem, is that the test system (like all of our job site systems) are behind a standard router, thus all computers would be receiving a private IP vs a public IP. This is confirmed when I check the information that is received by MEDC and that it shows that the IP and gateway reported are not the public IP, but the private IP.
Is there anyway to get this to work the way we need it to, by traversing through remote systems behind routers.