Karmic-Networking (SAMBA) just does not work, even with detailed attention.

Asked by emarkay

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.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu samba Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Chuck Short (zulcss) said :
#1

What happens when you disable ufw?

Regards
chuck

Revision history for this message
emarkay (mrk) said :
#2

Chuck, that's "Step One". Is that correctly formatted?
 Shouldn't that be a native part of Samba Configuration since I understand UFW is installed and activated by default? This example is one of the reasons I, and many others, are having troubles with Ubuntu Networking (as evidenced on the Ubuntu Forums).

Revision history for this message
emarkay (mrk) said :
#3

Also, what is "Incomplete" about this report or issue, as indicated by yis change in Status?

Revision history for this message
Thierry Carrez (ttx) said :
#4

What are you using "winbind" for exactly ?

Revision history for this message
Thierry Carrez (ttx) said :
#5

Also do you manage to access the shares by typing directly "smb://IPADDRESS/sharename" in the Nautilus location bar ? If yes, does "smb://MACHINENAME/sharename" work ?

Revision history for this message
Chuck Short (zulcss) said :
#6

@emarkay:

Yes that is the first step

You should just able to do sudo ufw allow samba as well. Also assuming that all three of your computers are apart of the same workgroup. What does /var/log/samba/log.smbd and /var/log/log.nmd say (if you can attach those as well) Also can you attach the output of testparm

Thanks
chuck

Revision history for this message
emarkay (mrk) said :
#7

#4: Winbind, because somewhere it was recommended to have installed.

#5:

1. "smb://192.168.x.xxx/sharename" in Nautilus (Ctrl-L) gives: the shared directory on this machine only, after entering my share password.

2. "smb://<name of thus PC>/sharename"gives: the shared directory on this machine only, after entering my share password.

3. "smb://<name of a remote PC>/sharename" gives: "Could not display "smb://wings/sharename/". Error: Failed to mount Windows share. Please select another viewer and try again."

#6:

1. Output of /var/log/samba/log.smbd:

 "[2009/10/18 12:44:36, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/18 12:44:37, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/18 12:44:37, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/18 12:52:59, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/18 12:52:59, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/18 12:52:59, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/18 15:41:10, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/18 15:41:11, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/18 15:41:11, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/18 15:41:12, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/18 15:41:12, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/18 16:09:35, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/18 16:09:37, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/18 16:09:37, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/18 16:09:39, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/18 16:09:39, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/19 09:16:07, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/19 09:16:08, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/19 09:16:08, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/19 16:42:42, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/19 16:42:43, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/19 16:42:43, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/19 16:42:45, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/19 16:42:45, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 08:48:08, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/20 08:48:09, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 08:48:09, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 08:48:10, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 08:48:10, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 09:01:28, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/20 09:01:29, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 09:01:29, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 09:01:31, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 09:01:31, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 10:22:47, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/20 10:22:47, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 10:22:47, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 10:22:47, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 10:22:47, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 13:01:01, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/20 13:01:02, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 13:01:02, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 13:01:04, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 13:01:04, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/20 15:32:48, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/20 15:32:49, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 15:32:49, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 21:09:11, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/20 21:09:12, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/20 21:09:12, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/21 10:54:03, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/21 10:54:04, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/21 10:54:04, 0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2009/10/21 10:54:05, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/10/21 10:54:05, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use"

2. /var/log/log.nmd : I do not have that file in /var/log/. I have only "lastlog. lpr.log and lpr.log.1 for "L" files.

3. testparm:

"Load smb config files from /etc/samba/smb.conf
Processing section "[ShareName]"
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
 workgroup = XXXXXXX
 netbios name = DESKTOP
 server string = %h server (Samba, Ubuntu)
 map to guest = Bad User
 obey pam restrictions = Yes
 pam password change = Yes
 passwd program = /usr/bin/passwd %u
 passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
 unix password sync = Yes
 syslog = 0
 log file = /var/log/samba/log.%m
 max log size = 1000
 name resolve order = bcast host lmhosts wins
 printcap name = cups
 dns proxy = No
 panic action = /usr/share/samba/panic-action %d
 cups options = raw
 use client driver = Yes

[ShareName]
 path = /home/<username>/<shared folder name>
 read only = No
 cups options =
 use client driver = No

[printers]
 comment = All Printers
 path = /var/spool/samba
 create mask = 0700
 guest ok = Yes
 printable = Yes
 cups options =
 use client driver = No
 browseable = No
 browsable = No

[print$]
 comment = Printer Drivers
 path = /var/lib/samba/printers
 cups options =
 use client driver = No"

 Also, for all, here's the thread from the Ubuntu Message board:http://ubuntuforums.org/showthread.php?t=1296111

Revision history for this message
Thierry Carrez (ttx) said :
#8

#4 Re:"Winbind, because somewhere it was recommended to have installed."
<<winbind is a component of the Samba suite of programs that solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine>>

I fail to see how winbind can help in your scenario (since you don't use a Windows domain) and I can certainly imagine how it can lead you to failure if badly configured.

Please try with just "samba" installed, and not "winbind".

#5 What does "smb://<IP of a remote PC>/sharename" return ?

#6 2. it's /var/log/samba/log.nmbd. And we need those of the remote PC, the one that you're trying to connect to and fail.

I'm still trying to figure out what exact bug you're reporting here, apart from general failure to configure SMB networking on your machines, and how much simpler this should be (which is not a bug). I suppose it's the "can't access remote PC via smb:// in Nautilus, while I can access it just fine locally". If I got it right, could you:

1/ try accessing the share using smbclient rather than Nautilus ? Try smbclient //remote_system/share_name
2/ try to define "guest ok = yes" in your share to rule out account name issues.

Revision history for this message
emarkay (mrk) said :
#9

#8: Regarding Winbind, all 3 machines ALSO have Win XPSP3 (NTFS) and I do want and expect to be able to connect to those when booted as such. But you now see all the "bogus" and misleading info that is "out there" and we NEED to have Lucid address this!

Thierry, I will get the additional information in an hour or so, but your statement: "I'm still trying to figure out what exact bug you're reporting here," needs clarification:

There are many, many many users of Ubuntu that have problems with networking (Google it or just look at the messageboards.). it MUST be as "simple" as Microsoft has configured it, for "noobs" and businesses alike, or this will ALWAYS be a negative for Ubuntu.

Just use "Bug Number One" as a reason!

Revision history for this message
emarkay (mrk) said :
#10

#8:
1. Winbind uninstalled vua Synaptic.

2. $ smb://192.168.x.xxx/sharename
bash: smb://192.168.x1.xxx/sharename: No such file or directory

3. /var/log/samba/log.nmbd
Date: Thursday, October 22, 2009, 1:39 PM
> [2009/10/18 13:34:03, 0]
> nmbd/nmbd.c:71(terminate)
> Got SIGTERM: going down...
> [2009/10/18 13:37:35, 0] nmbd/nmbd.c:854(main)
> nmbd version 3.4.0 started.
> Copyright Andrew Tridgell and the Samba Team
> 1992-2009
> [2009/10/18 13:37:35, 0]
> nmbd/nmbd.c:693(open_sockets)
> [2009/10/18 14:07:06, 0] nmbd/nmbd.c:854(main)
> nmbd version 3.4.0 started.
> Copyright Andrew Tridgell and the Samba Team
> 1992-2009
> [2009/10/18 14:07:08, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<20> on subnet 192.168.1.102.
> [2009/10/18 14:07:08, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<20> on subnet 192.168.1.102
> [2009/10/18 14:07:08, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<03> on subnet 192.168.1.102.
> [2009/10/18 14:07:08, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<03> on subnet 192.168.1.102
> [2009/10/18 14:07:08, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<00> on subnet 192.168.1.102.
> [2009/10/18 14:07:08, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<00> on subnet 192.168.1.102
> [2009/10/18 14:07:25, 0] nmbd/nmbd.c:71(terminate)
> Got SIGTERM: going down...
> [2009/10/18 15:29:59, 0] nmbd/nmbd.c:854(main)
> nmbd version 3.4.0 started.
> Copyright Andrew Tridgell and the Samba Team
> 1992-2009
> [2009/10/18 15:29:59, 0]
> nmbd/nmbd_subnetdb.c:206(create_subnets)
> create_subnets: No local IPv4 non-loopback
> interfaces !
> [2009/10/18 15:29:59, 0]
> nmbd/nmbd_subnetdb.c:207(create_subnets)
> create_subnets: Waiting for an interface to appear
> ...
> [2009/10/18 15:30:11, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<20> on subnet 192.168.1.102.
> [2009/10/18 15:30:11, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<20> on subnet 192.168.1.102
> [2009/10/18 15:30:11, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<03> on subnet 192.168.1.102.
> [2009/10/18 15:30:11, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<03> on subnet 192.168.1.102
> [2009/10/18 15:30:11, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<00> on subnet 192.168.1.102.
> [2009/10/18 15:30:11, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<00> on subnet 192.168.1.102
> [2009/10/18 15:36:45, 0]
> nmbd/nmbd_packets.c:1072(process_browse_packet)
> process_browse_packet: Discarding datagram from IP
> 192.168.1.101. Source name DESKTOP<00> is one of our
> names !
> [2009/10/18 15:48:52, 0]
> nmbd/nmbd_packets.c:1072(process_browse_packet)
> process_browse_packet: Discarding datagram from IP
> 192.168.1.101. Source name DESKTOP<00> is one of our
> names !
> [2009/10/18 15:52:12, 0] nmbd/nmbd.c:71(terminate)
> Got SIGTERM: going down...
> [2009/10/18 15:53:06, 0] nmbd/nmbd.c:854(main)
> nmbd version 3.4.0 started.
> Copyright Andrew Tridgell and the Samba Team
> 1992-2009
> [2009/10/18 15:53:06, 0]
> nmbd/nmbd_subnetdb.c:206(create_subnets)
> create_subnets: No local IPv4 non-loopback
> interfaces !
> [2009/10/18 15:53:06, 0]
> nmbd/nmbd_subnetdb.c:207(create_subnets)
> create_subnets: Waiting for an interface to appear
> ...
> [2009/10/18 15:53:18, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<20> on subnet 192.168.1.102.
> [2009/10/18 15:53:18, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<20> on subnet 192.168.1.102
> [2009/10/18 15:53:18, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<03> on subnet 192.168.1.102.
> [2009/10/18 15:53:18, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<03> on subnet 192.168.1.102
> [2009/10/18 15:53:18, 0]
> nmbd/nmbd_mynames.c:35(my_name_register_failed)
> my_name_register_failed: Failed to register my name
> DESKTOP<00> on subnet 192.168.1.102.
> [2009/10/18 15:53:18, 0]
> nmbd/nmbd_namelistdb.c:307(standard_fail_register)
> standard_fail_register: Failed to register/refresh
> name DESKTOP<00> on subnet 192.168.1.102
> [2009/10/18 15:58:50, 0]
> nmbd/nmbd_packets.c:1072(process_browse_packet)
> process_browse_packet: Discarding datagram from IP
> 192.168.1.101. Source name DESKTOP<00> is one of our
> names !
> [2009/10/18 15:59:13, 0] nmbd/nmbd.c:71(terminate)
> Got SIGTERM: going down...
> [2009/10/21 12:33:35, 0] nmbd/nmbd.c:854(main)
> nmbd version 3.4.0 started.
> Copyright Andrew Tridgell and the Samba Team
> 1992-2009
> [2009/10/21 12:33:35, 0]
> nmbd/nmbd.c:693(open_sockets)
> [2009/10/22 12:44:47, 0] nmbd/nmbd.c:854(main)
> nmbd version 3.4.0 started.
> Copyright Andrew Tridgell and the Samba Team
> 1992-2009
> [2009/10/22 12:44:47, 0]
> nmbd/nmbd.c:693(open_sockets)

4. " smbclient //remote_system/share_name"
(Why does it ask for password - it's not SUDO?)
Connection to remote_system failed (Error NT_STATUS_UNSUCCESSFUL)

5. "try to define "guest ok = yes" in your share to rule out account name issues" - can you specify where?

Also, is the original attachment of things I added and changed correct?

Revision history for this message
emarkay (mrk) said :
#11

Again, what is "Incomplete" on this Bug submission?

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) said :
#12

My bad -- I didn't mean to mark this Confirmed -- it stays Incomplete.

emarkay, this bug is marked Incomplete because we need more information in order to be able to understand and potentially fix the problem you're experiencing.

There's a number of things we'd need to know:

- What happens if you disable ufw, and leave it disabled as you try to see the shares, does it work?
- What about if you type smb://<ip of another machine among the three>/<sharename> in Nautilus. Can you see the share?

I'm curious as to this issue since I'm seeing a similar problem on a server where Samba was just installed (through tasksel and selecting Samba server), reported here: bug #458671

Revision history for this message
Thierry Carrez (ttx) said :
#13

@emarkay:

1/ Windbind is used to integrate with Windows domains. It is not useful to access SMB shares on individual workstations being part of a common workgroup.

2/ The main issue you're reporting here is how much easier it should be to set up shared files through Windows SMB networking on Ubuntu. Launchpad bugs are not used to track such generic bugs (bug #1 being an exception), but rather specific issues. You should use the Ubuntu Brainstorm site for this request.

3/ The method you're using is *not* the recommended, simplest way to do it. Doing it through samba manual configuration requires a good understanding on how samba works, as this is a very complex piece of software. Your remarks 4 and 5 in comment 10 seem to show you're underdocumented in that area.

4/ I'd recommend using the existing tools integrated on the Ubuntu Desktop instead (right-click on a folder in Nautilus and select "Share options"). That's the recommended, dead-simple way of doing it. Unfortunately your tries at a manual samba/winbind setup might now interfere with this feature working correctly. I'd recommend you purge samba samba-common winbind from synaptic before you try to enable the shares in Nautilus.

Revision history for this message
emarkay (mrk) said :
#14

First, sorry about "sharename" - I didn't even know about that - I guess "ShareName" is the default?
Second - I notice that the folders I have made as "shared" are no longer, on both machines - I reenabled them - I did not know when and how this had happened.

#12:
1. Type in "Location" in Nautilus: "smb://192.168.x.xxx/ShareName" gets this:
"Could not display "smb://192.168.x.xxx/sharename/".
Error: Failed to mount Windows share
Please select another viewer and try again."

2." $ sudo ufw disable
[sudo] password xxxx: xxxx
Firewall stopped and disabled on system startup"
and repeating the above gets the same response.

#13
:2 No the issue is, "It doesn't work!" - the suggestions are added as a reference, and have no bearing on the actual issue.

:3 Well I took the information direct from the Ubuntu Wiki, and the Ubuntu Messageboards, as well as prior experiments from other online sources - this validates my "suggestions" and leads to the conclusion that a/the problem may also then be (emphasized) the "underdocumentation" as well!

*****
Comments indicate possible "operator error" and therefore I am going to reload a fresh install of the Karmic RC on both machines. (I wanted to do this at the release anyway to test, but I can use the RC today.) After a successful boot and update/upgrade, I will then do nothing except what I have documented here,
http://ubuntuforums.org/showthread.php?t=1287543
on both machines, AND create a directory/folder on each machine that is indicated as "shared" in Nautilus.

Please then give me a specific procedure to test. This should identify if it's "operator error" or "Ubuntu error". I expect to have this completed in a few hours, and when I see procedures here to test, I will make those first priority today.

MRK

Revision history for this message
emarkay (mrk) said :
#15

I have 2 "virgin" Karmic machines now, waiting to test.
Let's pretend I am a new Ubuntuite and want to have 2 PC's communicate in Ubuntu and Windows XP.
If there is a bug we'll uncover it and if there is a config issue we'll clarify it, and in the end, there will be a legit and validated tutorial on Samba Networking for all.
Email or let's get started here.

Revision history for this message
bwat47 (bwat47) said :
#16

I have a fresh install of karmic and no dice. This worked perfectly in previous versions. This is a bug with samba and nothing to do with user error.

Revision history for this message
emarkay (mrk) said :
#17

Well?
If not for Karmic, then for Lucid!

Revision history for this message
Thierry Carrez (ttx) said :
#18

Converting to a question since the reporter asks for the recommended way to share files in Ubuntu.

Revision history for this message
Thierry Carrez (ttx) said :
#19

With the release I have no time to compile detailed instructions...

The recommended way is, on host A to select a folder in Nautilus, right-click on it and select share options.
If you enable the share, it should prompt you to install extra support. The only trick I remember is that you'll need to log out and log in again after enabling the share, not sure this was fixed in karmic.
Then on host B, you can access the share by opening "smb://A" in nautilus (obviously replacing "A" with the first machine hostname). If that doesn't work, it means you've a broken IP resolution (try "ping A" to see if it works), and you should try smb://IP.ADDRESS.OF.A instead.

Revision history for this message
emarkay (mrk) said :
#20

From the forum, on this issue, today:

"Certainly your problem is the samba naming daemon nmbd. I haven't installed Karmic.
<<<<< You should report this as a bug. >>>>> (emphasis added)
Under "Processes" surely there's something about file sharing or network sharing? What's there that's possibly related to windows networking or sharing?"

I give up - I'll just wait until I really have to get a network going in Linux. Thanks.

MRK

Revision history for this message
Marcel (oosterh) said :
#21

Hi Emarkay,

I had the same problem as you describe.
Sharing of files between karmic and vista is now working again,
the way it worked for jaunty.

I had to comment out the lines related to printing..
File sharing works when:
# load printers = yes
; printing = cups
; printcap name = cups

File sharing NOT working when:
   load printers = yes
   printing = cups
   printcap name = cups

I had the same symptons as you describe:
Same error about cups in the log file,
and nmbd was not running.

sudo /etc/init.d/samba status
now gives:
* nmbd is running
 * smbd is running
while with printing enabled it said nmbd not running.

So of course i understand this is only half a fix; the printer is not shared anymore,
but i hope it sets you in the right direction of fixing your problem.

Greetings.

Revision history for this message
emarkay (mrk) said :
#22

FWIW, this is still an issue for me, 2 (plus) years later, and a quick review of the Ubuntu Forum Message Boards indicate that there are still fundamental flaws in networking configuration and operation in Ubuntu, when using Samba, both natively and with other ooperating Systems. I also see more than one indicating a potential additional issue with wireless networked clients.

I was prepared to devote full days and virgin machines to address this issue a long while ago, but was basically rebuffed, and it hasn't been an important enough issue for me to address with 100% effort. However, as I just completely reinstalled Lucid 10.04.3 on one of my machines and "just for fun" spent some time trying to network to another Lucid machine, and still, no success.

If I was the only one saying that "Samba doesn't work" or "Networking Ubuntu is not intuitive" or similar, I could understand the lack of attention. However, I am just dumbfounded that there's no "point and click" configuration (I recall Windows 95 had that, but yes, I know this is Linux...), but moreso, that there is not at least updated and accurate official documentation from Canonical on getting PC's networked in Ubuntu Lucid and above.

Thus teh question remains: How to network 2 or more PC's in Ubuntu.

Revision history for this message
Launchpad Janitor (janitor) said :
#23

This question was expired because it remained in the 'Open' state without activity for the last 15 days.