The Specified Network Name is No Longer Available - Large File Copies
Right in the middle of a SMB copy the connection gets reset and the file starts from the begining or the copy crashes with "The Pecified Network Name is No longer Available" 3088 0.421409 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 It does not appear to matter weather the destination is NETAPP Windows 2008 or R2 and the client can be Win7, W2K8R2,W2K8,XP the copy will fail. so SMB1 & SMB2 both fail An interesting side note is that if we test between a Windows 7 client as the source and a Linux SAMBA share we do not experiance the issue. The network is configured as follows Office Network Datacenter These are connected via a 1Gbps link Local copies inside the Datacenter are OK Local copies inside the Office network are OK The failure occurs when copying from the Office to the Datacentre Their are no errors on the 1Gbps link and latency is <1ms Nic's port speed and duplex settings have all been checked for mismatch. Copying from the datacentre to the Office are successful For no apparent reason the server sends a connection reset packet right in the middle of the copy killing the client and the copy, the copy either restarts from the begining or dies with "The Specified Network Name is No Longer Available" We also believe it is also affecting smaller file copies as we get the same error intermitantly with Offline Files Syncronisation. No. Time Source Destination Protocol Length Info 3080 0.417576 10.193.114.102 10.160.1.40 TCP 35094 [TCP segment of a reassembled PDU] 3081 0.417924 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [ACK] Seq=29317 Ack=19977665 Win=3610 Len=0 3082 0.417950 10.193.114.102 10.160.1.40 TCP 8814 [TCP segment of a reassembled PDU] 3083 0.420270 10.160.1.40 10.193.114.102 SMB2 138 Write Response 3084 0.420417 10.193.114.102 10.160.1.40 TCP 62834 [TCP segment of a reassembled PDU] 3085 0.420508 10.193.114.102 10.160.1.40 TCP 62834 [TCP segment of a reassembled PDU] 3086 0.420590 10.193.114.102 10.160.1.40 TCP 62834 [TCP segment of a reassembled PDU] 3087 0.420668 10.193.114.102 10.160.1.40 TCP 52614 [TCP segment of a reassembled PDU] 3088 0.421409 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3089 0.421411 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3090 0.421413 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3091 0.421415 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3092 0.421416 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3093 0.421418 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3094 0.421420 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3095 0.421421 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3096 0.421423 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3097 0.421425 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3098 0.421426 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3099 0.421428 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3100 0.421430 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3101 0.421431 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3102 0.421432 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3103 0.421434 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3104 0.421436 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3105 0.421437 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3106 0.421439 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3107 0.421441 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3108 0.421442 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3109 0.421830 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3110 0.421831 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3111 0.421833 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3112 0.421835 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3113 0.421837 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3114 0.421839 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3115 0.421841 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3116 0.421843 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3117 0.421845 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3118 0.421847 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3119 0.421848 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3120 0.421850 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3121 0.421852 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3122 0.421854 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3123 0.421856 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3124 0.421857 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3125 0.421859 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3126 0.421861 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3127 0.421862 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3128 0.421864 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3129 0.421865 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3130 0.421867 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3131 0.421869 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3132 0.421870 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3133 0.421872 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3134 0.421874 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3135 0.421876 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3136 0.421877 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3137 0.421879 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3138 0.423935 10.193.114.102 10.193.114.20 DNS 85 Standard query A 3139 0.425212 10.193.114.20 10.193.114.102 DNS 101 Standard query response A 10.160.1.40 3140 0.426266 10.193.114.102 10.160.1.40 TCP 66 50139 > microsoft-ds [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1 3141 0.428378 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3142 0.428380 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3143 0.428381 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3144 0.428383 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3145 0.428385 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3146 0.428386 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3147 0.428388 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50133 [RST] Seq=29401 Win=0 Len=0 3148 0.428791 10.160.1.40 10.193.114.102 TCP 66 microsoft-ds > 50139 [SYN, ACK] Seq=0 Ack=1 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1 3149 0.428855 10.193.114.102 10.160.1.40 TCP 54 50139 > microsoft-ds [ACK] Seq=1 Ack=1 Win=65536 Len=0 3150 0.428967 10.193.114.102 10.160.1.40 SMB2 162 NegotiateProtocol Request 3151 0.430243 10.160.1.40 10.193.114.102 SMB2 294 NegotiateProtocol Response 3152 0.430912 10.193.114.102 10.160.1.40 SMB2 2707 SessionSetup Request 3153 0.431794 10.160.1.40 10.193.114.102 TCP 60 microsoft-ds > 50139 [ACK] Seq=241 Ack=2762 Win=65536 Len=0 3154 0.433883 10.160.1.40 10.193.114.102 SMB2 315 SessionSetup Response 3155 0.434954 10.193.114.102 10.160.1.40 SMB2 158 TreeConnect Request Tree: \\hollywood\d$ 3156 0.435822 10.160.1.40 10.193.114.102 SMB2 138 TreeConnect Response 3157 0.435879 10.193.114.102 10.160.1.40 SMB2 274 Create Request File: WIN7-ENT-SP1-x64-V1.7.wim 3158 0.436738 10.160.1.40 10.193.114.102 SMB2 242 Create Response File: WIN7-ENT-SP1-x64-V1.7.wim It appears to be an issue when the copy goes from the Router to the Switched side of the network at the Datacentre but doing the same copy with a SAMBA target works without error, so looks to be a possible SMB protocol issue. We are possible experianceing a variation on http://www.nynaeve.net/?p=93 but we are not using any NAT devices in the copy path.
August 17th, 2011 8:00pm

RedSt0rm - did you ever get this figured out? I am seeing the same behavior with Offline Caching on Windows 7 Pro with a SBS 2008 box. It starts the sync and then errors out with a "the specified network name is no longer available" message. I have removed my AV thinking that might be doing it - no love. It seems to sync a couple files then quits. Any help is appreciated. Thanks, ben
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2011 5:48pm

Hi Ben We finally got to the bottom of it, we had a WanScaler accellerating traffic for some clients, it turns out it was getting overwhelmed with the amound off data causing the copies to fail. in theory it should not have been interfearing but as soon as we disabled it and ran a test 5x the copies worked, re enabled the WanScaler and they started to fail again... We have now removed the WanScaler from the affected networks. FYI.
September 26th, 2011 11:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics