Mapped Drive Loosing Connection after 6 to 8 hours

[ap3xne]

Ok, here is a problem I have been having lately and it is driving me crazy. I have a network with a server running 2008 Standard R2 and 4 workstations using Windows 7 Professional 64-bit. I also have 1 other station using Windows XP Professional. The software I run off the server is installed as a client install on the workstations and have to use a mapped drive of E: to let the software see the database. Every 6 to 8 hours of non use of the software... when I reopen it I get a not responding and it has to close and reopen. I looked at the mapped drives and the E: drive disconnects but after opening the E: Drive up it connects right away and then the software works fine. I have tried a lot of things people are saying online. I have disabled autodisconnect -1 in the registry and turned off power management on the Ethernet port. I get the following message when I look at the event viewer...

Event 1005, Application Error
"Windows cannot access the file for one of the following reasons: there is problem with the network connection, the disk that the file is stored on, or storage drivers on tihs computer may be missing."

But here is the kicker... The windows XP Professional works all the time with no problems so it has to be Windows 7. I have the IPs static in the NIC properties and using the DNS of 8.8.8.8 and 8.8.4.4 which is Google. I was using 192.168.0.100 which was the IP of the server but that didn't make a difference.

I gave a lot of details to weed out the normal postings so any help would be appreciated. Also I have DHCP and DNS turned on the server if that would be any possible issue that is causing. I don't know beings I put Google as the DNS if routing in the software would be an issue?

 

[zigzag3143]

Ok, here is a problem I have been having lately and it is driving me crazy. I have a network with a server running 2008 Standard R2 and 4 workstations using Windows 7 Professional 64-bit. I also have 1 other station using Windows XP Professional. The software I run off the server is installed as a client install on the workstations and have to use a mapped drive of E: to let the software see the database. Every 6 to 8 hours of non use of the software... when I reopen it I get a not responding and it has to close and reopen. I looked at the mapped drives and the E: drive disconnects but after opening the E: Drive up it connects right away and then the software works fine. I have tried a lot of things people are saying online. I have disabled autodisconnect -1 in the registry and turned off power management on the Ethernet port. I get the following message when I look at the event viewer...

Event 1005, Application Error
"Windows cannot access the file for one of the following reasons: there is problem with the network connection, the disk that the file is stored on, or storage drivers on tihs computer may be missing."

But here is the kicker... The windows XP Professional works all the time with no problems so it has to be Windows 7. I have the IPs static in the NIC properties and using the DNS of 8.8.8.8 and 8.8.4.4 which is Google. I was using 192.168.0.100 which was the IP of the server but that didn't make a difference.

I gave a lot of details to weed out the normal postings so any help would be appreciated. Also I have DHCP and DNS turned on the server if that would be any possible issue that is causing. I don't know beings I put Google as the DNS if routing in the software would be an issue?

Could be dns, or using IPv6. Are you using homegroup (and IPv6)? check by running ipconfig /all and upload the output.


Ken J

 

[ap3xne]

I am not using IPv6.

ipconfig /all details:

DHCP Enabled: No
Autoconfig enabled: Yes
IPv4 Address: 192.168.0.51
Subnet: 255.255.255.0
Default Gateway: 192.168.0.1
DNS: 192.168.0.100, 8.8.8.8
Netbios Over tcip: Enabled

I am not using homegroup.

 

[Zymos]

Ap3xne,
I struggled with this for a couple of weeks before finally figuring it out. After that I involved microsoft with my findings and they admitted to the bug and wanted me to help them test a solution. I haven't had time and let my case slip closed. Maybe this will be fixed in server / workstation 8 upgrades.
Anyways, this is due to SMBv2 signing which is new to vista/7 and windows 2008. I first noticed that this bug existed in one of my government clients. Everything worked well in XP workstations with a 2k8r2 server, but when i upgraded them to win7 all heck broke loose.
There is 2 parts to fixing this:
First:
Run on the server in a administrative command prompt. c:\net config server /autodisconnect:-1
This will turn off the automatic drive mapping disconnect.
Second:
This part I recommend running on the Windows 7 and vista workstations and not the server. Again, go to an administrative command prompt (on each workstation) and run c:\sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
and
c:\sc config mrxsmb20 start= disabled
This will disable SMBv2 signing on the local workstations and they will resort to SMB (version 1) signing.

Reboot the machine and you are fixed.

** You can also bypass smbv2 siging by using ip addresses in the mappings instead of hostnames. (IPs use NTLM and not SMB) The only issue is you will have to know how to add the IPs of the servers into IE or you will get an error about the app being untrusted everytime you launch it.

Hope this helps. It was driving me buggy for awhile.
Nick
Network / Systems Engineer