samba - Sep 2002 - Interesting tidbit...

Greetings...

Our current production server is running 2.0.7 (we are getting ready to 
deploy 2.2.5 shortly)... and I experienced this interesting problem..

In Apache, if I had it listening to ports 444 and 445 for SSL, Samba would 
suddenly stop working on that machine. I killed Apache, and suddenly 
everyone could get to Samba again.. I started it, and everyone would get 
errors saying the machine was not available. So changed the ports to 8001 
and 8002 and *puf* everything's working again...

Just thought it would make for an interesting "Gee.. how odd" chuckle
for
the day.. :)

Glenn

---
Glenn E. Sieb
System Administrator
Lumeta Corporation
+1 732 357-3514 (V)
+1 732 564-0731 (Fax)

> In Apache, if I had it listening to ports 444 and 445 for SSL,
> Samba would
> suddenly stop working on that machine. I killed Apache, and suddenly
> everyone could get to Samba again.. I started it, and everyone would get
> errors saying the machine was not available. So changed the ports to 8001
> and 8002 and *puf* everything's working again...
Port 445 is reserved for "Naked (NetBios-less) SMB". Samba will be
listening
on that port as well. You can't have 2 servers listening on the same port !!

Andy