Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 0 subscribers
  • Views 31843 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can Enterprise Console manage non domain computers?

LY
Recently I installed Enterprise Console 4.0 in the server. Besides computers in the domain, there are also some computers in the network but are not in the domain. Can Enterprise Console manage these non domain computers? I can find these computers by using "find by IP address" option. But when I tried to "protect" them, it asks for user name and password. I put in local admin user name and password of the computer but it shows errors. Can someone help on this? Thanks in advance.
:500


This thread was automatically locked due to age.
Parents
  • 0

    Hello LY

    If you install Sophos from a package which includes RMS and the clients can connect to the server (ports 8192-8194 should be "open", preferably in both directions) they can be managed by the console. 

    VLANs shouldn't be a problem if

    1. The server can be accessed using the name specified in the update policy (for Protect Computers the value in the tab Initial Install Source is used). Do you have to specify a FQDN (or IP address) to map the share?
    2. The clients can connect to the share (obvious and obviously possible in your case - I just mention it here because I've seen more than once that the firewall silently blocked SMB between the VLANs)
    3. The management ports are permitted

    Christian

    :535
Reply
  • 0

    Hello LY

    If you install Sophos from a package which includes RMS and the clients can connect to the server (ports 8192-8194 should be "open", preferably in both directions) they can be managed by the console. 

    VLANs shouldn't be a problem if

    1. The server can be accessed using the name specified in the update policy (for Protect Computers the value in the tab Initial Install Source is used). Do you have to specify a FQDN (or IP address) to map the share?
    2. The clients can connect to the share (obvious and obviously possible in your case - I just mention it here because I've seen more than once that the firewall silently blocked SMB between the VLANs)
    3. The management ports are permitted

    Christian

    :535
Children
No Data
Unfiltered HTML