On Fri, Jun 05, 2009 at 05:40:20PM -0400, Matt Burkhardt wrote: > Okay - I've been plugging away and it got to the point that running > smbclient was returning information about an Alfresco install that I > never used, so I went ahead and deleted everything I could find on my > machine that said "alfresco". I then removed samba using apt-get from > the machine by typing > > apt-get remove --purge samba > > I deleted the /etc/samba directory and re-installed samba. > > So now I've made sure that DHCP, DNS and OpenLDAP are now working > correctly and I started to reconfigure Samba. I start it up and I look > at the log.smbd and log.nmbd files, don't see a single error message and > when I run nmap - there's nothing listening on the ports that Samba is > supposed to be using. I have no firewall set up and nothing between me > and the server. Here's showing that the daemons are running: > > ps -e | grep mb > 6984 ? 00:00:00 nmbd > 6986 ? 00:00:00 smbd > > Here's the results from nmap > > nmap ubuntu > > Starting Nmap 4.53 ( http://insecure.org ) at 2009-06-05 17:34 EDT > Interesting ports on 192.168.1.100: > Not shown: 1697 closed ports > PORT STATE SERVICE > 22/tcp open ssh > 53/tcp open domain > 80/tcp open http > 81/tcp open hosts2-ns > 82/tcp open xfer > 83/tcp open mit-ml-dev > 111/tcp open rpcbind > 389/tcp open ldap > 443/tcp open https > 631/tcp open ipp > 901/tcp open samba-swat > 3306/tcp open mysql > 5001/tcp open commplex-link > 5432/tcp open postgres > 8009/tcp open ajp13 > 8080/tcp open http-proxy > 10000/tcp open snet-sensor-mgmt
This ports list shows smbd is not binding to the external ports. smbd uses TCP 139 & 445. nmbd uses udp 137 and 138. Jeremy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba