I recently migrated a webserver using windows server 2000 and IIs 5.0 to a
new machine with windows server 2003 sp1 and IIs 6.0. The new server is now
part of a new active directory domain, the old one was in a workgroup. This
server is for a local isp and it hosts 10 web domains. The isp has it's own
web domain and this isp offers internet users free webspace on their site.
The previous setup utilized virtual directories under their domain for both
displaying the personal web sites and ftp access. Since they were using IIs
5.0, they did not utilize user isolation. Instead they placed the user
folders in a different directory and setup local users on the webserver for
ftp access. Everything is working very well, except for the ftp virtual
directories. The website virtual directories are viewable on the internet,
but users are not able to login to their personal websites. I have setup the
same local users that were setup on the old webserver. I have tried using
user isolation with folders under the website's directory and I have tried
using it without user isolation in a different directory, but every time I
try to log into a ftp site that is using a virtual directory, I get an event
in the webservers system event log" event id 13 from source MSFTPSVC, user
"whoever I try" failed to log on, could not access the home directory /. I
went as far as to share the folder out for one user, and ran a unc path over
the internet and was able to connect fine using the user's credentials, yet I
cannot connect through ftp, either from a command line or internet explorer
of an ftp client. The users in question, do have the logon locally
permission. I have followed every doc I could find from Microsoft and still
no luck. Do I need to create a/d users in the local domain?? I have no idea
what is wrong. One thing I did note was that on the old webserver(IIs 5.0),
there was no default ftp site, it appears that they simply renamed and
configured it to be the isp's ftp site. On the new webserver, I didn't use
the default ftp site and since it defaulted to all available ip addresses and
would cause all of the other sites to stop. The webserver has all of the ip
addresses for the websites in the nic properties and each site is assigned
