Page 1 of 4 123 ... LastLast
Results 1 to 10 of 40

Thread: Samba on Ubuntu 13.10

  1. #1
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Samba on Ubuntu 13.10

    Just recently installed Saucy Salamander on Pentium(R) Dual-Core CPU E5300 @ 2.60GHz × 2.
    It's 32 bit with 2 Gig Ram.

    I wanted to share files with my Windows 7 workgroup on my home network.

    So, I installed Samba Server.

    Now, here's the curious thing. From the Ubuntu machine I can browse the network. I cannot retrieve the share list from the Windows Workgroup that shows on the network in the Ubuntu machine, but the actual Windows 7 machines also show on the network and I CAN open them, provide the login passwords and get the shared files on the Windows machines. My first question and puzzlement is why can I get at the files that way but not able to retrieve the shares through the workgroup? But I have a more serious problem.

    Although somehow Samba is connecting my Ubuntu machine with the Windows computers on the Windows network, although I have shared folders on the the Ubuntu machine it refuses connection through the Ubuntu network folder to itself. And, none of my Windows machines can see the Ubuntu machine on the network at all.

    I saw something about using the Ubuntu machine's IP address from Windows 7 Search (//IP address), but that doesn't work at all. I've tried rebooting in various sequences, but nothing seems to work. All my Windows computers are seeing each other on the Windows workgroup without any problem. But none of at hem can see the Samba running Ubuntu machine. I've been battling with this all day with no success.

    Someone please help.

  2. #2
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    Continued piddling...Windows 7 network computers show the name of the Ubuntu computer in their network but when I click on the name they cannot "find" the path??? I find it strange that Ubuntu computer (when I browse the network) sees itself and only one Windows computer plus the Windows Network. Clicking on the Windows Network shows the Windows Homegroup. And, clicking on that shows all the Windows networked computers AND the Ubuntu one. I can drill down into the Windows computers but trying to open the Ubuntu one (from the Ubuntu computer) immediately returns "Unable to access location. Failed to retrieve share list from server: connection timed out." Of course Samba is running - how else would I be able to reach the Windows networked computers?

    Help, please.

  3. #3
    Join Date
    May 2008
    Location
    SoCal
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    Quote Originally Posted by ray_silva View Post
    Continued piddling...Windows 7 network computers show the name of the Ubuntu computer in their network but when I click on the name they cannot "find" the path??? I find it strange that Ubuntu computer (when I browse the network) sees itself and only one Windows computer plus the Windows Network. Clicking on the Windows Network shows the Windows Homegroup. And, clicking on that shows all the Windows networked computers AND the Ubuntu one. I can drill down into the Windows computers but trying to open the Ubuntu one (from the Ubuntu computer) immediately returns "Unable to access location. Failed to retrieve share list from server: connection timed out." Of course Samba is running - how else would I be able to reach the Windows networked computers?

    Help, please.
    From the Ubuntu command line, post the output of these commands
    Code:
    pgrep -l mbd
    
    smbtree -d3
    -BAB1

  4. #4
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    pgrep:
    1602 nmbd
    19570 smbd

    smbtree:
    lp_load_ex: refreshing parameters
    Initialising global parameters
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    params.cm_process() - Processing configuration file "/etc/samba/smb.conf"
    Processing section "[global]"
    WARNING: The "null passwords" option is deprecated
    added interface ham0 ip=2620:9b::190c:bd2e bcast=2620:9b::ffff:ffff netmask=ffff:ffff:ffff:ffff:ffff:ffff::
    added interface wlan0 ip=fe80::208:54ff:fe8d:99f%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
    added interface ham0 ip=fe80::7879:19ff:fe0c:bd2e%ham0 bcast=fe80::ffff:ffff:ffff:ffff%ham0 netmask=ffff:ffff:ffff:ffff::
    added interface wlan0 ip=192.168.0.194 bcast=192.168.0.255 netmask=255.255.255.0
    added interface ham0 ip=25.12.189.46 bcast=25.255.255.255 netmask=255.0.0.0
    Enter ray's password:
    tdb(/var/run/samba/gencache.tdb): tdb_open_ex: could not open file /var/run/samba/gencache.tdb: Permission denied
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to host=192.168.0.199
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    name_resolve_bcast: Attempting broadcast lookup for name __MSBROWSE__<0x1>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to host=192.168.0.199
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    WORKGROUP
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to host=192.168.0.199
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    \\RAY2-PC
    Connecting to host=RAY2-PC
    resolve_lmhosts: Attempting lmhosts lookup for name RAY2-PC<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY2-PC<0x20>
    resolve_wins: Attempting wins lookup for name RAY2-PC<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY2-PC<0x20>
    resolve_hosts: getaddrinfo failed for name RAY2-PC [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name RAY2-PC<0x20>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    \\RAY-PC Desktop Windows 7 PC
    Connecting to host=RAY-PC
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-PC<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-PC<0x20>
    resolve_wins: Attempting wins lookup for name RAY-PC<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY-PC<0x20>
    resolve_hosts: getaddrinfo failed for name RAY-PC [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name RAY-PC<0x20>
    cli_start_connection: failed to connect to RAY-PC<20> (0.0.0.0). Error NT_STATUS_BAD_NETWORK_NAME
    \\RAY-HP
    Connecting to host=RAY-HP
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-HP<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-HP<0x20>
    resolve_wins: Attempting wins lookup for name RAY-HP<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY-HP<0x20>
    resolve_hosts: getaddrinfo failed for name RAY-HP [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name RAY-HP<0x20>
    cli_start_connection: failed to connect to RAY-HP<20> (0.0.0.0). Error NT_STATUS_BAD_NETWORK_NAME
    \\RAY-DESKTOP ray-desktop server (Samba, Ubuntu)
    Connecting to host=RAY-DESKTOP
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-DESKTOP<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-DESKTOP<0x20>
    resolve_wins: Attempting wins lookup for name RAY-DESKTOP<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY-DESKTOP<0x20>
    Connecting to 192.168.0.194 at port 445
    Connecting to 192.168.0.194 at port 139
    Error connecting to 192.168.0.194 (Connection refused)
    cli_start_connection: failed to connect to RAY-DESKTOP<20> (0.0.0.0). Error NT_STATUS_CONNECTION_REFUSED
    \\BRW0022581B28B8
    Connecting to host=BRW0022581B28B8
    resolve_lmhosts: Attempting lmhosts lookup for name BRW0022581B28B8<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name BRW0022581B28B8<0x20>
    resolve_wins: Attempting wins lookup for name BRW0022581B28B8<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name BRW0022581B28B8<0x20>
    resolve_hosts: getaddrinfo failed for name BRW0022581B28B8 [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name BRW0022581B28B8<0x20>
    Got a positive name query response from 192.168.0.190 ( 192.168.0.190 )
    Connecting to 192.168.0.190 at port 445
    Connecting to 192.168.0.190 at port 139
    Error connecting to 192.168.0.190 (Connection refused)
    cli_start_connection: failed to connect to BRW0022581B28B8<20> (0.0.0.0). Error NT_STATUS_CONNECTION_REFUSED

    BTW, the BRW...is my cellphone
    I just checked: all the computers on the Windows WORKGROUP network see each other and can access each other's files.
    I can kind of see that only the Ubuntu computer "ray-desktop" and the one Windows 7 computer "Ray2-PC" are seeing each other.
    Still, not even that one is able to see files in Ubuntu "ray-desktop." The Ubuntu machine can't see itself on the network even though its name shows up when you browse the network. But it can browse to all the Windows computers and access their shared files without any problem.

  5. #5
    Join Date
    May 2008
    Location
    SoCal
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    Quote Originally Posted by ray_silva View Post
    pgrep:
    Code:
    1602 nmbd
    19570 smbd
    This doesn't look right. There should be a minimum 2 smbd daemons running and 1 nmbd daemon running. Also the PID of 19570 is pretty high. It indicates to me that the daemon has been restarted many times. On my machine it looks like this
    Code:
    pgrep -l mbd
    887 smbd
    896 nmbd
    898 smbd
    smbtree:
    Code:
    lp_load_ex: refreshing parameters
    Initialising global parameters
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
    Processing section "[global]"
    WARNING: The "null passwords" option is deprecated
    added interface ham0 ip=2620:9b::190c:bd2e bcast=2620:9b::ffff:ffff netmask=ffff:ffff:ffff:ffff:ffff:ffff::
    added interface wlan0 ip=fe80::208:54ff:fe8d:99f%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
    added interface ham0 ip=fe80::7879:19ff:fe0c:bd2e%ham0 bcast=fe80::ffff:ffff:ffff:ffff%ham0 netmask=ffff:ffff:ffff:ffff::
    added interface wlan0 ip=192.168.0.194 bcast=192.168.0.255 netmask=255.255.255.0
    added interface ham0 ip=25.12.189.46 bcast=25.255.255.255 netmask=255.0.0.0
    Enter ray's password: 
    tdb(/var/run/samba/gencache.tdb): tdb_open_ex: could not open file /var/run/samba/gencache.tdb: Permission denied
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to host=192.168.0.199
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    name_resolve_bcast: Attempting broadcast lookup for name __MSBROWSE__<0x1>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to host=192.168.0.199
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    WORKGROUP
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to host=192.168.0.199
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    	\\RAY2-PC        		
    Connecting to host=RAY2-PC
    resolve_lmhosts: Attempting lmhosts lookup for name RAY2-PC<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY2-PC<0x20>
    resolve_wins: Attempting wins lookup for name RAY2-PC<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY2-PC<0x20>
    resolve_hosts: getaddrinfo failed for name RAY2-PC [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name RAY2-PC<0x20>
    Got a positive name query response from 192.168.0.199 ( 192.168.0.199 )
    Connecting to 192.168.0.199 at port 445
    Doing spnego session setup (blob length=58)
    got OID=1.3.6.1.4.1.311.2.2.30
    got OID=1.3.6.1.4.1.311.2.2.10
    got principal=<null>
    Got challenge flags:
    Got NTLMSSP neg_flags=0x628a8215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x60088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x60088215
    SPNEGO login failed: Logon failure
    	\\RAY-PC         		Desktop Windows 7 PC
    Connecting to host=RAY-PC
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-PC<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-PC<0x20>
    resolve_wins: Attempting wins lookup for name RAY-PC<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY-PC<0x20>
    resolve_hosts: getaddrinfo failed for name RAY-PC [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name RAY-PC<0x20>
    cli_start_connection: failed to connect to RAY-PC<20> (0.0.0.0). Error NT_STATUS_BAD_NETWORK_NAME
    	\\RAY-HP         		
    Connecting to host=RAY-HP
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-HP<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-HP<0x20>
    resolve_wins: Attempting wins lookup for name RAY-HP<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY-HP<0x20>
    resolve_hosts: getaddrinfo failed for name RAY-HP [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name RAY-HP<0x20>
    cli_start_connection: failed to connect to RAY-HP<20> (0.0.0.0). Error NT_STATUS_BAD_NETWORK_NAME
    	\\RAY-DESKTOP    		ray-desktop server (Samba, Ubuntu)
    Connecting to host=RAY-DESKTOP
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-DESKTOP<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name RAY-DESKTOP<0x20>
    resolve_wins: Attempting wins lookup for name RAY-DESKTOP<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name RAY-DESKTOP<0x20>
    Connecting to 192.168.0.194 at port 445
    Connecting to 192.168.0.194 at port 139
    Error connecting to 192.168.0.194 (Connection refused)
    cli_start_connection: failed to connect to RAY-DESKTOP<20> (0.0.0.0). Error NT_STATUS_CONNECTION_REFUSED
    	\\BRW0022581B28B8		
    Connecting to host=BRW0022581B28B8
    resolve_lmhosts: Attempting lmhosts lookup for name BRW0022581B28B8<0x20>
    resolve_lmhosts: Attempting lmhosts lookup for name BRW0022581B28B8<0x20>
    resolve_wins: Attempting wins lookup for name BRW0022581B28B8<0x20>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    resolve_hosts: Attempting host lookup for name BRW0022581B28B8<0x20>
    resolve_hosts: getaddrinfo failed for name BRW0022581B28B8 [Name or service not known]
    name_resolve_bcast: Attempting broadcast lookup for name BRW0022581B28B8<0x20>
    Got a positive name query response from 192.168.0.190 ( 192.168.0.190 )
    Connecting to 192.168.0.190 at port 445
    Connecting to 192.168.0.190 at port 139
    Error connecting to 192.168.0.190 (Connection refused)
    cli_start_connection: failed to connect to BRW0022581B28B8<20> (0.0.0.0). Error NT_STATUS_CONNECTION_REFUSED
    BTW, the BRW...is my cellphone
    I just checked: all the computers on the Windows WORKGROUP network see each other and can access each other's files.
    I can kind of see that only the Ubuntu computer "ray-desktop" and the one Windows 7 computer "Ray2-PC" are seeing each other.
    Still, not even that one is able to see files in Ubuntu "ray-desktop." The Ubuntu machine can't see itself on the network even though its name shows up when you browse the network. But it can browse to all the Windows computers and access their shared files without any problem.
    I almost missed your response at the bottom. You should put the data output between [code] blocks so it is legible and separated from your comments.. you can do that by clicking on the # icon at the top of the editor (advanced mode). Look for the red highlights in the above. These are login failures and one name not not known.

    In addition you have used a deprecated parameter (see the purple highlight) in configuring the smb,conf file. This must mean that you have modified the smb.conf [global] configuration section.

    Post the output of these commands; using the [code] blocks (#
    Code:
    sudo pdbedit -L
    
    getent passwd |grep 1000
    
    cat /etc/samba/smb.conf
    I'm looking to see if the Ubuntu user is also a Samba user. Every Samba user (including the guest user) must be in the Samba user database as well as being an Ubuntu user. It's best of the Windows user name is the same as the Ubuntu and Samba user name.

    The default smb.conf file should work perfectly. The only addition needed is the share definitions. So I want to see what you have modified.

    The output shows that not all the hostnames are recognized. Let's see the /etc/hosts file for the Ubuntu machine we are testing. We should stick with one and then g t the second Ubuntu machine later. Post the output of these
    Code:
    hostname
    
    cat /etc/hosts
    -BAB1

  6. #6
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    First, RE:
    This doesn't look right. There should be a minimum 2 smbd daemons running and 1 nmbd daemon running. Also the PID of 19570 is pretty high. It indicates to me that the daemon has been restarted many times. On my machine it looks like thisCode:
    pgrep -l mbd
    887 smbd
    896 nmbd
    898 smbd

    You're right, I did re-start it many times trying to get it to work. At no point did I have two smdb daemons running.

    I'll reply to each of your comments in individual "quick replies."

  7. #7
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    Second, RE:

    Look for the red highlights in the above. These are login failures and one name not not known.

    In addition you have used a deprecated parameter (see the purple highlight) in configuring the smb,conf file. This must mean that you have modified the smb.conf [global] configuration section.

    You're right. The red highlights must be for the other Windows computers on the network, but remember this - the Ubuntu machine running Samba is having no problem browsing the Windows server and accessing files from all the Windows networked computers. Recall also that I mentioned the BRW... attempted connect is my cell phone. I would not be surprised that Samba does not know or connect to it since it has a hotspot shiled VPN.

    About the purple highlighted "depracation;" yes, I did try to edit the config file, both from Webmin and directly. I did have problems because it was read-only and I figured a way to edit and replace the old one, but that must have caused the depracation error.

  8. #8
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    ray@ray-desktop:~$ sudo pdbedit -L
    [sudo] password for ray:

    WARNING: The "null passwords" option is deprecated
    No builtin backend found, trying to load plugin
    Error loading module '/usr/lib/samba/pdb/xxxxxxx.so': /usr/lib/samba/pdb/xxxxxxx.so: cannot open shared object file: No such file or directory
    No builtin nor plugin backend for xxxxxxx found
    PANIC (pid 5975): pdb_get_methods_reload: failed to get pdb methods for backend xxxxxxx


    BACKTRACE: 7 stack frames:
    #0 pdbedit(log_stack_trace+0x29) [0xb77081b9]
    #1 pdbedit(smb_panic+0x28) [0xb77082b8]
    #2 pdbedit(+0x5faa3) [0xb7692aa3]
    #3 pdbedit(initialize_password_db+0x23) [0xb7695913]
    #4 pdbedit(main+0x33f) [0xb7669c0f]
    #5 /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0xb7388905]
    #6 pdbedit(+0x390d5) [0xb766c0d5]
    smb_panic(): calling panic action [/usr/share/samba/panic-action 5975]
    smb_panic(): action returned status 0
    Can not dump core: corepath not set up
    Please install an MTA on this system if you want to use sendmail!

    COMMENT -- I changed the actual password in the results to xxxxxxx

  9. #9
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    ray@ray-desktop:~$ getent passwd |grep 1000
    ray:1000:1000:ray,,,:/home/ray:/bin/bash

  10. #10
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    56
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    ray@ray-desktop:~$ cat /etc/samba/smb.conf
    [global]
    panic action = /usr/share/samba/panic-action %d
    workgroup = WORKGROUP
    netbios name = silvanet
    invalid users = root
    security = user
    wins support = no
    log file = /var/log/samba.log
    log level = 3
    max log size = 1000
    syslog = 1
    encrypt passwords = true
    passdb backend = xxxxxxx
    socket options = TCP_NODELAY
    dns proxy = no
    passwd program = /usr/bin/passwd %u
    passwd chat =*Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
    obey pam restrictions = yes
    pam password change = no
    null passwords = no


    #Share Definitions


    [homes]
    comment = Home Directories
    browseable = yes
    writable = yes
    security mask = 0700
    create mask = 0700


    COMMENT - Again, I changed the actual password in the results above to xxxxxxx

Page 1 of 4 123 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •