Hi
I have just installed Debian 6.0.1 base install, for the use of a file server.
I installed samba using apt-get and am using: smbd version 3.5.6
Here is my smb.conf file. Very basic, which by the way, seems OK according to the output of testparm.
Code:
[global]
log level = 3
workgroup = INERT
wins support = yes
[test]
comment = Testing Only
path = /export/tmp
read only = No
First of all, I connect to the samba server locally, using:
smbclient -L localhost -N
Code:
Anonymous login successful
Domain=[INERT] OS=[Unix] Server=[Samba 3.5.6]
Sharename Type Comment
--------- ---- -------
test Disk Testing Only
IPC$ IPC IPC Service (Samba 3.5.6)
Anonymous login successful
Domain=[INERT] OS=[Unix] Server=[Samba 3.5.6]
Server Comment
--------- -------
ARGON
XENON Samba 3.5.6
Workgroup Master
--------- -------
INERT XENON
Server ARGON, by the way is the name of an XP machine. I can't see anything in 'My Network Places', but if I type the IP address of the samba box into explorer on the XP machine, then I can view the share, 'test', however I can't access it despite the permissions on the samba server for /export and /export/tmp being set to 777.
Then, I add an account using smbpasswd (and one that's already present in /etc/passwd). And try and log into the server using this account.
smbclient //localhost/test -U ross
Code:
Enter ross's password:
Domain=[INERT] OS=[Unix] Server=[Samba 3.5.6]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Before I even attempt to log in however, I examined the output of the smdb login files.
This is the result of the log file from /var/log/samba/smbd.conf
Code:
lib/util_sock.c:880(open_socket_in)
bind failed on port 445 socket_addr = 0.0.0.0.
Error = Address already in use
[2011/06/15 22:19:51.969638, 0]
smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
lib/util_sock.c:880(open_socket_in)
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already in use
Output from netstat -an | egrep "
13|445)" :
Code:
tcp6 0 0 :::445 :::* LISTEN
tcp6 0 0 :::139 :::* LISTEN
udp 0 0 192.168.2.255:137 0.0.0.0:*
udp 0 0 192.168.2.4:137 0.0.0.0:*
udp 0 0 0.0.0.0:137 0.0.0.0:*
udp 0 0 192.168.2.255:138 0.0.0.0:*
udp 0 0 192.168.2.4:138 0.0.0.0:*
udp 0 0 0.0.0.0:138 0.0.0.0:*
And output from lsof -i | grep .mbd:
Code:
smbd 4886 root 25u IPv6 18313 0t0 TCP *:microsoft-ds (LISTEN)
smbd 4886 root 26u IPv6 18315 0t0 TCP *:netbios-ssn (LISTEN)
nmbd 4889 root 12u IPv4 18332 0t0 UDP *:netbios-ns
nmbd 4889 root 13u IPv4 18333 0t0 UDP *:netbios-dgm
nmbd 4889 root 14u IPv4 18339 0t0 UDP 192.168.2.4:netbios-ns
nmbd 4889 root 15u IPv4 18340 0t0 UDP 192.168.2.255:netbios-ns
nmbd 4889 root 16u IPv4 18341 0t0 UDP 192.168.2.4:netbios-dgm
nmbd 4889 root 17u IPv4 18342 0t0 UDP 192.168.2.255:netbios-dgm
I don't understand why smbd is not reportedly binding to IPv4 ports.
As you can see this threat is somewhat long, so thanks for taking the time to look through it and I hope that I haven't caused anyone to spend their time looking through it by doing something really silly!
