Run Webserver

Run a Webserver at home?
I have a server running Server 2003 and i need to run a webserver for an email server! How can i lower energy costs besides switching to laptop. Would it help if the server is running with out a monitor? Thanks

A laptop with a great cooling system will suffice. About costs... http://michaelbluejay.com/electricity/computers.html ------------------ You are better off using a free online mail service like Gmail. Seriously, running a mail server at home could be a real pain in the butt, there are simply so many factors that could ruin your plans, power outages, ISP problems, computer software/hardware failure, etc. I am talking from experience, you have to remember to manage the server once in a while to make sure everything is running smooth, so the thought alone is always on the back of your head. Also, the user interface and spam filters are not as good as the pro companies unless you design your own.

If i have a broadband connection, Can i run a webserver in it to be open to the internet to run my application


Yes. It is perfectly possible to do this, though some ISPs' terms of service forbid it, and some ISPs block port 80 (the normal port for HTTP). If you do not have a static IP address, go to http://www.dyndns.com or http://www.no-ip.com and set up dynamic DNS; it will make your life easier (most routers include a client for either or both of these services). If you have more than one computer, assign your Web server a fixed IP address on the local network, then have your router forward requests on the Web port (usually 80) to your Web server.

how to run a webserver on mac?
i got a domain from no-ip.com, then how do i run a web server on mac??? or any other suggestion?

If you are using Mac OSX Leopard on your mac, this video will show you how to use the built in apache web server: http://www.youtube.com/watch?v=ep5E4Y4N65E

Can someone tell me step by step how to set up a static IP address so that i can run a webserver?


To obtain a static IP address from your ISP (i.e. Time Warner), you need to call them and ask for pricing. Honestly, I don't know how much it is, but it will incur a monthly charge. Second, to get a website address, there are a handful of providers out there that you can get a domain name for as little as $2.95/month. I prefer GoDaddy (http://www.godaddy.com/). This will incur a yearly charge. Once you have that information, you need a hosted DNS provider so that when someone out there types in your domain name, it knows where to go. Most are paid services, but there are some free services out there. I prefer Afraid.org (http://www.afraid.org/). Once you sign up, you'll need afraid.org's DNS server addresses. Write these down and plug them into GoDaddy's DNS server information. Hope this makes sense so far... Finally, in afraid.org, you're going to need to create an "A" name. This is an "alias" name for your website. So, if your static IP (from your ISP) is 1.2.3.4, you add the "A" name as "www.[whateverdomainnameyouchoose].com" as 1.2.3.4. Hope this makes sense so far... Final step (short of creating your website) is to login to your router (or if you have your broadband router connected directly to your computer you need to access the firewall settings) and forward port 80 to your PC's internal IP address (again, if you have your broadband router connected directly to your computer, just allow/stop blocking port 80). Now you can get crazy and use your new found static IP and domain name for email serving, ftp hosting, etc., but that's for another day. === In the background, godaddy.com knows afraid.org's DNS and afraid.org's DNS says "www.[whateveryourdomainnameyouchoose].com" is "1.2.3.4". Now it will take too long for me to explain EXACTLY how everything takes place so here's a brief description of what happens: 1. Someone types in "www.[whateverdomainnameyouchoose].com". 2. That request goes to your ISP's DNS (domain name server) and that database looks to see if they know what IP that is going to. If it doesn't it forwards the request to another DNS to see if it knows where it is. 3. The DNS says "Yes, the IP is 1.2.3.4!". 4. The request goes to your server and says "Hey, where's your website?". 5. Your server gives the website to the request. 6. It sends the reply back to "someone". Hope this helps. It may be beneficial to draw a diagram of exactly what happens so you can visualize what's going on. It helps me. Good luck.

I want to run a webserver with dsl connection and windows 2003, is there any body know how?


If your DSL connection is Dynamic Public IP issued by ISP then you may not able to do it. One of the work around is to do virtual mapping using some software easily available over the net (I cant remmber the name, something sound like myip or noip, or something of which it issue u a virtual IP for your webserver but then constantly map to your ISP IP whenever they are changes)

What Program is good for a home webserver?
I know about these two programs. 1.Abyss webserver 2.Apache Is there anything (doesnt have to be free) that I could use instead of those two. I want to run a webserver from my own computer. How can I do this. I would like a very easy to use webserver software. I also would like one with many tools. Are there any other software for this?

Depending on the use of the webserver, you may want to look into many options. If you are just going to be hosting files for a website, I would recommend Apache Web Server. The most secure servers are set up as LAMP servers (Linux Apache Mysql Php). There are many free Linux ISOs floating around the net which can get you started. For a complete guide, go down to your local bookstore and get a book specifically about LAMP servers.

I'm tring to run apache http webserver on my PC it works with localhost but not my IP addres. Can you help me
My IP addres is http://86.153.233.212/ instead of showing the files in my htdocs folder it shows my BT router manager. how can i get apache to link the files to the IP address? If you can help thanks a lot. I really want it. Dynamic should still work. i tried to use a dynamic DNS service but it wasn't very good so i'm searching for others

So - you're behind a router, and the router's IP address is 86.153.233.212. When you open up a browser to that address, you see the router's web interface, naturally. Your Apache server's IP address is not 86.153.233.212, it's whatever address was assigned to it (or you statically assigned) in the private network behind the router. That address is not accessible from the Internet. For example: {{{ INTERNET }}} | | 86.153.233.212 [YOUR ROUTER] | 192.168.1.1 | | | 192.168.1.00 [APACHE SERVER] In order to be able to reach your Apache server from the Internet, you have to tell the router to pass Web requests to the Apache server. This means one of two things EITHER 1) You will no longer be able to talk to your router via hhtp OR 2) You have to set up either the router or the Apache server to respond on a port other than 80 If you can set the router to use a different port that would be best since only you need to know how to access the router. Then configure port forwarding on the router so that all incoming requests on port 80 are sent to 192.168.1.100 or whatever the address of your Apache server is.

How many websites can you run?
How many websites could I run off of apache webserver and if I can what would I need to do to my computer to be able to run them

How long is a peice of string? If you have the RAM, CPU and diskspace... set up virtual domains in Apache and go dog go!

How can i simpley create a forum on my webserver.?
I am running a web server off my windows 2000 server edition PC. I have the website running and i want to figure out how to set up a forum or message board.

There are "Forum" packages on the Net both free, shareware and commercial. The two key factors are your ability to install, maintain and tweak it and how much your willing to spend or find help to get it done. A tip is at the beginning just get a "Forum" up and running reliably and then **keep things simple** and just put the effort in to keep it backed up. Nothing annoys forum members more than the forum going down all the time as compared to things being a bit rudimentary. You then use the original forum to create a duplicate and bring together a couple of people in your forum who will Beta test for you, then do the custom tweaks you might need on the duplicate and Beta test it thoroughly before moving it over to the "running" version.