On 3/6/2024 3:20 PM, Frank Slootweg wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
Hi all,
All of a sudden we got a weird problem. We have a local wired network
with 2 W10 PC's and a W10 PC which acts as a server. On the server are
maps with files, which are accessable from our PC's. From my PC I have
access to all maps on the server. However, from the PC of my wife there
was all of a sudden no access to the maps anymore. We got this error
message when trying to open the map Files on the server (Z:):
An error occurred while attempting to reconnect Z: to \\Server\Files.
Microsoft Windows Network: The local device name is already in use. This >>> connection has not been restored.
[As the problem is back after an update:]
Call me stupid, but from the error message, I deduce that the *local*
*device*, i.e drive letter Z, is already in use.
On the problem client (not the server) the Network Drive Z: should be
visible in File Explorer in the 'This PC' view. If so, right-click on
the Network Drive Z: and choose 'Disconnect'. Now do whatever you did
initially (i.e. probably a long time ago) to create Network Drive Z:,
i.e. 'Map network drive...'.
There is one example here.
https://www.makeuseof.com/local-device-name-already-in-use-error-windows/
Administrator.
net use # This dumps something
net use Z /delete
net use Z: \\server\share /user:username password
Paul
Paul <nospam@needed.invalid> wrote:
On 3/6/2024 3:20 PM, Frank Slootweg wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
Hi all,
All of a sudden we got a weird problem. We have a local wired network
with 2 W10 PC's and a W10 PC which acts as a server. On the server are >>>> maps with files, which are accessable from our PC's. From my PC I have >>>> access to all maps on the server. However, from the PC of my wife there >>>> was all of a sudden no access to the maps anymore. We got this error
message when trying to open the map Files on the server (Z:):
An error occurred while attempting to reconnect Z: to \\Server\Files.
Microsoft Windows Network: The local device name is already in use. This >>>> connection has not been restored.
[As the problem is back after an update:]
Call me stupid, but from the error message, I deduce that the *local* >>> *device*, i.e drive letter Z, is already in use.
On the problem client (not the server) the Network Drive Z: should be >>> visible in File Explorer in the 'This PC' view. If so, right-click on
the Network Drive Z: and choose 'Disconnect'. Now do whatever you did
initially (i.e. probably a long time ago) to create Network Drive Z:,
i.e. 'Map network drive...'.
There is one example here.
https://www.makeuseof.com/local-device-name-already-in-use-error-windows/
Administrator.
net use # This dumps something
net use Z /delete
net use Z: \\server\share /user:username password
Good article and a nice set of commands. Hope it helps Fokke.
BTW, I hope Newyana2 isn't watching! Can't fix a problem with a couple
of commands, when you can fix it with umpteen clicks, can you!? :-)
Hi all,
All of a sudden we got a weird problem. We have a local wired network
with 2 W10 PC's and a W10 PC which acts as a server. On the server are
maps with files, which are accessable from our PC's. From my PC I have access to all maps on the server. However, from the PC of my wife there
was all of a sudden no access to the maps anymore. We got this error
message when trying to open the map Files on the server (Z:):
An error occurred while attempting to reconnect Z: to \\Server\Files. Microsoft Windows Network: The local device name is already in use. This connection has not been restored.
I rebooted her PC and the server, it didn't solve it.
On her PC I placed a system image back which I made with Macrium Reflect
a month ago. After starting up again, the problem was still there. No
maps are accessable. And, when opening the file explorer on her PC, it
takes a long time to open.
Do you have any suggestions how to solve this nasty problem?
Many thanks in advance.
With regards,
Fokke Nauta
On 07/03/2024 17:35, Frank Slootweg wrote:
Paul <nospam@needed.invalid> wrote:
On 3/6/2024 3:20 PM, Frank Slootweg wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
Hi all,
All of a sudden we got a weird problem. We have a local wired network >>>> with 2 W10 PC's and a W10 PC which acts as a server. On the server are >>>> maps with files, which are accessable from our PC's. From my PC I have >>>> access to all maps on the server. However, from the PC of my wife there >>>> was all of a sudden no access to the maps anymore. We got this error >>>> message when trying to open the map Files on the server (Z:):
An error occurred while attempting to reconnect Z: to \\Server\Files. >>>> Microsoft Windows Network: The local device name is already in use. This >>>> connection has not been restored.
[As the problem is back after an update:]
Call me stupid, but from the error message, I deduce that the *local* >>> *device*, i.e drive letter Z, is already in use.
On the problem client (not the server) the Network Drive Z: should be >>> visible in File Explorer in the 'This PC' view. If so, right-click on
the Network Drive Z: and choose 'Disconnect'. Now do whatever you did
initially (i.e. probably a long time ago) to create Network Drive Z:,
i.e. 'Map network drive...'.
There is one example here.
https://www.makeuseof.com/local-device-name-already-in-use-error-windows/ >>
Administrator.
net use # This dumps something
net use Z /delete
net use Z: \\server\share /user:username password
Good article and a nice set of commands. Hope it helps Fokke.
BTW, I hope Newyana2 isn't watching! Can't fix a problem with a couple of commands, when you can fix it with umpteen clicks, can you!? :-)
Hi Frank,
Who is Newyana2? What is an umpteen click?
On 06/03/2024 22:09, Paul wrote:[...]
There is one example here.
https://www.makeuseof.com/local-device-name-already-in-use-error-windows/
Administrator.
net use # This dumps something
net use Z /delete
net use Z: \\server\share /user:username password
Paul
Hi Paul,
Thanks.
I did:
net use
net use Z: /delete (that worked)
net use Z: \\Server\Files /user:"Fokke Nauta" xxx (where xxx stands for
the password). This did not work.
I placed a system image back from November. Now it worked again, but I
will definitively not update Windows.
Fokke Nauta <usenet@solfon.nl> wrote:
On 06/03/2024 22:09, Paul wrote:[...]
There is one example here.
https://www.makeuseof.com/local-device-name-already-in-use-error-windows/ >>>
Administrator.
net use # This dumps something
net use Z /delete
net use Z: \\server\share /user:username password
Paul
Hi Paul,
Thanks.
I did:
net use
net use Z: /delete (that worked)
net use Z: \\Server\Files /user:"Fokke Nauta" xxx (where xxx stands for
the password). This did not work.
Did you get an error message? If so, what did it say?
If you did not get an error message, then what does "This did not
work." mean, i.e. what did not work and did that give an error message
and if so which?
I placed a system image back from November. Now it worked again, but I
will definitively not update Windows.
Fokke Nauta <usenet@solfon.nl> wrote:
On 07/03/2024 17:35, Frank Slootweg wrote:
Paul <nospam@needed.invalid> wrote:
On 3/6/2024 3:20 PM, Frank Slootweg wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
Hi all,
All of a sudden we got a weird problem. We have a local wired network >>>>>> with 2 W10 PC's and a W10 PC which acts as a server. On the server are >>>>>> maps with files, which are accessable from our PC's. From my PC I have >>>>>> access to all maps on the server. However, from the PC of my wife there >>>>>> was all of a sudden no access to the maps anymore. We got this error >>>>>> message when trying to open the map Files on the server (Z:):
An error occurred while attempting to reconnect Z: to \\Server\Files. >>>>>> Microsoft Windows Network: The local device name is already in use. This >>>>>> connection has not been restored.
[As the problem is back after an update:]
Call me stupid, but from the error message, I deduce that the *local* >>>>> *device*, i.e drive letter Z, is already in use.
On the problem client (not the server) the Network Drive Z: should be >>>>> visible in File Explorer in the 'This PC' view. If so, right-click on >>>>> the Network Drive Z: and choose 'Disconnect'. Now do whatever you did >>>>> initially (i.e. probably a long time ago) to create Network Drive Z:, >>>>> i.e. 'Map network drive...'.
There is one example here.
https://www.makeuseof.com/local-device-name-already-in-use-error-windows/ >>>>
Administrator.
net use # This dumps something
net use Z /delete
net use Z: \\server\share /user:username password
Good article and a nice set of commands. Hope it helps Fokke.
BTW, I hope Newyana2 isn't watching! Can't fix a problem with a couple >>> of commands, when you can fix it with umpteen clicks, can you!? :-)
Hi Frank,
Who is Newyana2? What is an umpteen click?
Newyana2 is a poster in this/these group(s) who doesn't like
command-line commands, thinks they're old-fashioned, should not be
needed, etc., etc.. Hence the tease ('plaagstoot') and the smiley.
Of course *both* command-line commands *and* GUIs (Grahical User Interfaces) have their uses. If not, one or the other would cease to
exist and Microsoft would not be *adding* command-line commands over
time.
'Umpteen' means 'a lot of' (Dutch 'talloze'). Similar to 'a zillion', etc..
<https://translate.google.com/details?sl=en&tl=nl&text=%20umpteen%0A%0A%0A%0A&op=translate>
On 08/03/2024 17:00, Frank Slootweg wrote:[...]
<https://translate.google.com/details?sl=en&tl=nl&text=%20umpteen%0A%0A%0A%0A&op=translate>
Happily I am familiar with Google translate. I use it for these
newsgroups as well.
And according to your name you must be Dutch as well :-)
Fokke Nauta <usenet@solfon.nl> wrote:
On 08/03/2024 17:00, Frank Slootweg wrote:[...]
<https://translate.google.com/details?sl=en&tl=nl&text=%20umpteen%0A%0A%0A%0A&op=translate>
Happily I am familiar with Google translate. I use it for these
newsgroups as well.
And according to your name you must be Dutch as well :-)
Indeed, I am: "If it ain't Dutch, it ain't much!" :-)
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 7 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 150:40:02 |
| Calls: | 46 |
| Files: | 21,492 |
| Messages: | 65,402 |