>> I got Filezilla on there running as a service but my FTP client software could not connect, probably because I was unsure of the settings.
probably you hadn't added the program as an exception to the firewall. that's the thing I forgot straight after installing. ditto the web server. Under Windows 2008 the firewall doesn't prompt you to unblock unless you ask it to.
>> So, just to clarify, if I keep IIS running, presumably it does not matter so what port do I use?
if you keep IIS running then it is "using up" port 80. You can use any other port you like for your app, but then the url to use the site has to include the port number.
>> Scared silly about uninstalling IIS as there was so much hassle in the first place and with an unmanaged account it is worrying.
Given that you're clearly not an IIS expert (neither am I) you have no idea what ancillary effects IIS will have on your machine other than just consuming ram and cpu cycles. You will need to be responsible for keeping it updated, and managing the security issues created by leaving it there. It being an "unmanaged account" has nothing to do with it. This is "your machine" you can do anything you like on it. Don't be relying on Rackspace techs to do stuff for you. It's not hard to set up a server, it just takes a bit of effort and googling. It's by far _not_ the simplest server to configure, especially for FTP.
>> Or do I follow the instructions I came across on another thread whereby IIS can be reconfigured to listen on another port or something?
sure that's an approach. Then you just need to worry about long-term ram and cpu usage, and security issues. Honestly, setting up an FTP server like Filezilla is too easy to be messing around with IIS.
cheers
Bruce