Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: LANMonkey on March 18, 2009, 06:50:49 PM

Title: How do you disable Windows workgroup services from SME?
Post by: LANMonkey on March 18, 2009, 06:50:49 PM

How do you disable Windows workgroup services from SME and at the same time keep the ability to backup to a Windows Workstation?  Especially, SME server keeps trying to broadcast for the service from the x.x.x.255 IP on ports 137 and 138 out of a network in a DMZ.  This is my primary irritation as it keeps popping up in the firewall logs. 

I want to keep the ability to backup to Windows out of the DMZ, but I don't want SME to provide any file sharing services for Windows.

Title: Re: How do you disable Windows workgroup services from SME?
Post by: Stefano on March 18, 2009, 07:11:34 PM

hi

not sure, but a

Code: [Select]

config setprop smbd status disabled
service smbd stop

should do what you are asking for..

NOTE: I don't have tested it.. :-)

HTH
ciao
Stefano

Title: Re: How do you disable Windows workgroup services from SME?
Post by: LANMonkey on March 19, 2009, 10:18:38 PM

Should I assume that the following commands will get it working again?

Code: [Select]

config setprop smbd status enabled
service smbd start


Title: Re: How do you disable Windows workgroup services from SME?
Post by: Stefano on March 19, 2009, 10:42:47 PM

of course.. ;-)
ciao
Stefano

Title: Re: How do you disable Windows workgroup services from SME?
Post by: janet on March 19, 2009, 11:56:31 PM

LANMonkey

Quote

config setprop smbd status enabled
service smbd start

Those commands are doing two different things.
One is setting the start up status in the configuration db file, so that when sme server starts, smbd will not run (if disabled) or run (if enabled).

The other is actually telling a service to start or stop and it's obvious which one does what.

eg common scenarios
you can stop the service, but it will still start up again when sme server is rebooted (with status=enabled).

...and vice versa, you can start the service, but it will not restart after a reboot (with status=disabled).