Hello,I've been trawling through the task of setting up samba on the server in the network, however I'm come to a point where I've run out of ideas and search terms.
Hey guys, I'm guessing the update to samba 4 has broken my samba partially, my samba shares seem to no longer be visible, but I can still access them. Probably an out of date config file, any chance of help with it?These are super simple shares for my family home, no passwords, simple direct guest access. Windows computers are the main clients, other than my own linux ones.
I have a configured samba server on a Suse 11 machine
the problem is that when the samba server is connected to the network
the workgroup gets blocked, when i click on view workgroup computers in my network places, of a windows machine, i get a message telling that my workgroup is not accessible
when the samsa server is not on there is no problem with the workgroup
Thanks for the replie
I've read several threads regarding the setup and use of Samba, and Samba has always been working fine until recently. I didn't change anything, but for some reason, it appears that Samba only resolves hosts on the default "Workgroup" workgroup. However, the /etc/samba/smb.conf file is setup to use a different workgroup.
In my setup, I have a FreeBSD (soon to be Debian) server hosting multiple working samba shares. I access these shares from my Windows 7 laptop and Ubuntu 12.10 desktop, all on the same LAN segment. I can mount and use the shares without any trouble. However, my server machine does not show up under "Network Devices" under Win7 or Ubuntu.
I have one Windows 7 machine and when on Fedora 17 64bit (default install, nothing changed) I cannot browse the network shares. After installing Samba and Samba-Client, I am able to see the Windows workgroups (MSHOME and WORKGROUP). I can browse MSHOME which houses a XP machine with no shares. I cannot browse WORKGROUP, which contains the Windows 7 Machine.