search for: status_bad_network_name

...tried disabling Shorewall But that's about the only thing that works. Ethereal is showing errors such as: "NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED" and "Tree Connect AndX Request, Path :\\SERVER\DOWNLOADS" then "Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME". Im at my wits end. I've been fighting with this for 3 weeks and not making any progress. PLEASE, give me a push in the right direction. Brian

...n 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 ar...

...VS] section 3.1.6.8, to normalize the hostname by resolving server aliases and evaluating share scope. The server MUST use <normalized hostname, sharename> to look up the Share in ShareList. If no share with a matching share name and server name is found, the server MUST fail the request with STATUS_BAD_NETWORK_NAME. If a share is found, the server MUST do the following: If Share.Type includes STYPE_CLUSTER_FS, STYPE_CLUSTER_SOFS, or STYPE_CLUSTER_DFS and Connection.Dialect is greater than MaxClusterDialect and SMB2_TREE_CONNECT_FLAG_CLUSTER_RECONNECT is not set in Flags/Reserved field, the server MUST fail th...

...OFFICE\c.garling 100.397795864 192.168.15.6 -> 192.168.23.107 SMB2 142 Session Setup Response 100.397895000 192.168.23.107 -> 192.168.15.6 SMB2 198 Tree Connect Request Tree: \\office.example.com\technik 100.398866908 192.168.15.6 -> 192.168.23.107 SMB2 143 Tree Connect Response, Error: STATUS_BAD_NETWORK_NAME My client directly tries to connect to the share on 192.168.15.6, but this is the AD server that should forward to 192.168.15.17 which is the file server. I also traced the connection attempt with wireshark. In the request sent from my workstation I found this message in the flags: "This...

...95864 192.168.15.6 -> 192.168.23.107 SMB2 142 Session Setup > Response > 100.397895000 192.168.23.107 -> 192.168.15.6 SMB2 198 Tree Connect > Request Tree: \\office.example.com\technik > 100.398866908 192.168.15.6 -> 192.168.23.107 SMB2 143 Tree Connect > Response, Error: STATUS_BAD_NETWORK_NAME \\office.example.com doesn't look like a valid machine name. Do you have any idea how you might be getting from User 'OFFICE\c.garling' to a rather odd looking machine name (or did you just substitute that in?)...

...dX Response 0.564622 158.36.98.105 -> 158.36.146.4 SMB Tree Connect AndX Request, Path: \\PROF\PROFILE 0.564706 158.36.146.4 -> 158.36.98.105 TCP microsoft-ds > 1042 [ACK] Seq=960 Ack=1440 Win=9648 Len=0 0.576723 158.36.146.4 -> 158.36.98.105 SMB Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME