F5F Stay Refreshed Hardware Desktop Issue with the network drive on one computer not functioning properly.

Issue with the network drive on one computer not functioning properly.

Issue with the network drive on one computer not functioning properly.

B
BearCraft3
Junior Member
7
07-20-2020, 12:46 PM
#1
Good morning/afternoon. My laptop was functioning properly until last week when access to the network share drives stopped. Initially, it displayed incorrect credentials, then it showed "The Local Device name is already in use." All six drives failed after that. I’ve tried using CMD commands like (net use Z: /delete) and (net use Z: \\computer_name\share_name /PERSISTENT:YES) to temporarily fix it, but none of the other solutions worked. If anyone has a permanent fix, please let me know.
B
BearCraft3
07-20-2020, 12:46 PM #1

Good morning/afternoon. My laptop was functioning properly until last week when access to the network share drives stopped. Initially, it displayed incorrect credentials, then it showed "The Local Device name is already in use." All six drives failed after that. I’ve tried using CMD commands like (net use Z: /delete) and (net use Z: \\computer_name\share_name /PERSISTENT:YES) to temporarily fix it, but none of the other solutions worked. If anyone has a permanent fix, please let me know.

T
TomekCZE
Junior Member
28
07-20-2020, 08:02 PM
#2
I've encountered this problem before—password changes or clock discrepancies. Have you verified it? Edit: The clock being checked should match the current system time, file server, and logon domain controller settings.
T
TomekCZE
07-20-2020, 08:02 PM #2

I've encountered this problem before—password changes or clock discrepancies. Have you verified it? Edit: The clock being checked should match the current system time, file server, and logon domain controller settings.

S
sparkdog202
Member
50
07-22-2020, 03:04 AM
#3
The system is functioning properly with the correct time setting. There has been no change to the password, and her most recent activity occurred on a different platform. She accessed the service via a VPN, then disconnected it afterward, and returned here. It seems unlikely this would influence the current shares.
S
sparkdog202
07-22-2020, 03:04 AM #3

The system is functioning properly with the correct time setting. There has been no change to the password, and her most recent activity occurred on a different platform. She accessed the service via a VPN, then disconnected it afterward, and returned here. It seems unlikely this would influence the current shares.

N
naruto162
Member
199
07-22-2020, 04:31 AM
#4
I've tested it both with and without a VPN, but it didn't make any difference, as I expected.
N
naruto162
07-22-2020, 04:31 AM #4

I've tested it both with and without a VPN, but it didn't make any difference, as I expected.

L
Leopoldfun
Member
82
07-22-2020, 10:40 AM
#5
I’m re-attempting the Temp fix now. Since I’m the only IT person on the team, getting it resolved quickly is crucial so we can keep operations running. Please share any suggestions if you have them.
L
Leopoldfun
07-22-2020, 10:40 AM #5

I’m re-attempting the Temp fix now. Since I’m the only IT person on the team, getting it resolved quickly is crucial so we can keep operations running. Please share any suggestions if you have them.

S
Saricck
Member
103
07-25-2020, 04:10 PM
#6
i've made many disk mappings because of these problems. usually i delete them if the drive is already mounted. when two departments share the same drive for documents, and someone switches departments, it causes issues if they don't reboot or log out properly—just close the laptop and lock it. for users turning it off, it stops and for us it's hibernation. windows keeps mappings or doesn't always disconnect them correctly, which can cause kerboros keys to fail if not refreshed before restarting. it's still a bit of a gamble. most people rely on a gpo mapped link to the logon script they can run to reconnect. to fix this, you should delete the old drivemapping first so there are no duplicate logon scripts.
S
Saricck
07-25-2020, 04:10 PM #6

i've made many disk mappings because of these problems. usually i delete them if the drive is already mounted. when two departments share the same drive for documents, and someone switches departments, it causes issues if they don't reboot or log out properly—just close the laptop and lock it. for users turning it off, it stops and for us it's hibernation. windows keeps mappings or doesn't always disconnect them correctly, which can cause kerboros keys to fail if not refreshed before restarting. it's still a bit of a gamble. most people rely on a gpo mapped link to the logon script they can run to reconnect. to fix this, you should delete the old drivemapping first so there are no duplicate logon scripts.

S
Sean_Nosliw
Junior Member
24
07-26-2020, 10:01 AM
#7
You're wondering if the drive letters on your Windows machine are correct. Have you looked in Drive Manager to confirm everything is set properly?
S
Sean_Nosliw
07-26-2020, 10:01 AM #7

You're wondering if the drive letters on your Windows machine are correct. Have you looked in Drive Manager to confirm everything is set properly?

A
Altone123
Member
62
07-27-2020, 03:37 PM
#8
This makes sense, though everything remains the same except for a single incident today with no reason and no changes overall.
A
Altone123
07-27-2020, 03:37 PM #8

This makes sense, though everything remains the same except for a single incident today with no reason and no changes overall.

N
Noxder_oJ
Member
131
07-27-2020, 08:52 PM
#9
Here are the possible factors influencing it: certificate distribution, window update patches, VPN usage mentioned by her, IP range logging rules, Kerberos token expiration, and timeouts. Always create disk mappings that function effectively right away through a script.
N
Noxder_oJ
07-27-2020, 08:52 PM #9

Here are the possible factors influencing it: certificate distribution, window update patches, VPN usage mentioned by her, IP range logging rules, Kerberos token expiration, and timeouts. Always create disk mappings that function effectively right away through a script.

M
messi298
Member
68
07-28-2020, 02:50 AM
#10
Good morning, just to note the update, the solution resolved the VPN cache credentials issue and everything functioned properly once I manually reinstalled the shares using CMD.
M
messi298
07-28-2020, 02:50 AM #10

Good morning, just to note the update, the solution resolved the VPN cache credentials issue and everything functioned properly once I manually reinstalled the shares using CMD.