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

Computer could not be contacted

Dheald

When trying to install Sophos from the Enterprise Console, using the "Protect Computers" option from the menu, I have had some install successfully, but a few have come up with the error message: Computer could not be contacted. [0x0000002e] Any ideas what this is about? The machines are online and reachable.

:7991


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

    I had an XP Pro SP3 machine give me a 0000003b error code this morning. In the Sophos knowledgebase (http://www.sophos.com/support/knowledgebase/article/16307.html) it seemed to group the 0000002e message with this one, so my fix might help you. Sorry if it doesn't! I only had to carry this out on a single machine, but you should at least be able to check user access rights through AD.

    1.       On the client machine, open Local security settings by going to Control Panel > Administrative Tools

    2.       Expand Local policies > User rights management

    3.       Double-click the setting Access this computer from the network and add the account that you have been using to deploy installations remotely (most likely your network admin account)

    Once I did that, I tried to protect the computer again through the Enterprise console and it came back with a different error. This time it couldn't see the shared folder on the machine that it was trying to contact. I then went back to the client machine and made sure the local disk had an administrative share:

    1.       Right-click the local disk (normally C: drive) and click Properties

    2.       Click Sharing

    3.       Create a share with the name c$ and give the administrative account you've been using full permissions to this share

    I then went back to the console to protect the computer and it worked.

    :9205
Reply
  • 0

    I had an XP Pro SP3 machine give me a 0000003b error code this morning. In the Sophos knowledgebase (http://www.sophos.com/support/knowledgebase/article/16307.html) it seemed to group the 0000002e message with this one, so my fix might help you. Sorry if it doesn't! I only had to carry this out on a single machine, but you should at least be able to check user access rights through AD.

    1.       On the client machine, open Local security settings by going to Control Panel > Administrative Tools

    2.       Expand Local policies > User rights management

    3.       Double-click the setting Access this computer from the network and add the account that you have been using to deploy installations remotely (most likely your network admin account)

    Once I did that, I tried to protect the computer again through the Enterprise console and it came back with a different error. This time it couldn't see the shared folder on the machine that it was trying to contact. I then went back to the client machine and made sure the local disk had an administrative share:

    1.       Right-click the local disk (normally C: drive) and click Properties

    2.       Click Sharing

    3.       Create a share with the name c$ and give the administrative account you've been using full permissions to this share

    I then went back to the console to protect the computer and it worked.

    :9205
Children
No Data