I am setting up SAMBA on a RedHat 6.2 Linux box for a friend (it is actually running under VMWARE).
I can not get the SMBD to stay running. It starts, creates a PID file in /var/lock/samba, but then exits saying that a port is already in use. I have added entries to /etc/inetd.conf already. It also doesn't start automatically.
any clue? This should be a fairly vanilla install. I had originally setup the computer to run on DHCP, but have changed it to static. I wanted to get this system to my buddy by Tuesday, but I can wait til Wednesday or so.
--------------------------
Here is my inetd.conf settings:
# SAMBA NetBIOS services (for PC file and print sharing)
netbios-ssn stream tcp nowait root /usr/sbin/smbd smbd
netbios-ns dgram udp wait root /usr/sbin/nmbd nmbd
--------------------------
Here is the error I get with level 3 debugging on smbd:
[2000/12/24 15:10:25, 3] param/loadparm.c:lp_add_ip
adding IPC service
[2000/12/24 15:10:25, 2] lib/interface.c:add_interf
added interface ip=192.168.10.2 bcast=192.168.10.255 nmask=255.255.255.0
[2000/12/24 15:10:25, 1] smbd/files.c:file_init(216
file_init: Information only: requested 10000 open files, 1014 are available.
[2000/12/24 15:10:25, 3] smbd/server.c:main(699)
loaded services
[2000/12/24 15:10:25, 3] smbd/server.c:main(707)
Becoming a daemon.
[2000/12/24 15:10:25, 3] locking/shmem_sysv.c:sysv_
Initialised IPC area of size 1048576
[2000/12/24 15:10:25, 0] lib/util_sock.c:open_socke
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
[2000/12/24 15:10:25, 2] smbd/server.c:exit_server(
Closing connections
[2000/12/24 15:10:25, 3] smbd/server.c:exit_server(
Server exit (caught signal)
[2000/12/24 15:11:31, 1] smbd/server.c:main(643)
smbd version 2.0.6 started.
Copyright Andrew Tridgell 1992-1998
[2000/12/24 15:11:31, 1] smbd/files.c:file_init(216
file_init: Information only: requested 10000 open files, 1014 are available.
thanks for any help!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Oops, hit submit too soon. If you have inetd configured to auto-start Samba, then you can't start it from a command line as inetd will own the ports that Samba needs. You can have Samba operate either way (most folks just run it as a daemon from the rc.* scripts), but not both. It is a bit easier to set up and debug when it is running as a daemon because you control when the daemon starts and gets restarted.
since Samba/Linux is running as a guest on a Windows system, it's obvious why you can't get it to work. When Windows is running, NetBios (port 139) will always be taken. It doesn't matter if the guest os (linux) has a different IP, the port is already taken by Windows.
If you must use it this way, try disabling file sharing and other WINS related services. But then again, you won't be able to browse NetBios/SMB-based resources and other application errors will arise.
I thought of 139 being taken by windows, but I'm not sure if that would be the case with VMware. The networking stacks should actually be separate and the guest OS shouldn't know what ports the master OS is using. Granted, there might be something special about port 139 as far as VMware is concerned, but if VMware doesn't keep the networking segregated there'd be a lot of other problems with a guest OS (you certainly wouldn't be able to run Linux as a Master and some othe Unixen as a guest... which does work).
I would use nmap(www.insecure.org) to scan the client, to see what ports are being used and by what.
Good luck
mfarace:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
No comment has been added lately, so it's time to clean up this TA.
I will leave the following recommendation for this question in the Cleanup topic area:
Split: matt023 {http:#45590} & jlevie {http:#46021}
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
paullamhkg
EE Cleanup Volunteer
Business Accounts
Answer for Membership
by: jleviePosted on 2000-12-24 at 21:11:49ID: 45503
Are you saying that Linux is running as a "guest OS" under VMware? I know that one can run Samba under Linux running as the master OS and have windows running as a VMware "guest OS" be able to access the SMB services. I'm not so sure that you'd be able to do so the other way around.
On the chance that it is possible to have Samba work when Linux is running as a "guest OS", it would seem that something has the SMB ports open. This would most likely be another copy of Samba already running and you should see the smbd & nmbd tasks in a "ps -ef" list. Also you could use lsof to see what task "owns" ports 137 & 139.