Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: ZS-Man on January 09, 2015, 11:21:00 am
-
Hi, I have Zentyal4 installed as PDC. Win7 and Linux client joined to domain, users can login. On zentyal is created share folder, but this share is not visible on clients in browse network. Manual connection by IP address of PDC works fine.
So is there any additional settings for show zentyal shares by netwok browsing?
Browsing shares on another server (freenas) connected to zentyal domain works fine.
Thanks.
-
I have the same issue;
I can manually navigate to the share (and use it fine) , but it will NOT simply show in Windows7.
I have also tried to manually change and add smb.conf to include
(note: you need to change the smb.conf.mas file to make changes permanent)
wins support = yes
local master = yes
preferred master =yes
No change , Still not visible to Win7 network .
I have also played with all settings re: dhcp/dns, etc, still have found no solution.
pls HALPz :)
-
The network discovery code not implemented in Samba4!
-
would this explain why all seemed fine when I was using 3.5? (I have not upgraded, I am working with a fresh install of 4)
Is there a work around for this, or samba addon ?
-
can anyone else confirm?
I cant help but think there is just something silly I am missing here - I read that one person with this issue had a dns setup issue, but they did not specify. I have re-re-re-checked all I can think of
thx
-
Hi is there a solution for this problem?i can't find a solution..
-
Same problem Here, no solution found. It's really annoying.
Users will see it as a drawback from before :'(
-
i don't understand if is a problem of zentyal 4 or if there is something to configure
-
Sure it's annoying.
I ve try many system for supporting file sharing
freenas => serveur is discovered by network (under win 7 & 8.1)
nas4free ==> same
synology => same
zentyal 3.4 ==> same
zentyal 3.5 ==> no more (dont look for configuration a long time)
zentyal 4.0 ==> no more (even by changing smb.conf.mas with addition of local master/preferred master/win support)
This is really annoying, because common user dont know how to add a network directory, they only know how to search on network their server.
without this function, i all have to mix installation with
- zentyal (dhcp, openldap, openvpn, may be groupware is enough stable)
- NAS (file sharing, owncloud, zarafa)
-
KISSMANIAC :"This is really annoying, because common user dont know how to add a network directory, they only know how to search on network their server."
this is the real problem..i don't understand why this thing is not annoying others people..
-
The problem is linked to a known bug on samba/unbuntu.
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1321369
The service nmbd allowing network discover is not started.
First workaround is to launch nmbd service manually : sudo service nmbd start.
After Zentyal server is detected by windows machine.
I have not found currently how to correct the starting of service nmbd. Installation of samba 4.2 ?
-
The problem is linked to a known bug on samba/unbuntu.
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1321369
The service nmbd allowing network discover is not started.
First workaround is to launch nmbd service manually : sudo service nmbd start.
After Zentyal server is detected by windows machine.
I have not found currently how to correct the starting of service nmbd. Installation of samba 4.2 ?
The Zentyal deliberately does not start the nmbd service.
In vain I start it manually nmbd the service does not work!
-
i spent almost night trying nmbd service starting at boot without success. I am very far from being an unix user.
Last time i build a linux core i was 15 years old ( 35 five now....)
I am confusing between upstart an traditionnal sysvinit system for booting service...
may be i ll try zentyal 3.4 instead of 4.0 snif.
-
The network discovery code not implemented in Samba4!
You are not quite right.
Samba4 consists actually of 2 pieces of code: Samba4 and Samba3 code.
Neighborhood visibility functionality is at Samba3 code part.
At the moment neighborhood browsing doesn' t work if Samba4 acts as AD DC, and net browsing is not implemented in samba4 daemon and samba4 daemon doesn' t start nmbd daemon responsible for it.
But if Samba4 acts not as AD DC, nmbd can be to start, and you will see Zentyal server computer in your neighborhood environment at Windows.
And there is 2nd but: I got neighborhood browsing working even with AD DC Samba4 for earlier 4.1.x branch versions, for the latest i didn' t check. I told developers about this 'magic' variables where such condition could be reached at. May be they closed up this way.
-
But if Samba4 acts not as AD DC, nmbd can be to start, and you will see Zentyal server computer in your neighborhood environment at Windows.
Sorry but in zentyal what is the procedure to disable AD DC?i'm confusing
-
As I said there is no necessary to disable AD DS functionality.
There is necessary to 'activate' some parameter at Samba4 and edit start script.
I didn' t check for 4.1 versions, but for 4.0 worked.
-
As I said there is no necessary to disable AD DS functionality.
There is necessary to 'activate' some parameter at Samba4 and edit start script.
I didn' t check for 4.1 versions, but for 4.0 worked.
Could you tell me what you have done in particular and what is the right procedure?
Cheers
-
Hi is there a solution for this problem?
-
in my case:
when the Samba-computer is on same subnet(192.168.6.1) as client(192.168.6.2), then a client will see in browse network icon of Samba-computer
when the Samba-computer is on another subnet(192.168.1.1) as client(192.168.6.2), then a client will NOT see in browse network icon of Samba-computer and is necessary write \\Samba-computer
-
I used to work with MS Windows Servers, but I'm now looking for an alternative for the MS AD and Domain services. Therefore the past couple of days I've been trying out, among others, Zentyal. I have to say that i.m.h.o. Linux is still light years behind. The way services are dealt with is ridiculously complicated and very limited in possibilities as compared to Windows. I honestly believe they should work on that. At the moment it's a mess with like 4 or 5 different inconsistent ways of handling them :o.
Anyhow, I also had the problem of not being able to browse the Zentyal managed shares. I found out that it was indeed the NMBD service. When I manually start it (/etc/init.d/nmbd restart) the server becomes browsable. However, even though I tried to set the service to auto-start upon booting, that somehow fails. Therefore I've created a workaround:
create a script:
/opt/zentyal/startnmbd.sh
in the script add these lines:
#! /bin/sh
service nmbd start
in /etc/rc.local at the bottom add (before exit 0):
bash /opt/zentyal/startnmbd.sh
That worked for me.
Hope this helps
Edit: btw: It takes a while before the nmbd service will be started with the above method, but eventually it will.
-
I hope it is OK to dig up this old thread, but none of the previous suggestions worked for me. To solve the problem I added the following to /etc/samba/smb.conf and restarted the service.
#/etc/samba/smb.conf
winbind nss info = rfc2307
winbind trusted domains only = no
winbind use default domain = yes
winbind enum users = yes
winbind enum groups = yes
Everything seems to work now. Could someone follow up and let me know if this is going to cause problems somewhere else down the line?
-
Not working for me :(
-
Sorry, I forgot the sudo in the last bit:
create a script:
/opt/zentyal/startnmbd.sh
in the script add these lines:
#! /bin/sh
service nmbd restart
in /etc/rc.local at the bottom add (before exit 0):
sudo bash /opt/zentyal/startnmbd.sh
That worked for me.
Hope this helps
Edit: btw: It takes a while before the nmbd service will be started with the above method, but eventually it will.
This REALLY works for me.
-
Thanks por previous posts
This is what i did
For Zentyal 4.x
# update-rc.d nmbd defaults
# /etc/init.d/nmbd start
# /etc/init.d/nmbd status
For Zentyal 5.x
# systemctl enable nmbd.service
# systemctl start nmbd.service
# systemctl status nmbd.service
Reboot, it works
Regards, Saludos