SharePoint mapped as network drive no longer works











up vote
0
down vote

favorite












I have in the past accessed two SharePoint sites on our company network by mapping them as network drives. That is, I have added a network drive in File Explorer to a URL of the form



https://sharepoint.mycompany.com/sites/1234


I work mostly via VPN, so on login the drives show as disconnected. Upon opening the drive for the first time per session, the connection would get established and I was able to browse the site contents.



This has worked until recently, when I started getting an error message when I tried to access the drive (by double-clicking the disconnected drive in Explorer). The message reads:



An error occurred while reconnecting S: to
https://sharepoint.mycompany.com/sites/1234
Web Client Network: The network path was not found.

This connection has not been restored.


I have tried removing and re-mapping one of the two drives, which fails with the message:



Error code: 0x80070043
The network name cannot be found.


I can still open the URL in my web browser (indicating the site is available and name resolution works).



OS is Windows 7. The Web Client service is running (started manually). I have added the SharePoint site to the Trusted Sites zone in Internet Explorer.



What gives?










share|improve this question






















  • I'm voting to close this question as off-topic because issues specific to corporate IT support and networks are off topic, see On-Topic. Please talk to your IT department.
    – DavidPostill
    Nov 22 at 20:44










  • I’d say this is a generic question: What settings need to be in place on the client and the SharePoint server in order for drive mapping to work, and what change to a once working setup would cause the aforementioned malfunction?
    – user149408
    Nov 23 at 11:41










  • For the record, I was finally able to map the site as \sharepoint.mycompany.com@SSLDavWWWRootsites1234 (note the extra DavWWWRoot in the path).
    – user149408
    Nov 23 at 12:03















up vote
0
down vote

favorite












I have in the past accessed two SharePoint sites on our company network by mapping them as network drives. That is, I have added a network drive in File Explorer to a URL of the form



https://sharepoint.mycompany.com/sites/1234


I work mostly via VPN, so on login the drives show as disconnected. Upon opening the drive for the first time per session, the connection would get established and I was able to browse the site contents.



This has worked until recently, when I started getting an error message when I tried to access the drive (by double-clicking the disconnected drive in Explorer). The message reads:



An error occurred while reconnecting S: to
https://sharepoint.mycompany.com/sites/1234
Web Client Network: The network path was not found.

This connection has not been restored.


I have tried removing and re-mapping one of the two drives, which fails with the message:



Error code: 0x80070043
The network name cannot be found.


I can still open the URL in my web browser (indicating the site is available and name resolution works).



OS is Windows 7. The Web Client service is running (started manually). I have added the SharePoint site to the Trusted Sites zone in Internet Explorer.



What gives?










share|improve this question






















  • I'm voting to close this question as off-topic because issues specific to corporate IT support and networks are off topic, see On-Topic. Please talk to your IT department.
    – DavidPostill
    Nov 22 at 20:44










  • I’d say this is a generic question: What settings need to be in place on the client and the SharePoint server in order for drive mapping to work, and what change to a once working setup would cause the aforementioned malfunction?
    – user149408
    Nov 23 at 11:41










  • For the record, I was finally able to map the site as \sharepoint.mycompany.com@SSLDavWWWRootsites1234 (note the extra DavWWWRoot in the path).
    – user149408
    Nov 23 at 12:03













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have in the past accessed two SharePoint sites on our company network by mapping them as network drives. That is, I have added a network drive in File Explorer to a URL of the form



https://sharepoint.mycompany.com/sites/1234


I work mostly via VPN, so on login the drives show as disconnected. Upon opening the drive for the first time per session, the connection would get established and I was able to browse the site contents.



This has worked until recently, when I started getting an error message when I tried to access the drive (by double-clicking the disconnected drive in Explorer). The message reads:



An error occurred while reconnecting S: to
https://sharepoint.mycompany.com/sites/1234
Web Client Network: The network path was not found.

This connection has not been restored.


I have tried removing and re-mapping one of the two drives, which fails with the message:



Error code: 0x80070043
The network name cannot be found.


I can still open the URL in my web browser (indicating the site is available and name resolution works).



OS is Windows 7. The Web Client service is running (started manually). I have added the SharePoint site to the Trusted Sites zone in Internet Explorer.



What gives?










share|improve this question













I have in the past accessed two SharePoint sites on our company network by mapping them as network drives. That is, I have added a network drive in File Explorer to a URL of the form



https://sharepoint.mycompany.com/sites/1234


I work mostly via VPN, so on login the drives show as disconnected. Upon opening the drive for the first time per session, the connection would get established and I was able to browse the site contents.



This has worked until recently, when I started getting an error message when I tried to access the drive (by double-clicking the disconnected drive in Explorer). The message reads:



An error occurred while reconnecting S: to
https://sharepoint.mycompany.com/sites/1234
Web Client Network: The network path was not found.

This connection has not been restored.


I have tried removing and re-mapping one of the two drives, which fails with the message:



Error code: 0x80070043
The network name cannot be found.


I can still open the URL in my web browser (indicating the site is available and name resolution works).



OS is Windows 7. The Web Client service is running (started manually). I have added the SharePoint site to the Trusted Sites zone in Internet Explorer.



What gives?







windows-7 sharepoint network-drive






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 at 17:23









user149408

5781417




5781417












  • I'm voting to close this question as off-topic because issues specific to corporate IT support and networks are off topic, see On-Topic. Please talk to your IT department.
    – DavidPostill
    Nov 22 at 20:44










  • I’d say this is a generic question: What settings need to be in place on the client and the SharePoint server in order for drive mapping to work, and what change to a once working setup would cause the aforementioned malfunction?
    – user149408
    Nov 23 at 11:41










  • For the record, I was finally able to map the site as \sharepoint.mycompany.com@SSLDavWWWRootsites1234 (note the extra DavWWWRoot in the path).
    – user149408
    Nov 23 at 12:03


















  • I'm voting to close this question as off-topic because issues specific to corporate IT support and networks are off topic, see On-Topic. Please talk to your IT department.
    – DavidPostill
    Nov 22 at 20:44










  • I’d say this is a generic question: What settings need to be in place on the client and the SharePoint server in order for drive mapping to work, and what change to a once working setup would cause the aforementioned malfunction?
    – user149408
    Nov 23 at 11:41










  • For the record, I was finally able to map the site as \sharepoint.mycompany.com@SSLDavWWWRootsites1234 (note the extra DavWWWRoot in the path).
    – user149408
    Nov 23 at 12:03
















I'm voting to close this question as off-topic because issues specific to corporate IT support and networks are off topic, see On-Topic. Please talk to your IT department.
– DavidPostill
Nov 22 at 20:44




I'm voting to close this question as off-topic because issues specific to corporate IT support and networks are off topic, see On-Topic. Please talk to your IT department.
– DavidPostill
Nov 22 at 20:44












I’d say this is a generic question: What settings need to be in place on the client and the SharePoint server in order for drive mapping to work, and what change to a once working setup would cause the aforementioned malfunction?
– user149408
Nov 23 at 11:41




I’d say this is a generic question: What settings need to be in place on the client and the SharePoint server in order for drive mapping to work, and what change to a once working setup would cause the aforementioned malfunction?
– user149408
Nov 23 at 11:41












For the record, I was finally able to map the site as \sharepoint.mycompany.com@SSLDavWWWRootsites1234 (note the extra DavWWWRoot in the path).
– user149408
Nov 23 at 12:03




For the record, I was finally able to map the site as \sharepoint.mycompany.com@SSLDavWWWRootsites1234 (note the extra DavWWWRoot in the path).
– user149408
Nov 23 at 12:03















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377638%2fsharepoint-mapped-as-network-drive-no-longer-works%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377638%2fsharepoint-mapped-as-network-drive-no-longer-works%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