samba - Oct 2003 - upgraded from Samba 2.2.8a to Samba 3.0.0 now mount smbf does not work? update

I have upgraded from a almost perfectly working Samba 2.2.8a to Samba 3.0.0, I
wished to
join my NAS servers to the 
domain and it seemed something to do with DNS authentication was stopping them
from joining,
so I upgraded to Samba 3 
(not beta)

I have searched the web for reasons for this stange behavior but could find no
explaination
or fix, there are however 
other people having the same problem.

I have two questions:

1) my smbfs commands in /etc/rc.local now hangs the consol when I reboot,
needles to say
this did work before.... 
sometimes one or two or my smbfs commands will work without reason, I had to
comment out the
smbfs commands so I could 
test the reason for this behavior.

When I set log level = 3 ig get the following output when I run :

[root@cf root]# mount -t smbfs -o username=xxxxx,password=xxxxx //cores/users
/mnt/nas/users
opts: rw
opts: username=xxxxx
opts: password=xxxxx
mount.smbfs started (version 3.0.0)
added interface ip=10.0.0.100 bcast=10.0.0.255 nmask=255.255.255.0
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
resolve_lmhosts: Attempting lmhosts lookup for name core<0x20>
resolve_wins: Attempting wins lookup for name core<0x20>
resolve_wins: using WINS server 127.0.0.1 and tag '*'
Got a positive name query response from 127.0.0.1 ( 10.0.0.3 )
Connecting to 10.0.0.3 at port 445

Unless I press CTRL C the console will just hang their on ?Connecting to
10.0.0.3 at port
445?

There are no errors in the /log/var/messages log that seem to suggest an error
of any kind.

-----start
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

# mount -t smbfs -o username=xxxxx,password=xxxxx //cores/users /mnt/nas/users
# mount -t smbfs -o username=xxxxx,password=xxxxx //cores/backup /mnt/nas/backup
# mount -t smbfs -o username=xxxxx,password=xxxxx //cores/logon /mnt/nas/logon
# mount -t smbfs -o username=xxxxx,password=xxxxx //cores/source /mnt/nas/source
# mount -t smbfs -o username=xxxxx,password=xxxxx //cores/quickbooks
/mnt/nas/quickbooks

/root/firewall.sh
end-----

Does anyone know why this is happening and what to do about it


2) I wish to start using NFS mounts much the same way I was using smbfs mounts.

mount -t nfs 10.0.0.99:/backup /mnt/nas/backup

My problem is I seem not to be able to mount a NFS with a username and password,
how can I
mount a remote volume with a 
specific username and password.

Thanks for any help anyone can give
..

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