Web Server Question

[johnny5]

I'm thinking of starting a web server from home and was wondering which operating system was best. I am going to dedicate one box as a server to host a few web sites. I have NT 4.0 Server and I have Linux Red Hat 8.0. I was leaning toward using Apache 2 on either operating system. Which one would give me the most security and be easy to configure. Right now I'm running 3 Windows98se computers networked to a router to a DSL modem.

Thanks.........

[Player0]

I've installed on both, and because Im a MS kinda guy, I prefer the NT set up. Despite what the Linux geeks tell you, theres not really much of a security risk buy using the NT platform over the Linux. If anything, the ease of using a GUI makes catching those security holes much easier, imho.

The liquidninjas.net development server is running Apache 2, beta MySQL and PHP. For an NT/Apache2 system, you have to use the beta PHP modules. If you dont plan on installing PHP or SQL or anything fancy like that, dont worry about it.

Apache 2.0 runs great on Windows 2000 Server. Not sure about NT4. Youd have the webserver running much faster on that then a linux box, unless you have lots of linux experience. Again, its not anymore of a security risk than a Linux box if you configure it correctly, plus will install much more quickly because of the robust Windows GUI.

The only downside is SMTP (email server). Linux comes with Sendmail, a simple, free, and very well accepted email server. NT users are generally expected to use Exchange, but that can be overkill. You will have to find a small free/shareware SMTP server on your own for Windows. Might have to put $30-$40 on down for it.

If you need help configuring Apache, let me know. Lots of good info on the web too though. Thats usually where I end up needing help.

[johnny5]

Player0: I'm sure I'll have plenty of questions. I just bought one of those 24 hour books on Apache 2 and I will be reading it tonight. I to am leaning with NT 4.0. I'm thinking of just a simple web server, nothing fancy. Been looking at dslwebserver.com for info. I'm a little concerned that my DSL is dynamic and not static. No sense in starting up if my ip# keeps changing.
thanks for the quick reply...........

[^7_of_9]

I use Windows 2000 Server myself.

It's setup on a Dual AMD system and runs great.
I've also got a second Webserver running on Linux as well.


both run great.

Windows 2000 is more user friendly however, but the Linux one seems to run a bit faster even though the box is slower.

[NorthernYankee]

Originally posted by johnny5
Player0: I'm sure I'll have plenty of questions. I just bought one of those 24 hour books on Apache 2 and I will be reading it tonight. I to am leaning with NT 4.0. I'm thinking of just a simple web server, nothing fancy. Been looking at dslwebserver.com for info. I'm a little concerned that my DSL is dynamic and not static. No sense in starting up if my ip# keeps changing.
thanks for the quick reply...........

http://www.no-ip.com

Has a nice lil proggy that will keep your dynamic IP updated, i use it for my FTP server.

--NY

[johnny5]

NorthernYankee :super cool, thanks for the site.........

I have the software, I have the hardware, it's just the know-how I'm lacking.......

[Player0]

Johnny5, you are a prime candidate for:

http://www.dyndns.org/

[^7_of_9]

I use DynDns myself and have been using it for AGES now.
No problems whatsoever with it and I run DirectUpdate which updates the info on it if my IP ever changes.

[johnny5]

Well, I went with NT 4.0 and Apache 2.0 also. I registered with DynDns.com too. I can see my site internally, but not from the internet. Thinking its a port-forwarding problem, ISP blocking port 80, or router-setup thing.
It's back to Barnes&Noble for more books:)

[Gregorach]

Player: re SMTP - I dunno about Apache (I'm an IIS guy) but if you've got NT Server then you can install the standard SMTP component of IIS. Seems to work OK...

D

[^7_of_9]

J5,

Are you using a Router to share the internet with all of your machines? If so you'll need to enable port forwarding in there. ISP blocking Port 80 .......... I would hope not :eek:

Also if your using DynDns remember that the www part won't work unless you check the box that says "Use Wildcards" and then check to make sure the IP address it should be using is correct (The IP your ISP gave you, not an internal one)

(Sorry if this all sounds like routine stuff, but sometimes you forget to do something no matter how good you are)

[^7_of_9]

DOH! Just read your post again and see you are using a router. Which one are you using and maybe myself or someone else can walk you through Port Forwarding on it.

[johnny5]

^7_of_9 :
Thanks for the info on the "wildcard". I'm using a Linksys Cable/Router with 4-port switch model # BEFSR41. I have to look into the router setting to give my server a static #. Hey, nothing sounds routine as this is all new to me. (newbie at web hosting)

thanks.........

[Player0]

Thanks Gregorach, thats a good tip. I forgot that IIS had a SMTP server. That should work good.

Thanks!

[johnny5]

Well, I think I have everything right.:) I can access the site from IE , but not from AOL! :confused: I access the site on IE through my dsl line which is networked to my server. Do you think it's just going through the network and not the internet? I checked on my wife's computer with is not connected to my network through AOL and can not access the page. Hmmm............

Any ideas?

[Player0]

I dont know...give us the IP/dns name so we can try it ;)

[Synthohol]

Originally posted by johnny5
Well, I think I have everything right.:) I can access the site from IE , but not from AOL! :confused: I access the site on IE through my dsl line which is networked to my server. Do you think it's just going through the network and not the internet? I checked on my wife's computer with is not connected to my network through AOL and can not access the page. Hmmm............

Any ideas?

had same prob here, so i set the DMZ zone to the server, all was well from the outside. till i got 500 hits from unwelcome port scans!

[johnny5]

Well, I have been trying different things, different configurations on the routers, tcp/ip settings, putting the server in the dmz, and nothing works. :mad:
I might have to start looking into Apache 2.0 and see it that is the problem. The site is ~www.jpt.homeip.net.~ I am thinking of connecting the server up directly to the dsl modem in front of the router with just Zone Alarm Pro to protect it, be I'm leary of getting hacked! This is what I keep getting...............
PS. Which is not the web page ;)

[^7_of_9]

http://www.komher.homelinux.com/nuke12386954

There's my current setup. Using a D-Link DI-704 Router which then gets put through a 16 Port Linksys Hub and into that box.. The Webpage that is on there is served off of Win 2000 Server and using MySQL for the database off the same server.

I just have routing setup on port 80 to go to that particular computer. Setting DMZ permanently is not something you'd want to do as Synth found out. I get lots of hits on my Router each day and if it wasn't for the router those hits would be on the box instead.

[TGC]

I ran a trace route and pathping on your IP and it resolves to a verizon MAC address. I am wondering if they are infact blocking port 80 requests, can you set the server to listen on port 8080, or some other port. I would suggest doing that, then test it again.

I'm sure you have already done so, but have you enabled port forwarding in the routers menu to direct request to port 80 to the interenal IP assigned to that machine. It is under the Advanced tab on that routers menu. If you chnge the severs port to a different one (8080) you will obviously have to change it in on the router as well.

[johnny5]

Thanks TGC, I "port forwarded" to 8080 and it works. I have to type in :8080 after the web address. I read somewhere on the net how to get around this, just have to find it again............ :) So my brand new site is www.jpt.homeip.net:8080 . All your get is the Apache default page for now. :( Will be working on a new page soon.......

[^7_of_9]

Use port 80 instead and you won't have to worry about anyone putting in the Port Number as http defaults to 80.

[johnny5]

^7_of_9 : I tried that { Use port 80 instead } but my IP blocks that port! So I'll be looking for a work-around on the long address........

[TGC]

:cool3: Glad to be of service ;)