Setting up a web dev. test server with remote access

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: doug (anonymous_at_discussions.microsoft.com)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 06:40:35 -0700

Firstly, be aware that IIS on XP only allows 10
connections, which can be easily used up by 2 or 3
people.

You will want to secure this properly with NTFS
permissions on each project directory. If each tester has
an account, only give access to that account in the NTFS
permissions.

doug
>-----Original Message-----
>Dear all,
>
>I'm currently setting up a web development test server
but need some advice
>in how to configure the remote access security correctly.
>The server is running Windows XP Pro due to budget, and
therefore
>unfortunately only one virtual host.
>
>This server will have several project sites (virtual
folders) under the
>wwwroot, and each of them should be accessible by beta
testers from outside
>our network/FW. The actual development server is secured
and not accessible
>from outside our FW.
>
>Ex.
>http://123.123.123.123/project_1
>http://123.123.123.123/project_2
>etc...
>
>I have removed anonymous access to the web server in IIS
to start with and
>added accounts for each beta tester under the group
WEBDEV-BETA. But how
>should I continue and make this secure? I don't want any
of the testers to
>be able to access anything else but their own project.
>
>Does anyone know of a good tutorial/guide on this, or
some hints maybe? I've
>been spending some hours now trying to find a decent
guide on how to do this
>correctly, but I couldn't find any.
>All I could find was this;
>http://www.winnetmag.com/Web/Article/ArticleID/20252/2025
2.html but that one
>ends where I wants to begin.
>
>Thanks in advance!
>
>
>Best regards,
>Jonah Olsson
>Generation Software
>
>
>.
>

Relevant Pages

  • Re: Open Ports....How to block them all....?
    ... > I keep it up to date with SP's and Patches but find that the server keeps ... Frequently this happens through an IIS ... Ways to secure your system are detailed at: ...
    (microsoft.public.inetserver.iis.security)
  • Re: Outlook Web Access!!
    ... I don't know how they can be so sure it's secure... ... relevant IIS and other patches as they come out. ... OWA to your DC to do user authentication, ... > protect Exchange server in four different ways. ...
    (microsoft.public.security)
  • Re: Outlook Web Access!!
    ... I don't know how they can be so sure it's secure... ... relevant IIS and other patches as they come out. ... OWA to your DC to do user authentication, ... > protect Exchange server in four different ways. ...
    (microsoft.public.win2000.security)
  • RE: "Secure" Web Hosting?
    ... IIS 6.0 comes as standard on Server 2003 and is secure enough. ... I have switched to Apache though, coz there were a few things that couldn't work right on IIS. ... Subject: "Secure" Web Hosting? ...
    (Security-Basics)
  • Re: write with cURL
    ... It takes time to set up an account for you, process the billing, etc. ... Sorry, my servers are secure. ... Nothing you have told me shows me you know how to lock down a server so that it is secure - other than to use the server's file security. ...
    (alt.php)