Koozali.org: home of the SME Server

Obsolete Releases => SME Server 9.x => Topic started by: smiit on January 23, 2015, 03:04:09 PM

Title: SME Behavior as a domain controller
Post by: smiit on January 23, 2015, 03:04:09 PM
Two questions about SME 9 server running as PDC for Win7Pro clients joined to Domain.

Win7 Firewall has 3 profiles available: Domain networks, Home or work (private) networks & Public networks.

Clients logged in to SME domain are shown connected to the name of the Home or work (private) network, not Domain networks.

1) Is this standard SME behavior because of NT4 style workgroup/domain controller, not full Samba 4 AD capability?

Also discovered clients getting repeated requests to Set Network Location in Win7Pro after rebooting/logging in. Clients appear to be 'forgetting' their LAN profile and have to keep selecting Work Network.

2) Has anyone else experienced this?

We did recently rename the Windows workgroup from example.local to just example to remove the .local which appeared to be prohibiting any Win8 clients from joining, as described here:

http://forums.contribs.org/index.php/topic,50840.msg256687.html#msg256687 (http://forums.contribs.org/index.php/topic,50840.msg256687.html#msg256687)

Thanks
Title: Re: SME Behavior as a domain controller
Post by: Stefano on January 23, 2015, 05:53:48 PM
if you are behind a firewall, disable firewall on the clients, it's useless and gives you only problems..
on the clients be sure to have an updated AV, nothing more and nothing less

workgroup name should never be something.somethingelse, just something
Title: Re: SME Behavior as a domain controller
Post by: MSmith on January 28, 2015, 02:29:54 PM
Quote from: Stefano on January 23, 2015, 05:53:48 PM
if you are behind a firewall, disable firewall on the clients, it's useless and gives you only problems..
on the clients be sure to have an updated AV, nothing more and nothing less

I'm afraid I must disagree here. The default Windows firewall at least offers some protection against malicious software that might get loose inside the firewall.

I do agree that third-party firewalls such as those found in "Internet Security" AV suites inflict more aggravation than protection when behind a router/firewall.
Title: Re: SME Behavior as a domain controller
Post by: smiit on January 28, 2015, 04:24:54 PM
Quote from: MSmith on January 28, 2015, 02:29:54 PM
I'm afraid I must disagree here. The default Windows firewall at least offers some protection against malicious software that might get loose inside the firewall.

I do agree that third-party firewalls such as those found in "Internet Security" AV suites inflict more aggravation than protection when behind a router/firewall.

Agreed.  Most users are on laptops and travel frequently/work remotely.  I wouldn't dream of disabling the built-in firewall.
Title: Re: SME Behavior as a domain controller
Post by: zatnikatel on February 17, 2015, 09:35:36 PM
the windows firewall is crap is easy to hack use zonealarm free version and dissable the windows firewall the services in windows
just my 2 cents i use ZoneAlarm free version never been hacked
Title: Re: SME Behavior as a domain controller
Post by: janet on February 17, 2015, 11:00:14 PM
smiit

Quote
Most users are on laptops and travel frequently/work remotely.  I wouldn't dream of disabling the built-in firewall.

Yes but IIRC you can tweak the settings in Windows so the firewall is disabled when the Notebook is physically connected to a LAN eg via Ethernet cable, & so on, but remains enabled for other use eg mobile connections via modem/3G etc. Read up on your Windows firewall setting capability.

A firewall enabled on a "workstation' that is behind a firewall provided by a SME server can cause many other unwanted issues, some of which you seem to be experiencing.