[Samba] upgraded from Samba 2.2.8a to Samba 3.0.0 now mount smbf does not work? update

[Peter Atkin]

Ok Think found the problem, 

Samba 3.0.0 seems to use port 445 by default, which is a bit odd, as it should be using port 139 for compatibility., it 
will switch to port 139 after about 3mins, I have 5 smbfs mount points so I have to wait at least 15mins for the server 
to be ready from boot up, (makes windows look very fast)

Does anyone know how to either reduce the timeout time or tell smbfs to use port 139?

Kind Regards

Peter

Please find below excerpts from:
http://www.thekore.co.uk/inv/index.php?s=d2d462f5162672cf00a1450fa6b52076&showtopic=158&st=0&#entry441

If you're feeling daring, you can try running Samba via port 445/tcp
only using a method called "Direct-Hosted". Note that this method is
not as widely tested (or supported) as running a traditional install
of Samba. Note that only Windows 2000/XP/2003 support this method of
connecting to Samba, so if you have other clients this option is not
one that you should use. Modify your /etc/inetd.conf file to include:

* NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows
the continued use of NetBIOS traffic proxied over TCP/IP. As a
result, NetBIOS names are made to IP addresses and NetBIOS name
types are conceptually equivalent to TCP/IP ports. This is how
file and printer sharing are accomplished in Windows 95/98/ME.
They traditionally rely on three ports: NetBIOS Name Service
(nbname) via UDP port 137, NetBIOS Datagram Service (nbdatagram)
via UDP port 138, and NetBIOS Session Service (nbsession) via TCP
port 139. All name resolution is done via WINS, NetBIOS
broadcasts, and DNS. NetBIOS over TCP is documented in RFC 1001