Ports in close state
Urban Widmark
urban at teststation.com
Wed Mar 7 23:09:40 GMT 2001
On 7 Mar 2001, Howard Nugent wrote:
> The ports are still lingering in a closed status
> tcp 0 0 192.168.2.17:139 0.0.0.0:* LISTEN
> tcp 0 0 192.168.2.17:3534 192.168.2.20:139 CLOSE
> tcp 0 0 192.168.2.17:3535 192.168.2.20:139 CLOSE
> tcp 0 0 192.168.2.17:3536 192.168.2.20:139 CLOSE
> tcp 0 0 192.168.2.17:3537 192.168.2.20:139 CLOSE
> tcp 0 0 192.168.2.17:139 192.168.2.20:3827 ESTABLISHED
> tcp 0 0 192.168.2.17:3539 192.168.2.20:139 CLOSE
> tcp 0 0 192.168.2.17:3540 192.168.2.20:139 CLOSE
> tcp 0 0 192.168.2.17:3541 192.168.2.20:139 CLOSE
> tcp 0 0 192.168.2.17:3542 192.168.2.20:139 CLOSE
All of these in CLOSE are expected on an unpatched smbmount, but I was
pretty sure this was fixed by the patch. Are you sure you are not still
using the old smbmount binary?
The new smbmount should log things to /usr/local/samba/var/log.smbmount
(or similar, depending on how your logging is setup).
/Urban
More information about the samba
mailing list