Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
Have installed Samba on two linux machines A and B. When I access linux machine A from windows using the samba username/password that I created it connects OK. Now if ...
  1. #1
    Just Joined!
    Join Date
    Feb 2008
    Posts
    19

    Cannot access linux from windows


    Have installed Samba on two linux machines A and B.
    When I access linux machine A from windows using the samba username/password that I created it connects OK. Now if I access the same linux machine from a second windows pc it connects without a challenge!
    However when I try to access linux machine B from windows using the samba username/password that I thought I had created when I installed Samba on B it fails authentication.
    I can see windows machines from the linux machines and access the shares on them without being password challenged.
    Can somebody explain why I cannot access machine B from windows?

  2. #2
    Just Joined!
    Join Date
    Feb 2008
    Posts
    29
    Logs. Check the logs.
    /var/log/samba/<machineIP.log> or <samba/directory>/log/<machineIP.log>

    Have you added the user on the second machine to authenticate.
    Firewall on 2nd PC?

  3. #3
    Just Joined!
    Join Date
    Feb 2008
    Posts
    19

    How do I add a user that is accessible from Windows

    How do I add a user whose logon credentials will be accepted by windows?

    David

  4. #4
    Just Joined!
    Join Date
    Feb 2008
    Posts
    29
    smbpasswd -a <user>
    This adds the user to samba database for authentication.

    You should be able to login now from windows.

  5. #5
    Just Joined!
    Join Date
    Feb 2008
    Posts
    19

    Still cannot connect to linux box

    Hi,

    I have added samba user and tried to log on to my linux box with the credentials I specified. The following shows the samba log from the linux box at the time I try to connect to it.

    [2008/03/07 22:06:34, 0] lib/util_sock.c:write_data(562)
    write_data: write failure in writing to client 192.168.1.12. Error Connection reset by peer
    [2008/03/07 22:06:34, 0] lib/util_sock.c:send_smb(769)
    Error writing 4 bytes to client. -1. (Connection reset by peer)
    [2008/03/07 22:06:43, 0] lib/util_sock.c:write_data(562)
    write_data: write failure in writing to client 192.168.1.12. Error Connection reset by peer
    [2008/03/07 22:06:43, 0] lib/util_sock.c:send_smb(769)
    Error writing 4 bytes to client. -1. (Connection reset by peer)

    Still no go.


  6. #6
    Just Joined!
    Join Date
    Feb 2008
    Posts
    29
    Ok.

    Lets try to connect from the Linux box itself.

    smbclient -NL //smbserver/<sharename> -U <username>

    This asks for the samba passwd. Enter it and see if you are able to see the samba prompt,

    smb:>

  7. #7
    Just Joined!
    Join Date
    Feb 2008
    Posts
    19

    Connection refused

    david@Athlon:/etc/samba$ smbclient -NL //Athlon/share -U david
    Error connecting to 127.0.1.1 (Connection refused)
    Connection to Athlon failed (Error NT_STATUS_CONNECTION_REFUSED)


  8. #8
    Just Joined!
    Join Date
    Feb 2008
    Posts
    29
    why is your localhost 127.0.1.1?
    The error is localized to the samba server itself.

    service smb restart (or /etc/init.d/smb stop and then start
    telnet localhost 445 (that's the port samba uses by default)

    Regards,
    Lego

  9. #9
    Just Joined!
    Join Date
    Feb 2008
    Posts
    19

    The plot thickens

    What is supposed to happen when I do the telnet?
    Yes, I don't know why the IP comes back as 127.0.1.1



  10. #10
    Just Joined!
    Join Date
    Feb 2008
    Posts
    29
    If it gives connection refused then a firewall is probably blocking the port.

Page 1 of 2 1 2 LastLast

Posting Permissions

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