Automatically save login information via SMB

[AzP]

When restarting Samba, the log says:

Code: Select all

root@b3:~# cat /var/log/samba/log.all
[2011/10/29 16:00:57.143146,  0] param/loadparm.c:7617(lp_do_parameter)
  Global parameter security found in service section!
[2011/10/29 16:01:23.873720,  0] lib/util_sock.c:474(read_fd_with_timeout)
[2011/10/29 16:01:23.873973,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transportslutpunkten är inte förbunden
  read_fd_with_timeout: client 0.0.0.0 read error = Förbindelse borttagen av partnern.
[2011/10/29 16:01:23.880524,  0] lib/util_sock.c:474(read_fd_with_timeout)
[2011/10/29 16:01:23.880749,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transportslutpunkten är inte förbunden
  read_fd_with_timeout: client 0.0.0.0 read error = Förbindelse borttagen av partnern.

[AzP]

I'm wondering if I'm missing a user 'guest' on my B3. I read the Samba help, which says:

Code: Select all

guest ok = yes

    If this parameter is set to yes, no password is required to connect to the printer's service. Access will be granted with the privileges of the guest account. On many systems the guest account will map to a user named "nobody." This user will usually be found in the UNIX passwd file with an empty password, but with no valid UNIX login. On some systems the guest account might not have the privilege to be able to print. Test this by logging in as your guest user using su - guest and run a system print command like: 

lpr -P printername /etc/motd

But I can't do 'su - guest', it only outputs

Code: Select all

root@b3:/var/log/samba# su - guest
Unkown id: guest

[AzP]

I found a way of fixing the issue! Instead of just writing my user name and password in the log-in dialog, I have to enter the DOMAIN\username.

At the same time as trying that, I also changed my workgroup to LOCAL, so it's the same one as the B3.

Found this here:

What worked for me was to enter DOMAIN\username as the username when first being asked for logon details for the mapped share. Make sure the DOMAIN is the same workgroup or domain the computer is a part of. Otherwise the credentials get lost on reboot.

Now it works!