Xu, Qiang (FXSGSC)
2010-Apr-01 08:17 UTC
[Samba] Failure to transfer files to Win2008 Server Clusters
Hi, list: Our printers are using samba-3.0.37, and we hit a problem recently when doing file transfer to Windows 2008 Server Clusters. The error occurs when the printer attempts to locate the file path and uses the server IP address rather than the hostname: =====================================================18 21.335677 13.121.8.162 13.121.8.3 SMB Session Setup AndX Request, NTLMSSP_NEGOTIATE 19 21.337175 13.121.8.3 13.121.8.162 SMB Session Setup AndX Response, NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED 20 21.349010 13.121.8.162 13.121.8.3 SMB Session Setup AndX Request, NTLMSSP_AUTH, User: rasta-man\earl 21 21.354123 13.121.8.3 13.121.8.162 SMB Session Setup AndX Response 22 21.360548 13.121.8.162 13.121.8.3 SMB Tree Connect AndX Request, Path: \\13.121.8.3\SCANFOLDER 23 21.361288 13.121.8.3 13.121.8.162 SMB Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME =====================================================I believe the problem is related to how Microsoft scopes the file shares when using a cluster configuration. The transfer is smooth when the destination is a stand-alone Win2008 server. Still, from the client side, is there any way to walk around the problem? I mean, since the problem doesn't occure when the hostname is used to locate the file path, where in the code can I disable the resolving of the server's hostname to ip address in samba client? Looking forward to help, Xu Qiang
Volker Lendecke
2010-Apr-01 09:11 UTC
[Samba] Failure to transfer files to Win2008 Server Clusters
On Thu, Apr 01, 2010 at 04:17:42PM +0800, Xu, Qiang (FXSGSC) wrote:> Our printers are using samba-3.0.37, and we hit a problem > recently when doing file transfer to Windows 2008 Server > Clusters. > > The error occurs when the printer attempts to locate the > file path and uses the server IP address rather than the > hostname: > =====================================================> 18 21.335677 13.121.8.162 13.121.8.3 SMB Session Setup AndX Request, NTLMSSP_NEGOTIATE > 19 21.337175 13.121.8.3 13.121.8.162 SMB Session Setup AndX Response, NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED > 20 21.349010 13.121.8.162 13.121.8.3 SMB Session Setup AndX Request, NTLMSSP_AUTH, User: rasta-man\earl > 21 21.354123 13.121.8.3 13.121.8.162 SMB Session Setup AndX Response > 22 21.360548 13.121.8.162 13.121.8.3 SMB Tree Connect AndX Request, Path: \\13.121.8.3\SCANFOLDER > 23 21.361288 13.121.8.3 13.121.8.162 SMB Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME > =====================================================Probably there's not much you can do about this. You probably have to use the file server name in the //server/share piece of the smbclient (are you using that?) command line. What you can do if you have problems with your name resolution is to use the -I switch to smbclient to give it the server's ip address. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20100401/fbea3088/attachment.pgp>