On Sat, 2004-02-21 at 09:55, David Wuertele wrote: > When I use smbclient to access an IOMEGA NAS server, smbclient tries > to access port 445 for a full five minutes before timing out: > > [2004/02/20 17:48:24, 10] lib/gencache.c:gencache_get(262) > Returning valid cache entry: key = NBT/NAS_120_1#20, value = 192.168.123.161:0, > timeout = Fri Feb 20 17:53:22 2004 > > [2004/02/20 17:48:24, 5] libsmb/namecache.c:namecache_fetch(201) > name nas_120_1#20 found. > [2004/02/20 17:48:24, 3] lib/util_sock.c:open_socket_out(698) > Connecting to 192.168.123.161 at port 445 > [2004/02/20 17:51:38, 2] lib/util_sock.c:open_socket_out(733) > error connecting to 192.168.123.161:445 (Connection timed out) > > Next, smbclient goes on to contact it on port 139, and all works great > right away. > > Can I direct smbclient to not use 445? Anyone have an idea why > smbclient is getting stuck in this tar pit for five minutes?
We really expect hosts to do the sensible thing, and return connection refused in this case. We probably should do what MS does, which is to connect to both ports, then throw one connection away. It's not exactly nice however... Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
signature.asc
Description: This is a digitally signed message part
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
