Jump to content


  • Posts

  • Joined

  • Last visited

About PaulN

  • Rank

Profile Information

  • Location
  1. Thanks for the quick response! I feel much better knowing that the devices are secure. I think you are correct that the agents are not resolving the DNS name - in order to make the mapped network share folders work on the VPN i need to use the IP address of the server (\\172.22.xx.xx) in the file path, instead of the \\server name\. But, from what i can see in the ESMC server settings, the ESMC server is already designated by IP address, not name. I surmise that the DNS is missing for the VPN connection, but shouldn't the agents be looking for the IP address? Can you explain how i would configure AGENT to use alternate DNS/IP names of management SERVER? Would doing so work for all devices whether connected via VPN or direct Ethernet? I do see however that the devices are named as "LT01.[hostname]" - could that be related to the problem? Thanks! paul
  2. ees_logs.zip I think the attached files have what you need - not sure how to get the trace log or status html. Am i correct that, since the modules are updating when there is an internet connection, the device is fully protected, and the main concern is that ESMC is unable to gather statistics and update the agent with any policy changes? network connections.pdf Event log.txt
  3. We have several laptops that connect to our network via SonicWall Mobile connect SSL VPN. They can access network share folders, and run remote desktop connections to network PCs just fine. The devices communicate with the ESMC server when they are connected via ethernet, but not when connected over the VPN. In ESMC the "Remote Host" shows the device's Ethernet IP address. I've the a KB about needing to open ports and use a NAT rule, but that seams unnecessary with a VPN and very unsecure as the Wi-Fi IP addresses are not static. Thanks for any help. (Our patch management software server and agents work fine over the VPN).
  • Create New...