Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

(This has started to get quite lengthy, but hopefully will provide a summary of things to try for anyone else that's bumped into this issue - it's not a simple one-size-fits-all solution by the looks of things; other solutions or avenues of investigation may be found in the answers as well).

I'm having problems getting a reliable share working on an x64 Server 2008 R1 SP1 server.

All works well after a reboot, but after some time (within a day) the shares become unavailable to XP and Server 2003 servers. Interestingly, they remain available to other Server 2008 servers.

On trying to access \\server\share, Server 2003 returns immediately and simply gives me the message "The specified network name is no longer available", XP takes a minute or two to timeout before giving the same message. There doesn't seem to be anything in the event logs indicating a problem.

Doing some googling over the last day or two I've seen the following blamed:

  • Bad network drivers (Broadcom [which is what the HP servers we use have] seems to get a few mentions for being flaky) ... I've updated to the latest drivers with no result (see refs 1 and 2)
  • Symantec anti-virus ... we're not using it (currently no AV on the server) (see refs 1 and 3)
  • Receive window auto-tuning ... I've disabled with netsh int tcp set global autotuninglevel=disabled and netsh int tcp set global rss=disabled (see ref 4)

None of these have had an effect. Windows Firewall is currently disabled.

As other Server 2008 boxes (both x32 and x64) can connect, I can only assume that there's some new security configuration that's not quite right - or there's an AD issue that I need to trace, but don't know where to start. Even if anyone doesn't know how to resolve, if someone knows what I need to look for with Wireshark this would be a help.

EDIT ... I've put a Wireshark trace on (filtered by target host only) and what I'm seeing is that the client (Server 2003 in this case) sends an SMB "Negotiate Protocol Request" message to Server 2008, however no "Negotiate Protocol Response" is received from the server. The client retries until it times out. Note however that the server is responding postively to a session request. This is the full sequence of events:

C -> S  NBSS Session Request
S -> C  NBSS Positive Session Response
C -> S  SMB  Negotiate Protocol Request
[no response; time passes].
C -> S  NBSS Session Request
S -> C  NBSS Positive Session Response
C -> S  SMB  Negotiate Protocol Request
[no response; time passes].
[repeat]

EDIT2... Wiresharking a SMB connection from Server 2008 client shows the the Negotiate Protocol Response being sent, but with SMBv2:

C -> S  NBSS Session Request
S -> C  NBSS Positive Session Response
C -> S  SMB  Negotiate Protocol Request
S -> C  SMB2 NegotiateProtocol Response
C -> S  SMB2 SessionSetup Request
S -> C  SMB2 SessionSetup Response
[then the conversation contines, bringing the share back]

I'm going to try disabling SMBv2 on the 2k8 server (as per these instructions on petri.co.il) and see if that helps - should force the server to use SMB1 everywhere then.

EDIT3... I've also found this article on Microsoft Technet Forums ("Windows 2008 Keep disconnecting shares + outlook 2007 keep loos conection to exchange 2007" [sic]), to which others have suggested checking TCP Offload Chimney configuration. At this present moment however having disabled SMB2 (see EDIT2, above) things seem to be okay at the moment - shares have yet to disappear having disabled SMB2 last Friday. A quick google's found someone else (MS Technet forum "File opening issue on a server 2008 share.") who found that disabling SMB2 was also a solution. I'll let this tick over for a couple more days before self-answering and closing this question down.


References...
(1) Microsoft Networking Team - Intermittent file sharing connectivity from various clients to a Windows Server 2008 server
(2) 424help.com - Windows 2008 Server Network Connectivity Problem
(3) Symantec AVForums - MR3 Locks up Server 2008 file shares
(4) Usenet - Server 2008 R2 file share access fails under heavy load (also mirrored on various web forums like techarena, eggheadcafe, etc)

share|improve this question
    
anything in the event logs? –  tony roth May 27 '10 at 18:35
    
@tony - nothing obvious... which isn't helping, annoyingly. –  Chris J May 27 '10 at 19:32
    
are all the servers on the same subnet –  tony roth May 27 '10 at 20:08
    
Servers are, yes. XP workstations aren't. –  Chris J May 27 '10 at 21:00
add comment

2 Answers

In your capture, add Packet Length to the displayed columns, and sort by that column. Do you have any frames that are larger than a normal ethernet frame? (1514 I think). You should take this capture from the server if possible. Or on a switch port that mirrors the server switch port.

share|improve this answer
    
I'll check that on Tuesday when I'm next in front of the servers. However currently I've got SMB2 disabled so I'll be checking to see if that's done something. If that's fixed it, I'll call it a day - if not, I'll dig further with the packet sizes. 1514 is ethernet-sized, yes. What's the train of thought? Checking to see if 2k8 is providing providing bad sized packets? –  Chris J May 30 '10 at 14:58
1  
We have experienced numerous issues with Win2003 and Win2008 where settings like Large Send Offload or Jumbo Frames will result in oversize frames sent from the server. When the destination is on the same subnet, it isn't a problem. But the these oversize frames will most likely not make it to a host on another subnet. Furthermore, there are several ways these settings can be enabled. netsh, registry settings. I have found it necessary to ensure that the settings are also on the network adapter to disable jumbo frames and large send offload. –  Greg Askew May 30 '10 at 15:18
    
Greg - Just FYI: disabling SMB2 seems to have resolved this for me. I've left jumbo frames alone; although they seem to be disabled for my kit anyway. However cheers for the heads-up. –  Chris J Jun 3 '10 at 8:59
add comment
up vote 0 down vote accepted

It's been nearly a week since SMB2 was disabled (see EDIT2 in the question), and sharing has been stable since then. For reference, the server is configured with:

  • Latest network drivers (for HP NC373i)
  • Receive window autotuning disabled (see question for details)
  • SMB2 disabled (via registry)

I could probably re-enable receive window autotuning, however as this is an active system, that's probably not going to happen quickly: I'm leaving it alone now on that grounds that if it ain't broke, don't fix it.

If anyone else has a similar issue, the solution may be different (see rest of this question) - however disabling SMB2 ultimately was the fix for my situation.

As an aside, a quick google seems to indicate other isses that can be worked around by disabling SMB2, including (the happy snappy short titles are direct from the MSDN KBs):

Hope this all helps someone else :-)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.