1 Loss of mapped drive, networked drive disconnects

2 Windows 7 IT Pro
3 >
4 Windows 7 Networking
5 Question
6
7
8 0
9 Sign in to vote
10 I'm running Win7 ult x64. I am running on a network with 4 pcs, 2 vista, 2
xp. We have one server running 2000. I have mapped a couple of folders on
the server and can connect just fine when I first start my pc. But after
awhile the connection is lost. It still shows the drives, but not the
connection. This internet works fine and access is controlled through the
server. I can restart my machine and the drives will be connected and working
as they should. But after some time they will disconnect again. Win 7 is
acting like it is losing the connection to the network, because I can't map
another drive from one of the other PC's unless I reboot. But the internet
access is still working fine. Any ideas?
11 Moved by Chris.H-SBITMicrosoft Support Saturday, January 30, 2010 4:08 PM
(From:Networking, Mail, and Getting Online)
12 Friday, January 29, 2010 9:38 PM
13 Reply
14 |
15 Quote
16
17 infinite15
18
19 25 Points
20
21 Answers
22
23
24 1
25 Sign in to vote
26
27 This behavior is caused by the default policy setting in the Windows Server.
28 Mapped Drive Connection to Network Share May Be Lost
29 http://support.microsoft.com/kb/297684
30 Sometimes firewall can also cause this kind of issues. I suggest you temporary
disable the firewall on both computers.
31 After doing these, the mapped drives should not disconnect.
32 In general situations, although the connections disconnect after a while, it
should be able to reconnect if you launch it. In this case you may need to
change the NTLM authentication level. Please refer the following website.
33 Network security: LAN Manager authentication level
34 The policy is:
35 Computer Configuration\Windows Settings\Security Settings\Local
Policies\Security Options\Network security: LAN Manager authentication level
36 Please change “Send LM & NTLM - use NTLMv2 session security if negotiated”.
37 If your system is Windows 7 Home Premium, you may change it from Registry.
38 1. Launch regedit from Start Search box.
39 2. Find the following branch.
40
41 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
42 3. Create a DWORD key under Lsa and set:
43 Name: LmCompatibilityLevel
44 Value: 1
45 4. Restart.
46
47 Arthur Xie - MSFT
48 Marked as answer by infinite15 Wednesday, February 10, 2010 8:58 PM
49 Monday, February 8, 2010 5:50 AM
50 Reply
51 |
52 Quote
53
54 Arthur Xie
55
56 33,755 Points
57 Moderator
58 All replies
59
60
61 1
62 Sign in to vote
63
64 This behavior is caused by the default policy setting in the Windows Server.
65 Mapped Drive Connection to Network Share May Be Lost
66 http://support.microsoft.com/kb/297684
67 Sometimes firewall can also cause this kind of issues. I suggest you temporary
disable the firewall on both computers.
68 After doing these, the mapped drives should not disconnect.
69 In general situations, although the connections disconnect after a while, it
should be able to reconnect if you launch it. In this case you may need to
change the NTLM authentication level. Please refer the following website.
70 Network security: LAN Manager authentication level
71 The policy is:
72 Computer Configuration\Windows Settings\Security Settings\Local
Policies\Security Options\Network security: LAN Manager authentication level
73 Please change “Send LM & NTLM - use NTLMv2 session security if negotiated”.
74 If your system is Windows 7 Home Premium, you may change it from Registry.
75 1. Launch regedit from Start Search box.
76 2. Find the following branch.
77
78 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
79 3. Create a DWORD key under Lsa and set:
80 Name: LmCompatibilityLevel
81 Value: 1
82 4. Restart.
83
84 Arthur Xie - MSFT
85 Marked as answer by infinite15 Wednesday, February 10, 2010 8:58 PM
86 Monday, February 8, 2010 5:50 AM
87 Reply
88 |
89 Quote
90
91 Arthur Xie
92
93 33,755 Points
94 Moderator
95
96
97 0
98 Sign in to vote
99 Do you know if this is an issue with server 2008 R2? We will be moving over
in a month or two and just wondering if I should expect similar issues.
100
101
102 edit: and thanks for the above post. It worked great. As soon as I changed
the autodisconnect time it recognized the drives immediately and is working
great.
103 Wednesday, February 10, 2010 8:13 PM
104 Reply
105 |
106 Quote
107
108 infinite15
109
110 25 Points
111
112
113
114 0
115 Sign in to vote
116 I have a similar situation. In my case, I have several users on Windows 7 pro
but only one has issues with a mapped drive disappearing. He indicated that it
happens mostly when logging on but occasionally during the day. More so, he
experiences most of the disappearances using a VPN. We suspected the VPN at
first, of course, but after getting the same behavior on the LAN we had to
re-think it. Under Windows XP the user did just fine but once we moved him
over to Win 7 it changed. At one time I tried your suggestion "Please change
“Send LM & NTLM - use NTLMv2 session security if negotiated” but that did not
work in our case. Any other suggestions? Thanks for your time.
117 The affected mapped drive path goes to a SAN with VMWare 2008 Enterprise server.
118 Firewalls are off on both ends
119 Wednesday, May 5, 2010 2:36 PM
120 Reply
121 |
122 Quote
123
124 JICdbs
125
126 5 Points
127
128
129
130 0
131 Sign in to vote
132 I am having same trouble with only windows 7 professional workstations. They
are having the mapped drives shade out and the only thing that gets them
 reconnected is restarted the computer. We even have the policy client side
