System Error 1202 - Local device name has a remembered connection to another network resource
up vote
0
down vote
favorite
I just updated my Windows 10 computer to Update 1607 (the Anniversary Update). I now get the error in the title when doing the following:
- From a cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this new cmd window:
net use g: \fsSales
- From a new cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this second new cmd window:
net use g: \fsOperations
- This results in the following output:
System error 1202 has occurred.
The local device name has a remembered connection to another network resource.
- This results in the following output:
This has worked for me for years (since at least Windows 7) and for Windows 10 through Update 1511. After installing Update 1607 it now fails. Is this a bug in the Windows update or do I need to use a workaround?
networking windows-10 command-line windows-10-v1607
asked Sep 22 '16 at 13:45
mwolfe02
340417
add a comment |
up vote
0
down vote
favorite
I just updated my Windows 10 computer to Update 1607 (the Anniversary Update). I now get the error in the title when doing the following:
- From a cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this new cmd window:
net use g: \fsSales
- From a new cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this second new cmd window:
net use g: \fsOperations
- This results in the following output:
System error 1202 has occurred.
The local device name has a remembered connection to another network resource.
- This results in the following output:
This has worked for me for years (since at least Windows 7) and for Windows 10 through Update 1511. After installing Update 1607 it now fails. Is this a bug in the Windows update or do I need to use a workaround?
networking windows-10 command-line windows-10-v1607
asked Sep 22 '16 at 13:45
mwolfe02
340417
Why do you need to do this?
– mwolfe02
Sep 22 '16 at 13:47
I'm a software developer and consultant. One of my large clients has a fairly typical network setup where different departments have the same drive letter mapped to different network shares. I'm not a member of their domain, so I run into trust issues if I try to map the drives directly. The easiest workaround is to use arunascmd with the/netonlyflag. This has the added benefit of creating an isolated environment within the cmd window. It has allowed me to have multiple cmd windows each with their own G: drive mapped to a different department.
– mwolfe02
Sep 22 '16 at 13:50
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I just updated my Windows 10 computer to Update 1607 (the Anniversary Update). I now get the error in the title when doing the following:
- From a cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this new cmd window:
net use g: \fsSales
- From a new cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this second new cmd window:
net use g: \fsOperations
- This results in the following output:
System error 1202 has occurred.
The local device name has a remembered connection to another network resource.
- This results in the following output:
This has worked for me for years (since at least Windows 7) and for Windows 10 through Update 1511. After installing Update 1607 it now fails. Is this a bug in the Windows update or do I need to use a workaround?
networking windows-10 command-line windows-10-v1607
asked Sep 22 '16 at 13:45
mwolfe02
340417
I just updated my Windows 10 computer to Update 1607 (the Anniversary Update). I now get the error in the title when doing the following:
- From a cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this new cmd window:
net use g: \fsSales
- From a new cmd prompt:
runas /user:contosomwolfe /netonly cmd
- From this second new cmd window:
net use g: \fsOperations
- This results in the following output:
System error 1202 has occurred.
The local device name has a remembered connection to another network resource.
- This results in the following output:
This has worked for me for years (since at least Windows 7) and for Windows 10 through Update 1511. After installing Update 1607 it now fails. Is this a bug in the Windows update or do I need to use a workaround?
networking windows-10 command-line windows-10-v1607
networking windows-10 command-line windows-10-v1607
asked Sep 22 '16 at 13:45
mwolfe02
340417
asked Sep 22 '16 at 13:45
mwolfe02
340417
asked Sep 22 '16 at 13:45
mwolfe02
340417
asked Sep 22 '16 at 13:45
mwolfe02
340417
asked Sep 22 '16 at 13:45
mwolfe02
340417
340417
Why do you need to do this?
– mwolfe02
Sep 22 '16 at 13:47
I'm a software developer and consultant. One of my large clients has a fairly typical network setup where different departments have the same drive letter mapped to different network shares. I'm not a member of their domain, so I run into trust issues if I try to map the drives directly. The easiest workaround is to use arunascmd with the/netonlyflag. This has the added benefit of creating an isolated environment within the cmd window. It has allowed me to have multiple cmd windows each with their own G: drive mapped to a different department.
– mwolfe02
Sep 22 '16 at 13:50
add a comment |
Why do you need to do this?
– mwolfe02
Sep 22 '16 at 13:47
I'm a software developer and consultant. One of my large clients has a fairly typical network setup where different departments have the same drive letter mapped to different network shares. I'm not a member of their domain, so I run into trust issues if I try to map the drives directly. The easiest workaround is to use arunascmd with the/netonlyflag. This has the added benefit of creating an isolated environment within the cmd window. It has allowed me to have multiple cmd windows each with their own G: drive mapped to a different department.
– mwolfe02
Sep 22 '16 at 13:50
Why do you need to do this?
– mwolfe02
Sep 22 '16 at 13:47
Why do you need to do this?
– mwolfe02
Sep 22 '16 at 13:47
I'm a software developer and consultant. One of my large clients has a fairly typical network setup where different departments have the same drive letter mapped to different network shares. I'm not a member of their domain, so I run into trust issues if I try to map the drives directly. The easiest workaround is to use a
runas cmd with the /netonly flag. This has the added benefit of creating an isolated environment within the cmd window. It has allowed me to have multiple cmd windows each with their own G: drive mapped to a different department.– mwolfe02
Sep 22 '16 at 13:50
I'm a software developer and consultant. One of my large clients has a fairly typical network setup where different departments have the same drive letter mapped to different network shares. I'm not a member of their domain, so I run into trust issues if I try to map the drives directly. The easiest workaround is to use a
runas cmd with the /netonly flag. This has the added benefit of creating an isolated environment within the cmd window. It has allowed me to have multiple cmd windows each with their own G: drive mapped to a different department.– mwolfe02
Sep 22 '16 at 13:50
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Try closing all the cmd windows and starting over.
answered Sep 22 '16 at 14:00
mwolfe02
340417
This seems to have been a temporary issue. I closed every cmd window then tried to reproduce it and the problem disappeared. At this point I will assume it was a fluke and move on. I would have tried this first except I had just updated to Win 10 v1607. This was the very first time I tried this on update 1607 so I immediately assumed that was the culprit. I still think it must have something to do with it. This was the first time in seven years of using this on an almost daily basis that I saw this error. It's got to be more than mere coincidence, but I could be wrong.
– mwolfe02
Sep 22 '16 at 14:03
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Try closing all the cmd windows and starting over.
answered Sep 22 '16 at 14:00
mwolfe02
340417
This seems to have been a temporary issue. I closed every cmd window then tried to reproduce it and the problem disappeared. At this point I will assume it was a fluke and move on. I would have tried this first except I had just updated to Win 10 v1607. This was the very first time I tried this on update 1607 so I immediately assumed that was the culprit. I still think it must have something to do with it. This was the first time in seven years of using this on an almost daily basis that I saw this error. It's got to be more than mere coincidence, but I could be wrong.
– mwolfe02
Sep 22 '16 at 14:03
add a comment |
up vote
0
down vote
Try closing all the cmd windows and starting over.
answered Sep 22 '16 at 14:00
mwolfe02
340417
This seems to have been a temporary issue. I closed every cmd window then tried to reproduce it and the problem disappeared. At this point I will assume it was a fluke and move on. I would have tried this first except I had just updated to Win 10 v1607. This was the very first time I tried this on update 1607 so I immediately assumed that was the culprit. I still think it must have something to do with it. This was the first time in seven years of using this on an almost daily basis that I saw this error. It's got to be more than mere coincidence, but I could be wrong.
– mwolfe02
Sep 22 '16 at 14:03
add a comment |
up vote
0
down vote
up vote
0
down vote
Try closing all the cmd windows and starting over.
answered Sep 22 '16 at 14:00
mwolfe02
340417
Try closing all the cmd windows and starting over.
answered Sep 22 '16 at 14:00
mwolfe02
340417
answered Sep 22 '16 at 14:00
mwolfe02
340417
answered Sep 22 '16 at 14:00
mwolfe02
340417
answered Sep 22 '16 at 14:00
mwolfe02
340417
340417
This seems to have been a temporary issue. I closed every cmd window then tried to reproduce it and the problem disappeared. At this point I will assume it was a fluke and move on. I would have tried this first except I had just updated to Win 10 v1607. This was the very first time I tried this on update 1607 so I immediately assumed that was the culprit. I still think it must have something to do with it. This was the first time in seven years of using this on an almost daily basis that I saw this error. It's got to be more than mere coincidence, but I could be wrong.
– mwolfe02
Sep 22 '16 at 14:03
add a comment |
This seems to have been a temporary issue. I closed every cmd window then tried to reproduce it and the problem disappeared. At this point I will assume it was a fluke and move on. I would have tried this first except I had just updated to Win 10 v1607. This was the very first time I tried this on update 1607 so I immediately assumed that was the culprit. I still think it must have something to do with it. This was the first time in seven years of using this on an almost daily basis that I saw this error. It's got to be more than mere coincidence, but I could be wrong.
– mwolfe02
Sep 22 '16 at 14:03
This seems to have been a temporary issue. I closed every cmd window then tried to reproduce it and the problem disappeared. At this point I will assume it was a fluke and move on. I would have tried this first except I had just updated to Win 10 v1607. This was the very first time I tried this on update 1607 so I immediately assumed that was the culprit. I still think it must have something to do with it. This was the first time in seven years of using this on an almost daily basis that I saw this error. It's got to be more than mere coincidence, but I could be wrong.
– mwolfe02
Sep 22 '16 at 14:03
This seems to have been a temporary issue. I closed every cmd window then tried to reproduce it and the problem disappeared. At this point I will assume it was a fluke and move on. I would have tried this first except I had just updated to Win 10 v1607. This was the very first time I tried this on update 1607 so I immediately assumed that was the culprit. I still think it must have something to do with it. This was the first time in seven years of using this on an almost daily basis that I saw this error. It's got to be more than mere coincidence, but I could be wrong.
– mwolfe02
Sep 22 '16 at 14:03
add a comment |
draft saved
draft discarded
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1127157%2fsystem-error-1202-local-device-name-has-a-remembered-connection-to-another-net%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why do you need to do this?
– mwolfe02
Sep 22 '16 at 13:47
I'm a software developer and consultant. One of my large clients has a fairly typical network setup where different departments have the same drive letter mapped to different network shares. I'm not a member of their domain, so I run into trust issues if I try to map the drives directly. The easiest workaround is to use a
runascmd with the/netonlyflag. This has the added benefit of creating an isolated environment within the cmd window. It has allowed me to have multiple cmd windows each with their own G: drive mapped to a different department.– mwolfe02
Sep 22 '16 at 13:50