Hello,
ive been working on a problem with samba taking too long to mount a share from a Win2k machine. Im currently running RedHat ES4.0 with the following packages:
samba-common-3.0.10-1.4E.2
samba-client-3.0.10-1.4E.2

I actually have 2 linux systems that ive been using for testing. The other is ES3.0 with the following samba packages:
samba-client-3.0.6-2.3E
redhat-config-samba-1.0.16-2
samba-3.0.6-2.3E
samba-common-3.0.6-2.3E
samba-swat-3.0.6-2.3E

Both linux machines are in my DMZ area while the Win2K is in my internal area. Both linux machines are setup identically as far as the autofs automounting the samba shares.

Now the problem: The ES30 box will automount within seconds while the ES40 box takes upwards of a minute. When the mount is complete, then access is fast. This becomes a problem because the mountpoint is accessable via a webpage and i know that people hate staring at their browser for 60 seconds waiting for it to display.

Here's what i know: both boxes can ping the win2K machine and see its ports (445). There are no apparent error messages for the mount in the /var/log/messages log. Here is an nmap from the ES40 box:

[root@webconference /]# nmap search1

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2006-09-07 15:42 CDT
Interesting ports on search1 (192.168.20.111):
(The 1651 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
21/tcp open ftp
80/tcp open http
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
3389/tcp open ms-term-serv
6101/tcp open VeritasBackupExec
6106/tcp open isdninfo
10000/tcp open snet-sensor-mgmt
MAC Address: 00:02:B3:B9:79:90 (Intel)

Nmap run completed -- 1 IP address (1 host up) scanned in 1.758 seconds

Does anyone have any idea's why the mount would take so much longer on 1 machine than another? Any suggestions on things i can try? Im out of ideas to try and im not terribly familiar with samba.

Thanks
--Brett