Dns, Http, Ftp

[wigoweb]

Hello,

 

I am working for a web site client that I hope to convert to a hosting client as well. However, right now I need to solve a dilemma with the current host.

 

The client had a hosting set up which allowed only one ftp account. In order to have multiple ftp accounts, the host moved the client to a different server and changed the DNS. Everything seemed to work.

 

After a few days, we noticed some anomalies in that pages we posted via ftp in DreamWeaver were not showing up in Explorer.

 

We dug a little using Fetch and discovered the following:

 

If we ftp into example.com with the login joe and password go, our destination path is this:

 

/.users/32/joe/web/

 

If we http with my browser and go to **** or to www.****, our destination path is this:

 

/web

 

/web is at the same level as /users which is several layers about /joe/web/

 

My question is this. Are there separate DNS settings for http and ftp? Could the hosting company have reset DNS for one protocol but not the other?

 

If that is not possible, any ideas on what might be causing this to occur?

 

We set up several accounts so that different departments could edit their own web pages without having access to other department's pages.

[wigoweb]

This is a follow-up to my earlier posting.

 

I finally determined that I needed to put information in the Host Directory field on the Remote settings page for DreamWeaver. Usually, I just leave this blank and all works as expected. This time it didn't work out that way. The directions in DreamWeaver help suggest that one leave the field blank and see if it works.

 

By adding the root folder /web/ on the Remote Info page, my main user can now log in and post to the correct set of folders so that the pages are visible via http and a browser.

 

However, we still haven't determined what to do about the second user who owns a folder inside the main site. Our attempts to ftp to that account all go to a folder inside the /users path instead of out at the root level and into the /web path.

 

I have had several emails and a phone conversation with the tech support people at the client's host. They are working on it since it appears that the rights for the subordinate account weren't set up as we had anticipated.

 

For part of the solution, though, that Host Directory field in DreamWeaver provided the fix.

 

Hope this is helpful to someone else.