Hi
After we haven't found a solution for weeks now, I hope someone here has a suggestion.
Local network, new Server 2008 R2 SP1 fileserver with mapped drives with VB login script on each client computer; WinXP and Win7. After login, the script map all the drives, but after while the mapped drives have a red X in the Explorer on the Win7 clients, WinXP never has any disconnected drives.
What we did already:
- disabled autodisconnect on the servers kb297684
- set keepconn to 65535 on each Win7
- disabled Chimney Offload State
- completly disabled IPv6 on both sides
- updated all NIC drivers
- disabled power saving on all NIC
- played with the Spanning-tree and portfast settings on Cisco switches
- set the keep alive interval on 120 seconds
- disabled Netbios over TCPIP on some test computers
We haven't any DNS problems, we can't see any disconnects or dropped packets on our Cisco switches and we have the same behaviour not just with one Windows 2008 R2 server, we have it on 2003 servers and for testing we created some shares on Win7 computers.
After a Whireshark trace on both sides, we could see that after the login script mapped the drives, the Server 2008 sends the keep alive packets on TCP445 to the client and the client responds with ACK each 120 seconds. But after a while the server doesn't send any keep alive packet anymore, instead it sends out a TCP445 RST, ACK packet and resets the connection. Immediately the clients have a red X in the Explorer. Sometimes it takes longer when the client is keeping the Explorer open instead of closing the Explorer, but it happens as well.
So what could be the reason, why the server still send some RST packets?
What I haven't disabled yet is the Receive Window Auto-Tuning Level on the server, because I guess this bug should be patched since a few years now.
Any suggestions?
Thx, Wayne