Samba always take Apache tcp port !
Robert Dahlem
Robert.Dahlem at gmx.net
Tue Oct 3 22:31:10 GMT 2000
Vladimir,
On Tue, 03 Oct 2000 16:23:12 +0200, Vladimir Vyskocil wrote:
>Why almost always samba bind to tcp port left by apache (httpd)
>after apache shutdown ie I start httpd then smbd & nmbd, then I stop
>httpd and when I want to relaunch httpd it doesn't work because smbd
>has bound requiered port ! Here is a dump of netstat -nap when smbd
>has takeover needed port for httpd (2004 is a HTTP SSL port) :
First: 2003 (guess you mean this one instead of 2004) is really a bad
choice for any server to listen on a busy machine, it will almost
always collide with dynamically assigned ports. Try ports below 1024
for your servers.
If I shorten your netstat output a little, I get the following:
- ESTABLISHED 21953/smbd
127.0.0.1:1393 127.0.0.1:389
Ok, that's Samba connecting to your LDAP server.
- LISTEN 21953/smbd
0.0.0.0:139 0.0.0.0:*
0.0.0.0:80 0.0.0.0:*
0.0.0.0:443 0.0.0.0:*
172.20.50.1:2003 0.0.0.0:*
Well, that's really a funny process: your smbd seems to listen for
NETBIOS sessions (139, that's ok) as well as for HTTP (80) and HTTPS
(443). How come? I never saw this on any of my machines.
Which OS/version are you running?
Which Samba version?
Which parameters did you give to ./configure?
Can you post your smb.conf? Your startup parameters?
Do you have lsof for your architecture? Can you do an 'lsof -p xxx'
with xxx being smbd' PID?
I have a feeling your OS messes some things up. :-)
Regards,
Robert
--
---------------------------------------------------------------
Robert.Dahlem at gmx.net Fax +49-69-432647
---------------------------------------------------------------
Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email
software; far better than Outlook. Try it sometime.
More information about the samba
mailing list