Raw SMB Requests Across Router Results in Session TerminationLast reviewed: March 18, 1997Article ID: Q127023 |
The information in this article applies to:
SYMPTOMSRaw SMB requests initiated by network activities (such as backing up a server), may result in an abnormal session termination when the SMB request is sent across a router. In the case of a network backup, the backup would be aborted and the following error would be logged:
WARNING: "\BACKUP\HRS014C$.DAT" is a corrupt file. This file cannot be verified. The network disk drive has stopped responding. Backup set aborted. CAUSEThe abnormal session termination occurs when a packet exceeding the Maximum MTU size is sent to the router port.
When a router receives a packet that exceeds the Maximum MTU size on aport, it is the routers responsibility to either:
Abnormal Termination Request From The Clients Side Of The RouterAfter the first Read Block Raw, the server never responds with the data, so the client's timer pops after 70 seconds and it requests that the connection be closed by setting the FIN bit in the IP packet.
Time Src Dst Protocol Description ======================================== 0.012 COLA11 HRS014 SMB C NT create & X, File = \BACKUP\HRS014C$.DAT 0.004 HRS014 COLA11 SMB R NT create & X, FID = 0x2002 0.006 COLA11 HRS014 SMB C transact2 GetFsInfo 0.002 HRS014 COLA11 SMB R transact2 0.004 COLA11 HRS014 SMB C transact2 GetFileInfo, FID = 0x2002 0.003 HRS014 COLA11 SMB R transact2 0.003 COLA11 HRS014 SMB C transact2 GetFileInfo, FID = 0x2002 0.004 HRS014 COLA11 SMB R transact2 0.009 COLA11 HRS014 SMB C NT transact - Query Security Description 0.004 HRS014 COLA11 SMB R NT transact 0.011 COLA11 HRS014 SMB C read block raw, FID = 0x2002, Read 0x7000 at 0x0 0.252 COLA11 HRS014 SMB C read block raw, FID = 0x2002, Read 0x7000 at 0x0 0.003 HRS014 COLA11 TCP .A.... 71.12 COLA11 HRS014 TCP .A...F 0.002 HRS014 COLA11 TCP ...R.. Abnormal Termination Request From The Servers Side Of The RouterAfter the first Read Block Raw, the server responds with the data in a packet larger than the routers Maximum MTU size for that port. The router never responds with an ICMP Destination Unreachable message so the server never resends the data with an appropriate packet for that router port. After 70 seconds the client's timer pops and the client requests that the connection be closed by setting the FIN bit in the IP packet.
Time Src Dst Protocol Description ======================================== 0.011 COLA11 HRS014 SMB C NT create & X, File = \BACKUP\HRS014C$.DAT 0.007 HRS014 COLA11 SMB R NT create & X, FID = 0x80c 0.004 COLA11 HRS014 SMB C transact2 GetFsInfo 0.003 HRS014 COLA11 SMB R transact2 GetFsInfo 0.004 COLA11 HRS014 SMB C transact2 GetFileInfo, FID = 0x80c 0.003 HRS014 COLA11 SMB R transact2 GetFileInfo 0.005 COLA11 HRS014 SMB C transact2 GetFileInfo, FID = 0x80c 0.003 HRS014 COLA11 SMB R transact2 GetFileInfo 0.031 COLA11 HRS014 SMB C NT transact - Query Security Description 0.003 HRS014 COLA11 SMB R NT transact - Query Security Description 0.017 COLA11 HRS014 SMB C read block raw, FID = 0x80c, Read 0x7000 at 0x0 0.078 HRS014 COLA11 NBT SS: Session Message, Len: 28672 0.281 COLA11 HRS014 SMB C read block raw, FID = 0x80c, Read 0x7000 at 0x0 0.001 HRS014 COLA11 TCP .A.... 0.142 HRS014 COLA11 NBT SS: Session Message, Len: 28672 1.002 HRS014 COLA11 NBT SS: Session Message, Len: 28672 2.002 HRS014 COLA11 NBT SS: Session Message, Len: 28672 4.006 HRS014 COLA11 NBT SS: Session Message, Len: 28672 8.010 HRS014 COLA11 NBT SS: Session Message, Len: 28672 58.61 COLA11 HRS014 TCP .A...F 0.001 HRS014 COLA11 TCP ...R.. WORKAROUNDThis issue occurs on Token Ring ports in Cisco 7000 series routers with software version 9. The Maximum MTU size on a Cisco 7000 series Token Ring port is 4,464 (well below the Maximum packet size of 17K on a 16 MB Token Ring network). You can correct this problem on the router by reducing the Maximum MTU size to 4000 on the Cisco 7000 series router (software version 9). At a Maximum MTU size of 4000, the router sends the ICMP Destination Unreachable messages to the sender, resolving the problem. The following workarounds for the router problem impact network performance: WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.
|
Additional query words: prodnt 3.1 backup arcada megabyte
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |