• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Any suggestions for webserver for Win2000?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
It seems to me that neither is secure, in this case.... as likely neither would likely be setup properly to start, given the no-experience issue.



 

You'll find a lot of zealots giving you answers to this.

Use IIS. If you have an NT/2000/xp box you can have it up and running for free in about 5 minutes. It supports frontpage extensions....click once to publish is what you are after here correct?

Go to the microsoft website, get the IIS lockdown tool and security checklist. You'll patch and whatnot for about another 5 minutes and you're done.

WHEN PROPERLY PATCHED IIS is pretty secure....you don't patch it up and you're in deep trouble though 🙂

Nothing wrong with Apache...it's great for larger sites and quite secure.

 
Originally posted by: Smilin
You'll find a lot of zealots giving you answers to this.

Use IIS. If you have an NT/2000/xp box you can have it up and running for free in about 5 minutes. It supports frontpage extensions....click once to publish is what you are after here correct?

Go to the microsoft website, get the IIS lockdown tool and security checklist. You'll patch and whatnot for about another 5 minutes and you're done.

WHEN PROPERLY PATCHED IIS is pretty secure....you don't patch it up and you're in deep trouble though 🙂

Nothing wrong with Apache...it's great for larger sites and quite secure.
yes, let's quit arguing about pointless things. IIS should be just fine for what your doing, just make sure that "write" access is not enabled and download the latest updates.

Have fun
-Spy
 
and just for you hardcore Apache fans out there dont worry, I believe that Apache can beat IIS hands down for the features that the 2 server software packages support (primarily xfuing http). But let's be realistic here, for what he's doing (hosting his resume) and the features he wants (like frontpage extensions) IIS is the easiest way to go.

-Spy
 
A heavily patch IIS would be okay. Apache is also very good. It's not quite as difficult as you might imagine for the basic stuff. The cool thing is that you can learn as you go which is how real learning happens. 🙂

 
Originally posted by: N11
Originally posted by: n0cmonkey
Raven76

On that note, Ill change my answer. Setup IIS. But do it on Linux.

That would be an act of heresy.

Yeah, but it would be funny. 😛


The main reason I recomment apache on a Windows platform is security and ease of use. Why bother fiddling with IIS when you can setup apache in 8-10 seconds (after download/install)? Why have to download update after update after update after update only to get cracked on the one you happen to miss at 3:30am after it was pulled off the Microsoft webpage because it didnt actually fix the problem (just the symptoms) and ended up causing other problems?

🙂
 
Originally posted by: n0cmonkey
Originally posted by: N11
Originally posted by: n0cmonkey
Raven76

On that note, Ill change my answer. Setup IIS. But do it on Linux.

That would be an act of heresy.

Yeah, but it would be funny. 😛


The main reason I recomment apache on a Windows platform is security and ease of use. Why bother fiddling with IIS when you can setup apache in 8-10 seconds (after download/install)? Why have to download update after update after update after update only to get cracked on the one you happen to miss at 3:30am after it was pulled off the Microsoft webpage because it didnt actually fix the problem (just the symptoms) and ended up causing other problems?

🙂

Ok I will play devil's advocate.

There are situations where IIS is not only recommended, it is required. A few examples:

- You're environment runs Exchange/Outlook. You need a great web based mail system for remote staff. OWA2k requires IIS. You cannot run it over apache or anything else for that matter. Say what everyone will about Microsoft, OWA2k is the most robust/user friendly web based email client on the planet.

- You're software package requires a frontend that is only developed for IIS. Example, MRI, GEAC and Yardi's accounting systems which are widely used.

I think dependancy is the biggest factor, as well as lack of options -- something the user cannot necessarily control. I am most fascinated by it's functionality with Exchange/OWA 2000. This is a very powerful package and was a pretty huge leap for Microsoft from 5.5, about as large as the leap from NT to 2000.

IIS does have a home on some servers. But as the signature says it does not have a home at Network Eleven.
 
Originally posted by: N11
Originally posted by: n0cmonkey
Originally posted by: N11
Originally posted by: n0cmonkey
Raven76

On that note, Ill change my answer. Setup IIS. But do it on Linux.

That would be an act of heresy.

Yeah, but it would be funny. 😛


The main reason I recomment apache on a Windows platform is security and ease of use. Why bother fiddling with IIS when you can setup apache in 8-10 seconds (after download/install)? Why have to download update after update after update after update only to get cracked on the one you happen to miss at 3:30am after it was pulled off the Microsoft webpage because it didnt actually fix the problem (just the symptoms) and ended up causing other problems?

🙂

Ok I will play devil's advocate.

There are situations where IIS is not only recommended, it is required. A few examples:

- You're environment runs Exchange/Outlook. You need a great web based mail system for remote staff. OWA2k requires IIS. You cannot run it over apache or anything else for that matter. Say what everyone will about Microsoft, OWA2k is the most robust/user friendly web based email client on the planet.

- You're software package requires a frontend that is only developed for IIS. Example, MRI and Yardi's accounting systems which are widely used.

I think dependancy is the biggest factor, as well as lack of options -- something the user cannot necessarily control. I am most fascinated by it's functionality with Exchange/OWA 2000. This is a very powerful package and was a pretty huge leap for Microsoft from 5.5, about as large as the leap from NT to 2000.

IIS does have a home on some servers. But as the signature says it does not have a home at Network Eleven.

My little rant mostly applied to these hobbyist home webservers. Companies can afford 24/7 monitoring, most hobbyists cant 😉
 
Back
Top