Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 10158 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

Protected computers still showing as greyed out in Enterprise console

SN

Hi

I'm having a problem where by computers i have protected through the enterprise console are not showing as protected even though the sophos client installed correctly and updates without problems.

Basically the same computers were protected and showed fine when installed with win XP.  I have recently upgraded all the desktops to Win 7 and protected them from console but they do not show as protected. 

On some of the computers i had to manually run the sophos install from task scheduler.  The machines have the same SID from when they had XP installed and Sophos is gathering information from AD.  Server is domain controller running win 2k8 R2 SP 1 and enterprise console 4.5.

I would really appreciate some help on this.   Thanks

:12209


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

    Thanks for your final results :smileyhappy:

    Some comments in case someone else stumbles over this thread:

    Getting parent router IOR from *server MAC*

    It's not a MAC but the IPv6 address. The four Getting parent router IOR ... lines show that the client's RMS is attempting to connect to the server's 8192 port to get the IOR (and subsequently the certificate) using in this order: IPv4, IPv6, FQDN and NetBIOS name to locate the server. This corresponds to the values in mrinit.conf (note that not all are required - for  more details please see Remote Management System: significant files and registry entries on the client computer).

    As you saw the client wasn't getting any response from the server. Of course this doesn't tell you the precise cause but it should put you on the right path. If you telnet to the server's 8192 port (using the same addresse(s)/name(s) as RMS it should return the IOR string and close the connection. This can help in determining the exact cause.

    Christian

    :12231
Reply
  • 0

    Thanks for your final results :smileyhappy:

    Some comments in case someone else stumbles over this thread:

    Getting parent router IOR from *server MAC*

    It's not a MAC but the IPv6 address. The four Getting parent router IOR ... lines show that the client's RMS is attempting to connect to the server's 8192 port to get the IOR (and subsequently the certificate) using in this order: IPv4, IPv6, FQDN and NetBIOS name to locate the server. This corresponds to the values in mrinit.conf (note that not all are required - for  more details please see Remote Management System: significant files and registry entries on the client computer).

    As you saw the client wasn't getting any response from the server. Of course this doesn't tell you the precise cause but it should put you on the right path. If you telnet to the server's 8192 port (using the same addresse(s)/name(s) as RMS it should return the IOR string and close the connection. This can help in determining the exact cause.

    Christian

    :12231
Children
No Data