Web Hosting Talk : Web Hosting Main Forums : Dedicated Server : Learn to configure windows 2003 into a web server?

[factorx]

I'm about to get my windows 2003 deticated server and i need to know how to make it into a web server. It is unmanaged so that is why i need to learn how to. My site will run off mySQl. Please post any links that show you how to do this and secure your windows server. There is nothing in Dedicated Server Tutorials. thanks

[dkitchen]

It's pretty simple, install IIS, change a few settings, install MySQL and you're done. Configure your firewall, install some antivirus, run Windows Update, and you're done really.

If you're in doubt about the security of your box always consult someone who really knows what they're doing ...

[factorx]

i know this might been dumb but where do u get IIS from

[MrKurt]

It's on the Win2k3 CD. There should be a one click option from "Manage Your Server" in the start menu (or Administrative Tools) to turn it into a Web server.

Before you do anything, though, make sure Service Pack 1 is installed and the firewall is enabled.

[Defcon|Rich]

You might need the I386 directory to install some components. Have your server provider put a copy of the files on your machine for you if they aren't there already.

[Hudson Digital]

Start > Settings > Control Panel > Add or Remove Programs > Add/Remove Windows Components > Applications Server > Details

[dkitchen]

Originally posted by factorx
i know this might been dumb but where do u get IIS from

No offence, but if you don't know this, you really need someone to get your server secured down, etc.

[HiVelocity]

Originally posted by RazorBlue - Dan
No offence, but if you don't know this, you really need someone to get your server secured down, etc.

Don't most providers secure the box before they put it on the network , that would be a huge security risk for a network , I know we do this on every box that we install. Cuts down on reloads and other stuff that is a total pain in the butt for a provider.

[dkitchen]

They're secured to the point that you can't get in, but once you install services such as a control panel, IIS, etc, etc you're opening potential security holes, and this is where you need to make sure all your permissions are set correctly, and unwanted traffic is blocked.

One thing tons of people seem to forget is AntiVirus, all someone needs to do is upload an infected EXE, and your server is messed up.

[RayWomack]

Originally posted by RazorBlue - Dan
all someone needs to do is upload an infected EXE, and your server is messed up.

WRONG, WRONG, WRONG WRONG WRONG.

This common misconception drives me NUTS. An exceutable cannot infect your machine by FTP'ing to the wwwroot/ under "normal" or "default" permissions.

[RayWomack]

Originally posted by HiVelocity
Don't most providers secure the box before they put it on the network , that would be a huge security risk for a network , I know we do this on every box that we install. Cuts down on reloads and other stuff that is a total pain in the butt for a provider.

Windows Server 2003 is installed in a "secure" manner, anyway. And any provider should provide SP1 and aplicable patches. This goes without saying.

The "securing" that the poster is talking about has nothing to do with how you deliver a server. Its the exploitations in applications that need securing.

There are people that make a fine living securing servers. I doubt that an ISP delivered box that is considered "secured" is what this subject is about.

[Take-IT-EZZI]

ANY provider who supplies Windows will install the OS and all critical updates before handing it off to the customer, and by default Windows 2003 is pretty much secure at that point. Just about any provider is going to copy the i386 folder over too, look for C:\i386 or C:\WindowsCD or something

But after you install IIS, it's by default not going to allow certain types of files to be downloaded, and certain types of scripts to be run, this is where people often open themselves up to disaster. Don't just indescriminently change permissions and allow scripts to be run, know what you need, and enable what you need for the sites you need them for.

There is lots of documentation out on the net for IIS, do some reading, there is also a forum dedicated to IIS with some experts on it. http://www.iis-resources.com They have been helpful to me in the past.

The Microsoft Baseline Security Analyzer is another good tool for checking best practices.