1. Open the Windows firewall settings
2. Click the Advanced tab
3. Click the top settings button
4. Check the box that says FTP Server
5. Click OK
6. Click OK

That should work then.

Related posts:

1. How to (Successfully) Install Cisco VPN Client on Windows 7 I’ve been having trouble connecting to h365 using the cisco...

Related posts brought to you by Yet Another Related Posts Plugin.

Right, I’m going to assume that you are nothing like me and actually went searching for an article like this before you dived in head first. Either that or you are making use of the restore function and shock and horror its actually working.  I recommend you follow this to the letter, I’m not going to try it a couple of different ways because I have neither the time nor inclination, the first time everything worked I breathed a sigh of relief and returned to some work that actually makes money.

First off you’ll want to install MSSQL, you’ll need x64 version. You’ll need to go into iis and on your default ftp site enable writing to the home directory before you can upload the installation files. Make sure you upload both the server and the tools into the ftp site, I’d recommend zipping them beforehand and I’d recommend using 7z to do it. It has an x64 version, its free and its on sourceforge. So once you have the two folders on the server sitting side by side called SERVERS and TOOLS then you need to download the native client from the following URL: http://www.microsoft.com/Downloads/details.aspx?familyid=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en, put it in the same directory. So that you have SERVERS TOOLS and the native client exe all sitting in the same folder. Click on the native client exe and install it. Then you can click on the setup in SERVERS, install everything bar reporting services which won’t install because you are running 32 bit IIS on x64 windows. Yes there is a way around reporting services breaking by preventing 32 bit from running as x64 but that will break plesk and probably other stuff.

Next you’ll want to install .net. There are two ways you can do that, either you download the stand alone installer from microsoft.com or you use windows update. Now if you have delved a little into the machine you’ll have discovered windows update is disabled. This is because Blacknight handles all the updates themselves (apparently). To start windows update you will have to go to the start menu, click run, type services.msc and hit enter.
Right click on automatic updates, set to automatic, click apply, click start then ok. Right click on Background Intelligent Transfer Service, do the same. Open your browser, go to http://update.microsoft.com You don’t need IE 7, so select the other priority update option and clear selection. Then go to optional updates and install 3.5.

Next you want to tell plesk to add your www subdomain when you add a domain.
Do the following:

To set this up automatically for any new domains you add to your Windows Plesk VPS go to (in Plesk):
# Server >> DNS Settings >> Add new record
# The record you are adding has to have the following details:
Record Type: CNAME
Domain name: www
Canonical name: <domain>

Next go to the blacknight domain control panel and add your domain using Plesk as hosting. Once that is complete you should have the domain listed in plesk. You’ll need to add physical hosting for it. I’m not going to tell you how to do that but you will probably notice that you aren’t able to run .net 3.5 apps yet. You’ll need to do the following to get that working on whatever site you have.

To change over an IIS website (even if you created it in Plesk you are going to have to follow the following instructions)

Firstly you will need to find what folder the version of .net you want to use is located and you will need to know what number IIS has assigned the domain you want to change.

For example if you wanted to set up .net 2.0 and configure a domain to use it the folder is most likely the following (though you will need to verify):
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

If you look up the domain in IIS Manager you should see what number it is using*

Once you have confirmed the directory you can open a command prompt in Windows:
Start >> run >> type in ‘cmd’ and press enter

In here you can change to the directory in question:
cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

If you run the following command you can see the different vhosts (domains) on the server and what version of .net they currently have installed:
aspnet_regiis /lk

A sample output of this would be (please see below for how to tie these numbers to a domain name*):
W3SVC/14382/ROOT/ 1.1.4322.573
W3SVC/17058/ROOT/ 1.1.4322.573
W3SVC/17090/ROOT/ 1.1.4322.573
W3SVC/17123/ROOT/ 1.1.4322.573

To add .net 2.0 to a vhost we run:
aspnet_regiis /sn *vhost*

where *vhost* is the vhost name taken from the above results.

For example to set W3SVC/17058/ROOT/ to .net 2.0 we do:
default path> cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
then:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727> aspnet_regiis /sn W3SVC/17058/ROOT

If you run the ‘aspnet_regiis /lk’ command again it will look something like this:
W3SVC/14382/ROOT/ 1.1.4322.573
W3SVC/17058/ROOT/ 2.0.50727.0
W3SVC/17090/ROOT/ 1.1.4322.573
W3SVC/17123/ROOT/ 1.1.4322.573

*You can find out what the number between W3SVC and ROOT is through the IIS Manager on the server.

Hope it all works out for you.

Related posts:

1. How to (Successfully) Install Cisco VPN Client on Windows 7 I’ve been having trouble connecting to h365 using the cisco...
2. Handling Relative Paths and debug mode with Jquery in ASP.Net Web Forms I had a problem where I wanted to use the...

Related posts brought to you by Yet Another Related Posts Plugin.