Bug #2070 - problems starting as service on XP
SourceForge user: markodaris
FYI: installed v1.1.6 on windows. I wanted to install
synergy (client) to startup as a service when the
computer starts.
I found some problems: the service depends on Computer
Browser service - the problem is that if you have a
Win2k or WinNT PDC on the net (primary domain
controller) and a use WinXP machine, then the XP
machine will win the elections as the domain browser
which is not desirable. To disable this you need to
Disable the Computer Browser service - doing so synergy
will not start anymore.
Workaround: use regedit and search for synergyc -
delete the DependsOn* entries. Set the service to
restart on failure after 0 minutes.
You need to find some other service for synergyc to
depend on.
I also found that while the service is starting it
happens that it cannot resolve the hostname - I used
the IP instead, now it works.
#1
SourceForge user: crs23
Logged In: YES
user_id=21565
yep, this was reported in the forums. i wish i knew what
service to depend on so synergy would be guaranteed to be
able to lookup names. for now i'll just remove the dependency.
#2
SourceForge user: crs23
Logged In: YES
user_id=21565
fixed in 1.1.7. unfortunately synergy may now attempt to
start before the service that performs name lookup. i wish
i knew what service to depend on.
#3
SourceForge user: nobody
Logged In: NO
I wish I knew also... With two computers we had success by
setting Recovery's First Second and Subsequent failures to
"Restart The Service" and "Reset service after" to 0 minutes.
Maybe you can try to depend on the "Workstation Service"...
Or on NetLogon (who itself depends on "Workstation
Service"). It seems most of the network services on XP have
the dependency to "Workstation Service" (also the Computer
Browser service has it).
BTW: it seems that there is a problem with name resolution
also if you depend on Computer Browser. I mean I remember
that the first problem I had when installing synergyc
service was that it could not resolve the hostname - so I
entered the IP. So it seems that Computer Browser does not
ensure DNS name resolution (which is obvious from the
services description - it doesn't have anything to do with
DNS). Maybe you could try and add the dependency to DNS
client service.
Write comment