samba fails - port already in use problem
I just installed samba from the ports and set up the smb.conf file by, initially, setting only the workgroup name to match my home network. I then tried to start samba but it fails with these messages - -bash-2.05b$ tail log.smbd Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/11/30 00:55:24, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use [2002/11/30 01:28:16, 0] smbd/server.c:main(707) smbd version 2.2.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/11/30 01:28:16, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use What else could be using port 139? And how do I fix this? I tried a search of the lists on google but came up with no relevant answers. Thanks, Chip -- My smb.conf file -- [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4 workgroup = HOMENET # server string is the equivalent of the NT Description field server string = Chip # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Security mode. Most people will want user level security. See # security_level.txt for details. security = user # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY [homes] comment = Home Directories browseable = no writeable = yes [mp3s] comment = My MP3's directory path = /usr/mp3s read only = no public = yes To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: samba fails - port already in use problem
Hi Chip, How are you starting samba? You try to determine who's using port 139 by running: sockstat -4l netstat -at | grep -i list netstat -an | grep -i '139' Between the three commands, you should be able to track down who's got port 139 in the bag already. Saying this though, its often a problem with apps like samba, when you decide to start the daemons from inetd, but inadvertently run the start up scripts from /usr/local/etc/rc.d as well:-) Just something to verify in the mean time. Stacey PS: Is that *all* of your smb.conf? On Sat, 2002-11-30 at 09:46, chip wiegand wrote: I just installed samba from the ports and set up the smb.conf file by, initially, setting only the workgroup name to match my home network. I then tried to start samba but it fails with these messages - -bash-2.05b$ tail log.smbd Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/11/30 00:55:24, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use [2002/11/30 01:28:16, 0] smbd/server.c:main(707) smbd version 2.2.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/11/30 01:28:16, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use What else could be using port 139? And how do I fix this? I tried a search of the lists on google but came up with no relevant answers. Thanks, Chip -- My smb.conf file -- [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4 workgroup = HOMENET # server string is the equivalent of the NT Description field server string = Chip # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Security mode. Most people will want user level security. See # security_level.txt for details. security = user # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY [homes] comment = Home Directories browseable = no writeable = yes [mp3s] comment = My MP3's directory path = /usr/mp3s read only = no public = yes To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: samba fails - port already in use problem
With Samba 2.27 ( and earlier versions, the only samba-like line in /etc/inetd.conf that should be unciommented is: swatstream tcp nowait/400 root/usr/local/sbin/swatswat and that's only if you want to run the web administration tool. I tried the listed smb.conf, and the only change I made to it was a netbios name line: Samba config file created using SWAT # from mts-125.wallnet.com (208.225.162.57) # Date: 2002/11/30 17:24:20 # Global parameters [global] workgroup = HOMENET netbios name = CHIP server string = Chip log file = /var/log/log.%m max log size = 50 [homes] comment = Home Directories read only = No browseable = No [mp3s] comment = My MP3's directory path = /usr/mp3s read only = No guest ok = Yes With the netbios name defined, I was able to mount the mp3s share using mount_smbfs: mount_smbfs -W HOMENET -I 128.235.198.6 //timothyk@chip/mp3s /mp3 It all looks ok; I agree with Stacey, beware smbd and nmbd in inetd.conf Tim Kellers CPE/NJIT On Saturday 30 November 2002 05:21 pm, Stacey Roberts wrote: Hi Chip, How are you starting samba? You try to determine who's using port 139 by running: sockstat -4l netstat -at | grep -i list netstat -an | grep -i '139' Between the three commands, you should be able to track down who's got port 139 in the bag already. Saying this though, its often a problem with apps like samba, when you decide to start the daemons from inetd, but inadvertently run the start up scripts from /usr/local/etc/rc.d as well:-) Just something to verify in the mean time. Stacey PS: Is that *all* of your smb.conf? On Sat, 2002-11-30 at 09:46, chip wiegand wrote: I just installed samba from the ports and set up the smb.conf file by, initially, setting only the workgroup name to match my home network. I then tried to start samba but it fails with these messages - -bash-2.05b$ tail log.smbd Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/11/30 00:55:24, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use [2002/11/30 01:28:16, 0] smbd/server.c:main(707) smbd version 2.2.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2002 [2002/11/30 01:28:16, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use What else could be using port 139? And how do I fix this? I tried a search of the lists on google but came up with no relevant answers. Thanks, Chip -- My smb.conf file -- [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4 workgroup = HOMENET # server string is the equivalent of the NT Description field server string = Chip # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Security mode. Most people will want user level security. See # security_level.txt for details. security = user # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY [homes] comment = Home Directories browseable = no writeable = yes [mp3s] comment = My MP3's directory path = /usr/mp3s read only = no public = yes To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
