On another machine, same network, also Windows 7, same web client settings, I could not get it working. I could engage Explorer View from the SharePoint web site, or from Network in Explorer, and it just worked. One Windows 7 machine cheerfully opened the Explorer view to a remote site on port 444. Windows 7 is better, though I experienced an odd issue. It does not apply to Windows 7 though.Ī good resource on the repeated login issue is here. It is necessary on Windows 2003 since the web client is not installed by default. In addition, many XP and even Vista users find this update essential before anything starts working. Apparently Microsoft has no intention of fixing this. You are stuck with the FrontPage view, which is less useful. This white paper on Understanding and Troubleshooting the SharePoint Explorer View is essential reading.įrom this you will discover that if you are using Windows XP, the WebDav SharePoint Explorer view will not work over SSL or on any port other than 80. However, achieving this is notoriously troublesome, raising uninformative messages such as “Your client does not support opening this list with Windows Explorer", or from the command line System Error 67, or System Error 53 “The network path was not found”.Īnother common complaint is incessant login dialogs. It’s the second of these that you most likely want. If you have looked into this, you will know that there are really two Explorer Views, one using Internet Explorer and ancient FrontPage protocols, and the other using WebDav and Explorer. Troubleshooting though is a world of pain. Sounds great and when it works, it is great. Now you can browse documents without a web browser, and upload directly to a web application. SharePoint Explorer View lets you access documents through Windows Explorer you can even map SharePoint as a network drive. The workaround is to save the document out of SharePoint to the local drive, then upload it.įortunately there is another option. This is straightforward if the document is on a local hard drive or network share, but not if it is in SharePoint. Their company uses a web application that frequently requires documents to be uploaded. A user recently highlighted another issue. That said, it is inconvenient to run up the browser and navigate to a web site whenever you want a document. SharePoint is a mixed bag of course, but once it is up and running the browser user interface seems reliable as a means of getting at your documents over the internet. VPN is heavy on bandwidth and not great for security, so SharePoint seems the obvious solution. Thanks to Mike for this detailed tutorial.Many of us want access to our documents from anywhere these days, and if you are still storing documents on a Windows server then remote access to documents usually means either VPN or SharePoint. Now the network drive will be connected and you can see the drive in Window Explorer. It will prompt you to enter the Windows Live credentials after attempting to connect to Skydrive. In the Map Network Drive option, enter the folder as You can also chose to reconnect at Login and if you want to connect using multiple account, check the second box as well.ĥ. Open Windows Explorer, right click on the Network and select Map Network Drive.Ĥ. Modified URL- are connecting using the SSL for Windows Live Skydrive.ģ. Next step you need to make some modification to the URL. The sub domain cdckda refers to the your account and the folder you are trying to access.Ģ. Here the sdfsd24645759 refers to the path which is the same as a personal sub domain when logging on to SkyDrive the normal way from your web browser. In the image above, you can see an address corresponding to the folder I have selected.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |