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

Intodns.com dnscolos.com Those two sites will give you insite to your DNS problems. On your domain registrar I'm guessing you are pointing your domain to your name servers ns1.example.com and ns2.example.com located at your static IP. If you are planning on hosting your web server on the same static IP as your DNS then you will need to setup port forwarding on your router for port 53 (dns) to the internal ip of your domain controller (which will handle the DNS entries for ns1 and ns2). Then setup port forwarding for 80/443 (http/https) to the internal IP of your web server. You really should have multiple static IPs having one for your domain controller handling DNS and a separate IP for your web server. Hope that makes sense good luck!

Are you trying to use your server to lease DHCP? Your client computers aren't getting an IP because you disabled DHCP on your router that would normally lease IPs and you haven't specified a static IP for your clients. It seems to me that you would want to enable DHCP on your router to lease IPs to wireless clients and keep the server on a static IP. If you want to use Active Directory on your Domain Controller with your clients then set the clients Primary DNS to the IP of your server.

In cmd if you run ipconfig your not getting the IP address that you set on the interface? Are you sure the static IP you're assigning on the server is valid for your network?

Hi, I use Windows Server 2008 for web hosting/active directory and CentOS for email. Specifically postfix as my smtp server and dovecot for pop3s/imaps. I want the ability to use my CentOS box as my smtp server for Windows Server 2008... unfortunately it has been difficult to find a whole lot of information on this. To give a little more information I want the ability to use the PHP mail function in IIS to send mail from an account on my smtp server. My smtp server requires SSL and user authentication. Any suggestions? Thanks!

Custom build running XenServer for virtualization: Intel Xeon Westmere 2.4ghz Quad Core CPU Asus Z8NA-D6 Mobo 12GB Patriot DDR3-1333 Registered Memory Areca 1210 PCIe-8x RAID Controller with 256MB cache 4x Western Digital 1TB 7200rpm 3.0GBs Enterprise HDDs in a RAID 10 480 watt PSU 4U Rack Case

Wooo! Got everything working!!! In regards to the 3 DNS entries coming back by themselves what was happening was I had one DNS entry for my public static IP of web server, then the other two entries were coming from my network interfaces on my internal and external domain controllers. To fix the problem I had to goto: Network adapters > right click interface and properties > click IPv4 and toto properties > advanced > DNS tab > uncheck "Register this connection's addresses in DNS" I also added the following registry key: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/Tcpip/RegistrationEnabled type DWORD value 0 Now my network interfaces don't come back after deleting them. Appreciate everything, couldn't have got to where I am on this without your help! As for the split DNS setup it doesn't seem to be working exactly as I expected... Whenever I change the IP on either my internal or external DC it duplicates on the other, so right now both DCs are using my external static IP which works, although I thought the purpose of splitting the DNS was to allow the internal DCs DNS to point to my internal static IP and likewise for my external. Any thoughts?

Well it seems to be responding now in DMZ. The only thing I changed was the DNS servers listed on my modem to use OpenDNS instead of my ISPs DNS. I don't see how this would affect anything so maybe the DNS servers just needed a few days for the cache to clear? On my external DC there are three A entries for mydomain.com (one pointing to internal DC, one pointing to external DC, and one pointing to my web servers public IP (as it should be)). If I delete the other two IPs (other than public) they come back automatically after some time. As a result of pinging mydomain.com sometimes it works fine and gives my the public IP while other times (hours later) it returns a private IP. Whats up with that?

I tried browsing to that IP along with yahoo.com and a few other sites with no success. Surprisingly the only site I was able to browse to was my web server IP #3. I was able to get to the default IIS site. On a side note I also decided to scan the ports with nmap for IP #2. Running nmap without any parameters indicates that the host is down however if I use the Pn parameter (treating the host as online) I am able verify that the correct ports are open.

tracert worked fine. The first IP in the trace is my routers gateway 192.168.1.1 and the second IP my ISP gateway. I tried turning off my firewall on the router (although being its in DMZ it's not behind the routers firewall anyways right?) and checked windows firewall it appears correct having rules to allow port 53. I went ahead and turned off the windows firewall as well and restarted. After I was still unable to browse and the intodns report was the same. I did a test of putting my web server into DMZ as well on IP #3 and got a similar result being unable to browse on the VM however I was still able to see the IIS default page when browsing to IP #3 directly. Any other ideas or tools I can use to troubleshoot what's going on?

Hi, I've been working on setting up a server at home and am running into some issues resolving DNS for my site. Im running windows server 2008 and have a split DNS setup. I have a DrayTek Vigor 2920n with 5 static IPs. Network config: - Internal Domain Controller - External Domain Controller - Read-Only external Domain Controller in DMZ on IP #2 - IIS Web Server on IP #3 with port forwarding for 80/443 All is working except DNS resolution. intodns.com reports that my RODC on IP #2 didn't respond (contains DNS entries for ns1 and ns2 for mydomain.com). I can ping IP #2 succesfully. If I get on the RODC VM I can ping out but can't browse (at first I couldn't even ping out but enabling recursion on the external DC fixed that). It seems strange that I can ping but not browse. If I take the RODC out of the DMZ I am able to browse. I suspect that when browsing in the DMZ perhaps the identified IP is IP #1 instead of IP #2 and the response is not able to find its way back? I'm really at a loss as to what could be going on. All help is appriciated!