Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 1653 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

Issue with invalid credential error when protecting PC's in a workgroup

em2_newf

Hi guys,

We have been protecting some servers in our DMZ but some machines will produce an invalid credential error in the Protection Wizard. Here is the background:

We have one Sophos server on our Corp LAN and we have setup the firewall rules to allow traffic for ports 8192 and 8194 and have updated the host files on the Sophos server and DMZ servers. Name resolution now works and I was able to successfully install Sophos and a couple but some are now giving the invalid credential error.

The DMX servers are WORKGROUP and not domain members, this means that the usernames and passwords do not match up with anything in AD. Has anyone else had this issue? I tried creating a local account with the same name and password as an AD user with adin rights but still had the same reult.

If anyone can shed some light it would be greatly apprecited.

:38505


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

    Hi,

    The account you enter in the wizard is required to logon to the management server.

    So, I would think if on the "SEC Server" you had a local account (I assume it's not on a DC) called SophosDeploy, then you had a local account called SophosDeploy on the target computer it would work.  If you don't have a common username and password on all computers you would need to essentially create an account on the SEC server for every account that exists on the workgroup computers.


    Maybe it would be worth performing a pull install, i.e. running setup.exe from the server if the number of account required is too many to manage?

    Regards,

    Jak

    :38515
Reply
  • 0

    Hi,

    The account you enter in the wizard is required to logon to the management server.

    So, I would think if on the "SEC Server" you had a local account (I assume it's not on a DC) called SophosDeploy, then you had a local account called SophosDeploy on the target computer it would work.  If you don't have a common username and password on all computers you would need to essentially create an account on the SEC server for every account that exists on the workgroup computers.


    Maybe it would be worth performing a pull install, i.e. running setup.exe from the server if the number of account required is too many to manage?

    Regards,

    Jak

    :38515
Children
No Data