Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 13 subscribers
  • Views 8748 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

Clients showing as disconnected until I restart message router (Windows 10 1709)

dubsdj

Really annoying problem:

clients show as disconnected from the console at every reboot. I have to then restart message router service (Which is already running).

I have checked firewall ports are open (Which they are)

checked logs, no errors.

Anyone else know how to fix this? I have other 1709 clients which are not experiencing this issue and some that are.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to dubsdj

    I read the article but it only suggests having a script to restart the service on startup. Is that really the only solution to this? 

    That's a bit annoying.

  • 0 in reply to dubsdj

    Hello dubsdj,

    as you see the last activity is from a month ago. Posts suggest that it's a "cooperative issue", i.e. it seems to surface only with Windows 10 1709 and RMS 4.1.1.127.
    I'd expect that it can be determined what has been changed since RMS 4.1.0.140 though there's not always a direct cause-effect chain and it might be almost impossible to determine the critical factor.
    I'd suggest that you open a support ticket even if it won't help immediately (or not at all) so that it becomes clearer that it is not an isolated issue.

    Christian

  • 0 in reply to QC

    Thanks Christian, I opened a ticket a few days ago but still haven't heard anything back from them (case still open). Perhaps they know about it and are working on resolution..

  • 0 in reply to dubsdj

    Unfortunately Sophos never found a solution to this. They did a remote session and escalated it to the highest level.

     

    Good news is that I solved the problem myself. I just changed the sophos message router service startup to "Delayed Auto Start". Problem solved!

  • 0 in reply to dubsdj

    Hi everyone,

    The reported issue is actively being investigated internally by our team. I will periodically keep this thread updated with further developments. As a temporary workaround, you can set the service to "Delayed Auto start" as mentioned by

    Regards,

    Gowtham Mani
    Community Support Engineer | Sophos Technical Support
    Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts
    If a post solves your question use the 'This helped me' link.

Unfiltered HTML