[Bug 456808] Re: Karmic-Networking (SAMBA) just does not work, even with detailed attention.

[Scott Grizzard]

Just out of curiosity, is preferred master set to "no" on all of the
computers?  Who is winning bcast elections?

- Scott

Joern Schimmelpfeng wrote:
> After upgrading to Karmic I have exactly the same problem. This is an
> very serious problem. Samba is completely useless and there is even no
> workaround mentioned here. How can this be classified as invalid/low?
>
> I'm going to downgrade now...
>
> Bye
> Joern
>
>> Karmic-Networking (SAMBA) just does not work, even with detailed attention.
>> https://bugs.launchpad.net/bugs/456808
>> You received this bug notification because you are a member of Ubuntu
>> Directory Services, which is subscribed to samba in ubuntu.
>>
>> Status in “samba” package in Ubuntu: Invalid
>>
>> Bug description:
>> Binary package hint: samba
>>
>> I have been tryiong to get my 3 PC's networked, for the past few Ubuntu releases, with no success.  As I have more experience with Ubuntu than most novice users, this may indicate something that needs substantial attention for Lucid. I don't expect a Windows Wizard, with an "out of the box" instant connection, but there is still way too much CLI as well as educated guessing in what should be a straightforward process. I know the network works, because I can get them connected in Windows XP.
>>
>> I have "system-config-samba", "winbind" and "smbfs" installed. I have confirmed my "workgroup" names are identical, and added the "netbios name" to all, also. In "Samba Server Configuration" the specific folders are all shared (indicated in Nautilus with share icon on folder) and is "Read/Write, Visible".
>>
>> When I go to "Places > Network", "Windows Shares on <workgroup>" I click and eventually only see one machine - this one.
>>
>> I have seen DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered." occasionally but always get the infamous "Unable to mount location. Failed to retrieve share list from server" everytime. Once, recently I did see one of the machine's names, but when I clicked on it, I then got the "share list" error.
>>
>> All are Karmic (beta) updated machines, but this has been through Jaunty back to about Dapper for me.
>>
>> This is the procedure I have used on all 3 machines:
>>
>> "1. sudo ufw disable
>>
>> 2. gksu gedit /etc/default/ufw
>> Find and change to this: IPT_MODULES="nf_conntrack_ftp nf_nat_ftp nf_conntrack_irc nf_nat_irc nf_conntrack_netbios_ns"
>>
>> 3. sudo ifconfig | grep Bcast
>> Look for "inet addr: and replace last segment  of this IP address with  "0/24".  In my case it's: 192.xxx.x.0/24. Now do:
>> sudo ufw allow proto udp to any port 137 from 192.xxx.x.0/24
>> sudo ufw allow proto udp to any port 138 from 192.xxx.x.0/24
>> sudo ufw allow proto udp to any port 139 from 192.xxx.x.0/24
>> sudo ufw allow proto udp to any port 445 from 192.xxx.x.0/24
>>
>> 4. Enable and confirm: sudo ufw enable | sudo ufw status
>>
>> 5. Add a user to the Database or change an existing user's password (as root) with smbpasswd:
>> sudo smbpasswd -a <username>
>> New SMB password: ######
>> Retype new SMB password: ######
>>
>> 6. Confirm with: sudo pdbedit -L
>>
>> 7. Paste this stanza into smb.conf:
>> [global]
>> workgroup = WORKGROUP_NAME
>> netbios name = NETBIOS_NAME
>> server string =
>> name resolve order = bcast host lmhosts wins
>> preferred master = no
>>
>> printing = cups
>> printcap name = cups
>> printcap cache time = 750
>> cups options = raw
>> load printers = yes
>> use client driver = yes
>> [printers]
>> comment = All Printers
>> path = /var/spool/samba
>> printable = Yes
>> create mask = 0700
>> browseable = No
>> guest ok = Yes
>> [print$]
>> comment = Printer Drivers
>> path = /var/lib/samba/printers
>> browseable = yes
>> read only = yes
>> guest ok = no
>>
>> 8. Each share is defined in a separate stanza in smb.conf. - In my case it's:  path = /home/<username>/XXXX_Shared-"X"
>> [ShareName]
>> path = /path_to/shared_directory
>> read only = no
>>
>> 9. Then: sudo chmod 1777 /path_to/shared_directory
>>
>> 10. Restart Samba: sudo /etc/init.d/samba restart."
>>
>> Again, this is not even attempting to network alternate OS's , this is strictly Karmic to Karmic to Karmic.

-- 
Karmic-Networking (SAMBA) just does not work, even with detailed attention.
https://bugs.launchpad.net/bugs/456808
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.