Re: XP Pro as Web Server w/Firewall?

From: DevonS (DevonS_at_discussions.microsoft.com)
Date: 01/02/05


Date: Sun, 2 Jan 2005 14:33:02 -0800

So... sounds like I should just not bother. On the other hand, this is just
my home play box, nothing important on it... gets rebuild ever other month.
I need to study my security topics.

Man... I love computers and technology. Everything is so simple and
convenient. >:(

Thanks for the info.

-D

"Leythos" wrote:

> In article <9769EAFB-5F35-42AD-85E8-2FDE8273DE17@microsoft.com>,
> DevonS@discussions.microsoft.com says...
> > I'm a developer, but never done any web development. I want to start playing
> > around and set my XP Pro machine up as a web server. I'll set up IIS and the
> > virtual root stuff, but my questions are:
>
> Running a IIS service on XP Pro and allowing public access is asking for
> trouble - not because IIS on XP isn't secure, but, since you're asking
> this question (and it's a good question) you show that you don't know
> enough about security to do so.
>
> In locking down a IIS server for public access there are a LOT of
> changes that make your workstation less usable and not desirable for
> local use. There are many services and security changes that will make
> your machine less than friendly for your normal use - at least if you
> lock it down properly.
>
> > 1) How do I open up a port (or whatever, terminology is not my strong suit)
> > throught the XP firewall?
>
> In XP SP2, and you should be running SP2, just open the firewall and
> follow the directions to open port XX where XX is the port you are
> running your web server on. Keep in mind, if you want to run it on
> Workstation you should at least not run it on the standard web ports
> that bots scan for - I would suggest that you run it on port 40000 or
> something strange like that. While it won't keep people out, it does
> eliminate some of the background chaff that you would see on 80.
>
> > 2) Any other precautions to take when doing this?
>
> Yes, lock down the computer so that it's almost not usable.
>
> Setup authentication so that only a authenticated user can access the
> site - make sure that all accounts have STRONG PASSWORDS. This means
> that once people find your site they will be prompted to enter a
> workstation user name and password before they can even see the site -
> one more level to stop that crackers.
>
> > 3) If I don't have a domain name, just use my IP (i.e. http://iphere/website)?
>
> From inside the network it would be:
>
> http://localhost:portXX for the root site
> http://localhost/virtualsite:portXX for virtual directories off root
>
> for external access it would be:
>
> http://ipaddress:portXX
> http://ipaddress/virtualsite:portXX
>
> If you use port 80, then you can leave ":portXX" out completely.
>
> > 4) I also have to go through a LinkSys wireless router. What do I open up
> > here?
>
> You have to FORWARD TCP 80 to the internal IP of the workstation.
>
> > 5) Other pertinent info?
>
> Yes, don't do this until you completely understand security, this is the
> fastest way to compromise your machine.
>
> --
> --
> spamfree999@rrohio.com
> (Remove 999 to reply to me)
>



Relevant Pages

  • Re: XP Pro as Web Server w/Firewall?
    ... I'll set up IIS and the ... Running a IIS service on XP Pro and allowing public access is asking for ... follow the directions to open port XX where XX is the port you are ... Workstation you should at least not run it on the standard web ports ...
    (microsoft.public.windowsxp.network_web)
  • Re: windows 2000 IIS 5 403.6 ip address restriction
    ... web server, ... Running www.ethereal.com sniffer on ... your workstation, and/or checking your web server logs, may help confirm or ... >I have a problem with IIS 5.0, My IP address is blocked by IIS server ...
    (microsoft.public.inetserver.iis.security)
  • Re: Jeez... how do I even start ????
    ... > When I would start IIS from the Administrative tools, ... > situation, with the same resolution as described in the msdn article, so ... A lot of these other posts also mentioned the ASPNET user. ... > the web server was running on this machine. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: preventing username enumeration on NT4
    ... Nimda Worm Shows You Can't Always Patch Fast Enough ... should start to investigate less-vulnerable Web server products. ... Microsoft's Internet Information Server (IIS), ...
    (comp.os.ms-windows.nt.admin.security)
  • Re: preventing username enumeration on NT4
    ... Nimda Worm Shows You Can't Always Patch Fast Enough ... should start to investigate less-vulnerable Web server products. ... Microsoft's Internet Information Server (IIS), ...
    (comp.os.ms-windows.nt.admin.security)