I've been given access to a WAMP Server (Windows Server 2003) by two different methods:
1) FTP
2) Remote Desktop Protocol (RDP)

The FTP config seems really wrong. When I login, The files I see appear to have nothing at all to do with the actual htdocs folder of the web server. I'm still trying to figure out what that gives me access to.

I can login using remote desktop protocol and browse the entire computer, but in order to publish files to it, I have to
switch to the Remote Desktop Client
manually drag/drop or copy/paste changed files from my local shared hard drives to the server
look at results in a browser
minimize RDP client and return to IDE running on my local machine to make more changes
* repeat

This workflow totally sucks. Is there any way I can have visibility to the remote machine as a mapped network drive or something so I can save directly to the remote machine and dispense with the RDP client?

Any help would be much appreciated.

    If you are on the same private network, not connecting across the internet, you can share the htdocs folder
    If you connect across the public internet without a VPN I would not share the folder.

    If you are not the administrator of this server get the administrators OK to create a share.
    To create the share:

    • RDP to the server

    • Right click on the htdocs folder

    • Select sharing and security

    • Click the radio button for “share this folder”

    • The default share name is the folder name if you want to change it type the share name you want in the “share name” box

    • Click on the permissions button, this brings up share permissions

    • Remove the “everyone” user

    • Click add and follow the dialog to add your user account or group you are a member of to the permissions list

    • With your username or group highlighted check the full control box

    • Click apply or OK

    The folder should be shared

    You probably don’t need to adjust the file system permissions.

    Next map your drive:
    Open a command prompt (cmd)
    Net use x: \servername\sharename

    To Fix the FTP issue:
    If you are not the administrator of this server get the administrators OK before changing FTP settings:

    • Open the IIS manger
      Start->all programs->administrative tools-> Internet Information Services (IIS) Manager

    • Browse to the FTP sites
      Click the + signs on the server name and FTP sites

    • You will see the default FTP site or whatever site you have setup

    • Click with the right mouse button on the FTP site and select properties

    • Click on the home directory tab

    • On the home directory tab you will see the local path box showing where the FTP root is

    • If you are the only one using the FTP on this server you should be able to change it the htdocs folder using the browse button

    • If FTP is used by other people or things don’t change it!

      you rock!

      Is that first series of steps going to work if I'm connecting over the internet or is it potentially a hazardous security risk? I literally am connecting to some IP address that's out there on the internet.

      Also, does removing the everyone user affect the file system at large or just this particular item?

      I managed to figure out the FTP solution and that is to add a 'virtual directory' to the default FTP site. Works like a charm.

        Is that first series of steps going to work if I'm connecting over the Internet or is it potentially a hazardous security risk? I literally am connecting to some IP address that's out there on the Internet.

        It is possible to connect to a share directly across the Internet but it is a BIG security hazard. Hopefully file sharing is blocked at their router.
        If you use a VPN to connect to their network you are OK

        does removing the everyone user affect the file system at large or just this particular item?

        It will only affect the share permissions, anyone connecting to the share across the network. If you leave "everyone" in place anyone with windows or SMB can connect to the share. They also have to get past the file system permissions.
        As a rule I always remove everyone from the share permissions and assign it to the group that needs the share like "Domain users".

        I am glad FTP is working!

          Write a Reply...