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?
windows-7 sharepoint network-drive
add a comment |
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?
windows-7 sharepoint network-drive
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 extraDavWWWRoot
in the path).
– user149408
Nov 23 at 12:03
add a comment |
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?
windows-7 sharepoint network-drive
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
windows-7 sharepoint network-drive
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 extraDavWWWRoot
in the path).
– user149408
Nov 23 at 12:03
add a comment |
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 extraDavWWWRoot
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
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1377638%2fsharepoint-mapped-as-network-drive-no-longer-works%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
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 extraDavWWWRoot
in the path).– user149408
Nov 23 at 12:03