extensions GPO in place on a 2008 DC for mapped drives instead of using login
scripts. We do have some 2003 DCs active, however the file shares reside on a
2008 file server where the mappings occur. Anyone come up with a solution to
this one? Also, this is also a SAN and all servers are VMs on VMWare.
133 Friday, May 21, 2010 5:34 PM
134 Reply
135 |
136 Quote
137
138 ATNewby
139
140 0 Points
141
142
143
144 0
145 Sign in to vote
146 I have a similar problem on a home network where my Win 7 Pro 64 bit machine
loses access to a Win XP box which is being used as a file server.
147 Very frustrating & only fixed by a reboot.
148 I've applied the fixes in the posts above & will post if the problem recurs.
149
150 Monday, June 14, 2010 5:15 PM
151 Reply
152 |
153 Quote
154
155 ARMAsoft
156
157 0 Points
158
159
160
161 0
162 Sign in to vote
163 No luck - still losing access to local shares.
164 Tuesday, June 15, 2010 7:29 PM
165 Reply
166 |
167 Quote
168
169 ARMAsoft
170
171 0 Points
172
173
174
175 0
176 Sign in to vote
177 I 've got a network with one Win 7 machine and the other XP. The XP machine
is password protected, the Win 7 machine is not.
178 Problem:
179 Drive mappings on the Win 7 machine are lost at every reboot.
180 Fix:
181 I added a password to the Win 7 machine, and the drive mappings are retained.
Mirabile dictu!
182 It's repeatable: remove the password from the Win 7 machine, and mappings are
lost. Reinstate the password, and the mappings are retained.
183 I've tried every fix I could find on the net, and this is the only thing I've
found that works for me.
184
185
186
187 Wednesday, June 23, 2010 6:16 PM
188 Reply
189 |
190 Quote
191
192 LOK2
193
194 0 Points
195
196
197
198 1
199 Sign in to vote
200 To All,
201 Here is what I have found. This is a problem with Windows 7 and nothing
else. After several test and looking at forum after forum. here is what I
came up with.
202 I have 3 machines. 1 (XP) and 2(Windows 7 recently loaded). the 2 machines
that I loaded Windows 7 (fresh) were both XP. The 1 XP machine that is still
XP for this post I will call File_Machine (because this is where I hold my
files and map to from the other machines.
203 1. When my other 2 machines were loaded with XP I have no problem with mapped
drives. No dropping or reconnection problems.
204 2. I load Windows 7 on 1 of my machines and start noticing when I would
shutdown or logoff it woudl hang at the log off screen and the only way to
shutdown is a hard shutdown. I knew it was related to a network connections
not closing or something but could not isolate it.
205 3. Installed Windows 7 one the other machine (oohh by the way 1 is Windows 7
Ultimate and the other is Professional). I started experiencing the same
problems with this machine mapping back the my File_Machine.
206 4. Saw a post referencing the idle network connection disconnect feature in
the Windows Operating system.. so I looked at my XP machine (File_machine)
active sessions.
207 5. I brought both windows 7 machine online and let them restore the network
connections to the XP box. after being idle for a while the sessions dropped
because they were idle (this is normal and by default). ok fine.. no problems
there.
208 6. here is the kicker.. when I went back to either Windows 7 machine and
clicked on the mapped drive, it hung and would not reconnect to the share.
the share is fine and active. The problem is the Windows 7 is not sending the
correct signal to the system housing the share to reconnect.
209 7. To confirm this I ran the following command on the XP (File_machine).. NET
CONFIG SERVER /AUTODISCONNECT:-1 (this command disabled the autodisconnect
feature in a network connection is idle).. the (-1) represents the duration to
 wait before disconnecting. -1 is to disable.. I believe the number range is
from 0 to 655555 or something.. representing seconds.
210 8. after the was disabled there were no more dropped connections.
211 9. set the number to 1 and tested again.. and the problem came back..
212 What does this say.. Microsoft needs to look at Windows 7 reconnection attempt
commands for idle connection and see what signal is being sent to the resource
to say wake up and reconnect me because it's not working..
213 Hopes this helps everyone and Hope MS reads this and looks into it.. You know
have the info on how to recreate the problem.
214 Proposed as answer by What_I_Found Wednesday, July 7, 2010 4:03 AM
215 Wednesday, July 7, 2010 3:46 AM
216 Reply
217 |
218 Quote
219
220 What_I_Found
221
222 20 Points
223
224
225
226 0
227 Sign in to vote
228 To All,
229 Here is what I have found. This is a problem with Windows 7 and nothing
else. After several test and looking at forum after forum. here is what I
came up with.
230 I have 3 machines. 1 (XP) and 2(Windows 7 recently loaded). the 2 machines
that I loaded Windows 7 (fresh) were both XP. The 1 XP machine that is still
XP for this post I will call File_Machine (because this is where I hold my
files and map to from the other machines.
231 1. When my other 2 machines were loaded with XP I have no problem with mapped
drives. No dropping or reconnection problems.
232 2. I load Windows 7 on 1 of my machines and start noticing when I would
shutdown or logoff it woudl hang at the log off screen and the only way to
shutdown is a hard shutdown. I knew it was related to a network connections
not closing or something but could not isolate it.
233 3. Installed Windows 7 one the other machine (oohh by the way 1 is Windows 7
Ultimate and the other is Professional). I started experiencing the same
problems with this machine mapping back the my File_Machine.
234 4. Saw a post referencing the idle network connection disconnect feature in
the Windows Operating system.. so I looked at my XP machine (File_machine)
active sessions.
235 5. I brought both windows 7 machine online and let them restore the network
connections to the XP box. after being idle for a while the sessions dropped
because they were idle (this is normal and by default). ok fine.. no problems
there.
236 6. here is the kicker.. when I went back to either Windows 7 machine and
clicked on the mapped drive, it hung and would not reconnect to the share.
the share is fine and active. The problem is the Windows 7 is not sending the
correct signal to the system housing the share to reconnect.
237 7. To confirm this I ran the following command on the XP (File_machine).. NET
CONFIG SERVER /AUTODISCONNECT:-1 (this command disabled the autodisconnect
feature in a network connection is idle).. the (-1) represents the duration to
 wait before disconnecting. -1 is to disable.. I believe the number range is
from 0 to 655555 or something.. representing seconds.
238 8. after the was disabled there were no more dropped connections.
239 9. set the number to 1 and tested again.. and the problem came back..
240 What does this say.. Microsoft needs to look at Windows 7 reconnection attempt
commands for idle connection and see what signal is being sent to the resource
to say wake up and reconnect me because it's not working..
241 Hopes this helps everyone and Hope MS reads this and looks into it.. You know
have the info on how to recreate the problem.
242