koga73

Oh ok I see now. IIS doesn't really work that way... Typically you wouldn't nest websites where you have site1 and site2 that is in the directory of site1. If you are going to do something like this then you would want to convert site2 to an application... But this still won't allow you to setup separate FTP sites. This also explains why you are unable to add users for site2 since site2 is in site1 it makes sense that site1s user rules are affecting site2. I think a smarter way to set this up is with subdomains. Instead of having site2 inside site1 have site1 and site2 in separate directories in the wwwroot. Then instead of using site1.com/forums you can setup a subdomain for forums.site1.com. This will allow you to setup a separate FTP for each.

Strange. Let me get this straight, you have FTP setup for both your default site and forum site correct? Each site has its own directory in the wwwroot directory? So... --wwwroot ----site1 ----site2 Is that how you are configured?

Are you running IIS on Windows Server 2008 or Windows 7? Either way you shouldn't need a Domain Controller to get the FTP working... although I'm not really sure what your problem is exactly. When I setup FTP in IIS it was pretty straight forward but my server running IIS is tied to a Domain Controller as well. I think the problem your having stems from your user accounts. This is different for me because my windows accounts are handled through Active Directory on my Domain Controller.

You have a domain controller as well correct? If so if you look at your users you can go into the properties for a user and set an email address. If I were you I would remove all user rules from the IIS root node and sites then add the administrator account as an allowed user to the FTP site your trying to get working. Once you are able to login then add other users.

Does the user your trying to login as have an associated email? Ive found that putting only the username doesn't work. You have to specify an email address or the windows domain\username. Are you able to login to the domain using the administrator account?

When you add an FTP site there is a checkbox that allows you to enable a virtual host name. Make this the same as your domain name. http://learn.iis.net/page.aspx/320/using-ftp-virtual-host-names-in-iis-7/ No idea about your Facebook problem... Facebook sucks anyways don't use it.

If your not already using FTP virtual hosts you should. With IIS 7 Microsoft changed how FTP works for multiple domains. Using virtual hosts you pass the domain along in the username for FTP login. For instance if I have the following domains on the same server: site1.com site2.com You enable a virtual hostname for site2.com after setting up ftp for site1.com. Then to login you point your FTP to: [serverIP hosting both sites] User: site2.com|user@domain.com Pass: ******* So the username becomes "{VIRTUAL_HOST}|{ACCOUNT}" Hope that helps.

I have my data range set to 5000-5100 and have an inbound firewall rule that requires a secure connection for TCP local and remote ports 5000-5100. Besides that I have the windows default firewall rules that are created when you install the FTP service.

The part your missing is where you are actually setting your DNS entry to point to your web server. Microsoft didn't make this very clear because I struggled with the same issue. You need to create a new A host entry pointing to your web servers public static IP. Leave the first field blank so that your entry has "(same as parent folder)" type "A Host" pointing to "Public Static IP". If your trying to host your web server on the same instance of Windows Server 2008 as your DNS server you may run into problems. I had to use separate virtual machines with one acting as a DC and DNS and a separate to run IIS.

If you don't have a static IP then use Dynamic DNS. Dynamic DNS will allow you to use a URL such as username.dyndns.org to point to a dynamic IP. You just need to configure your network or server to update your Dynamic DNS account with its IP whenever it changes.

Your getting a 403 because you are trying to browse a directory or access a file that doesn't have permissions for annonomous users. Right click the file or folder and go to properties and adjust the permissions as you see fit.

Sounds like not everything in your page requires SSL. If you are using https then all imports within the page that contain absolute URLs must also be https. This includes any JavaScript imports, CSS files, etc that your page is pulling in. Currently you are using a secure connection but pulling in unsecure files in your page that's why your browser is giving you the warning.

If your JavaScript is in an external file make sure that your web page is pointing to the correct URL and make sure that the permissions at that URL are set so anyone can access it. Make sure JavaScript is enabled in your clients browser. Make sure that your IIS configuration includes a *.js mime type so your server knows how to correctly serve the JavaScript file to clients. A great program for debugging web sites is Charles. http://charlesproxy.com

If you are using FTP with port forwarding / network address translation then you need to set your FTP firewall support settings in IIS. When accessing FTP via passive mode the server responds with a port and ip address for the client to connect to. You need to set the data port range and the ip to your public static ip. You also need to open your firewall to the data port range. This should fix your problems.

Just add the 4 DNS IPs as Forwarders to your DNS then change the client machines DNS to yours