The Challenge of Copying Files to a Network Place from a Command Line

If you’re using Windows XP and find yourself in a situation where you need to copy files to a Network Place using a script or the command line, you may be in for a challenge. This scenario often arises when trying to publish files to a specific document library connected to services like WSS 3.0 (Windows SharePoint Services). Unfortunately, directly accessing or manipulating a Network Place through the command line isn’t straightforward as you might hope. Let’s explore this problem in detail and discuss potential solutions.

Problem Overview

When trying to publish files from a user’s machine to a WSS 3.0 document library:

  1. Restrictions: The WSS site only allows authentication via NTLM and is hosted on a port that is neither 80 nor 443.
  2. Drive Mapping Limitations: Direct drive mapping to the library may not be possible due to the inability of tools like the net use command or PowerShell to specify port numbers in the destination path.

Exploring the Solution

While accessing a Network Place directly from command line tools has its limitations, here are some potential workarounds you might consider:

1. Use of WebDAV

Since the underlying challenge is to perform file operations over HTTP, one solution to consider is utilizing WebDAV clients. These clients allow for drive mapping over non-standard ports. A popular option is WebDrive, which enables drive mapping via WebDAV for sites that operate outside the usual HTTP ports.

  • Pros:

    • Simplifies the access to the document library by mapping it as a drive.
    • Allows you to manage files directly from Windows Explorer.
  • Cons:

    • It typically requires purchasing or licensing the software.

2. SharePoint Configuration Changes

Alternatively, you can adjust your SharePoint configuration:

  • Separate Web Application: Create a separate web application that runs on a standard port, thus avoiding the limitation of the current setup.
  • Host Headers: Set up host headers to expose the site correctly, allowing normal NTLM authentication.

3. Utilize SharePoint Web Services

If the above options don’t suit your needs, consider using SharePoint web services to push files directly to the library. This involves more programming overhead but gives you finer control over file uploads.

  • Requires familiarity: You will need to understand how to interact with SOAP web services and manage authentication via code.

Conclusion

While copying files to a Network Place using a script or command line in Windows XP presents its challenges, particularly in terms of authentication and port specification, there are solutions available. Utilizing tools like WebDrive, adjusting your SharePoint settings, or employing SharePoint web services can significantly ease the process.

In summary, while direct command line interactions may not be possible, there are several pathways to achieve your goal of publishing files to a WSS document library effectively.

If you have any questions or need further guidance on specific steps, feel free to reach out or leave a comment!