Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 25842 invoked by uid 500); 22 Apr 2002 18:54:12 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 25830 invoked from network); 22 Apr 2002 18:54:12 -0000 Received: from repulse.concentric.net (HELO repulse.cnchost.com) (207.155.248.4) by daedalus.apache.org with SMTP; 22 Apr 2002 18:54:12 -0000 Received: from w5 (phnxdslgw16poolD183.phnx.uswest.net [65.101.17.183]) by repulse.cnchost.com id OAA22964; Mon, 22 Apr 2002 14:54:12 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Errors-To: Message-ID: <001801c1ea2f$0719d320$0300000a@w5> Reply-To: "Jay Turberville" From: "Jay Turberville" To: References: <009d01c1ea21$60d27470$50821b18@nwadm> Subject: Re: NT Server Date: Mon, 22 Apr 2002 11:53:42 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >From a licensing standpoint, no. You must use a "server" version of the OS. Read the EULA.txt on your operating system CD-ROM. >From a technical standpoint, I'm pretty sure you can do it. Considering that a typical page request often opens many connections, I think the howls of complaints would be legendary if there were a real limit of 10 connections. Jay Turberville > ""You'll probably want a 2000 Server license. The workstation license > > limits the number of incoming socket connections (I believe the limit is > > 10),"" > > Nope, Apache isnt affected by this IIS limitation. > > :) > > If he DOES use IIS, he's nuts. Lotsa probs with weekly updates etc. > Apache for windows keeps the cost down and you can install Frontpage > Extentions > (the only reason I can think of that folks would ask for an NT machine) > with minimal fuss. > I havent personally installed FPE on mine, but I intend to soon. The > questions he asks will probably > help alot of us when he starts up. > > ::waves:: > > BTW all, got that CGI thing runnin. Changed the cgi-bin dir to > "webdir"/cgi-bin and it works fine. > Moved it from the apache/cgi-bin/ dir. > > :) > > > > ==================================== > "It is said that if you line up all the cars in the > world end to end, someone would be stupid > enough to try and pass them." > ==================================== > ----- Original Message ----- > From: "Pete Nelson" > To: > Sent: Monday, April 22, 2002 11:54 AM > Subject: Re: NT Server > > > > I've never used a Windows/Apache server in a production environment, > > only for testing and educating. From my experience, Windows has too > > many memory leaks and security vunerabilities to use as a public server > > (we use linux). However, here are a few suggestions - > > > > 1. You'll probably want a 2000 Server license. The workstation license > > limits the number of incoming socket connections (I believe the limit is > > 10), so for a production web server, you'll need 2000 Server license. > > Likewise, if your users a currently using FTP to upload files, you may > > need to buy licenses for additional named users. > > > > 2. For remote administration - well, this is (IMHO) a downside to > > Windows - you need a GUI to do most tasks. You could try a VNC server - > > http://www.uk.research.att.com/vnc/ - but VNC through windows allows > > only one desktop at a time, so if you need multiple administrators, > > you'll have to be careful you don't have multiple people working on it > > via VNC at the same time (you'll fight eachother for mouse & keyboard > > control). You could also consider purchasing Microsoft's Terminal > > Server, which does allow multiple people access to the GUI. > > > > 3. Be prepared to reboot a lot more often! And if you find the > > server's hanging, check to see that there isn't a dialog box waiting to > > be dismissed on the GUI (this has tripped up our internal web server > > numerous times). > > > > > > > > -- > > Pete Nelson, Web Developer > > > > http://www.ci.stpaul.mn.us/ > > > > >>> soheils@jhanna.com 04/22/02 11:12AM >>> > > Hello everyone. > > I have a question, that might be a bit off the topic, so please forgive > > me. > > I have been running Linux, and FreeBSD servers for my hosting company, > > and > > recently noticed that a lot of the people who get referred to me, are > > asking > > for NT servers. > > > > I am pretty familiar with the NT intranet servers, but have never made > > a web > > server using one. > > So, here are the questions I have: > > 1. Do I actually need to have an NT machine, or a Win2000 Server to > > setup a > > web server, or can I just use a Win2000 software to do this? > > > > 2. Is it fairly simple to operate a Windows server remotely? > > > > 3. Can anyone give me some quick pointers to get me started on this > > please? > > > > I am looking for an inexpensive solution, if possible. > > > > > > > > Sincerely, > > Soheil > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org