Go Back
1 Vote

rsynd Should Be Enhanced To Automatically Have A Dependency Upon Server/"LanmanServer"


Closed

rsynd Appears to have an explicit dependency on Server/"LanmanServer" when installing new services these dependencies should be explicitly listed just as the DHCP Client, Windows Event Log, and Workstation roles are:

User-added image

Failure to do so will cause 1355: The specified domain either does not exist or could not be contacted errors as documented here https://synergexresourcecenter.force.com/SiteAnswer?id=a2Z0d000000hX2YEAU

The root cause is unknown; its either Licensing or the fact that a network account is being used. If it really is because a network account is being used then the ask should be modified to do this ONLY if a network account is configured for the service.

7 Comments | Posted by Ace Olszowka to xfServer, xfServerPlus on 11/16/2018, 4:43 PM
Phillip Bratt
This is a bug; we've created tracker 38154 for it.

1/11/2019, 7:14 PM   0  
Phillip Bratt
We initially thought this was a missing dependency for xfServerPlus and thus a bug. After additional research, we determined that the dependency is only needed when using a domain account and not in all situations. We don’t believe there is a way to create a conditional dependency through Microsoft’s Service Control Manager (SCM). We are not planning additional research at this time but will leave this as an open idea and will consider any future customer input.

1/30/2019, 3:22 PM   0  
Ace Olszowka
Possible? https://serverfault.com/questions/24821/how-to-add-dependency-on-a-windows-service-after-the-service-is-installed

1/30/2019, 3:28 PM   0  
Steve Ives
Ace, apologies that there hasn't ben any action on this, somehow this thread got incorrectly tagged "do not review" and so it fell completely off the radar.

Can you provide some additional information about the exact scenario under which you see this error, because I have been trying to, but have completely failed to reproduce what you describe. From what you're describing, I assume that you are able to register the service successfully, but at boot time, on some systems, the service fails to start?

I have attempted to reproduce the scenario by stopping the service, then stopping and disabling the "Server" (LanmanServer) service, and restarting the service, but I don't repro what you are reporting.

I'm using a Windows Server 2019 VM which is an AD domain controller. Do you think it's possible I don't see a repro because I'm on the DC?

9/21/2020, 9:14 PM   0  
Mark Vinten
Hi Steve,

Based off what I have read here, I would surmise that this is an issue with a domain-based server (not dc) using windows authentication.  As such, the service is needed to properly authenticate with the domain controller.  When you are on a domain controller, that acts pretty much like a workgroup server because the SAM is local to the domain controller (all be it the AD version).

I would suggest creating a second domain-joined VM and then stopping the service on there, then trying to use windows auth via xfserver/xfserverplus as a starting point.

Thanks,

Mark.

9/25/2020, 8:18 AM   0  
Steve Ives
Thanks, Mark, you raise a good point, and I will try exactly what you suggest.

9/25/2020, 5:31 PM   0  
Steve Ives
I finally got around to doing some more testing on this, following Mark's suggestion to add a non-DC server to the AD domain, then configuring xfServer and xfServerPlus on that server. No matter what I do with the "Server" (LanmanServer) service, xfServer and xfServerPlus both start, stop, restart and operate just fine.

Unless anyone else has any suggestions as to how to repro the reported issue, we're just going to have to put this to one side.

1/10/2021, 11:50 PM   0  
Please log in to comment on this idea.