Forum Home
Press F1
 
Thread ID: 34927 2003-06-28 06:26:00 Web server Question stu140103 (137) Press F1
Post ID Timestamp Content User
155818 2003-06-28 06:26:00 Hello every one,

I have a test web server, which has been running over my network, & I have been thinking about putting it live.

Is there any thing (major or not major) I need to know before I do this????

Like about opining the HTTP port & FTP port
(On a Win XP PC, for more info on how I am doing it see this post: pressf1.pcworld.co.nz)

(I know about port scanner (so I will not be using the default ports 80 / 21 instead I will be using 8080 & 2121 is that ok???)

Also the HTTP software I am using is: Savant
- FTP ------------------------is: GuildFTP (I think, I have not made my mind up yet)

(The resion why I am asking this is just so I can refresh my general knowledge on this & so I do not put our network at risk)

Also we have two firewall( the win XP one & Zone alarm) on the gateway pc(Win XP) ;) & I have a name thanks to No-IP.com & another DNS company 		stu140103 (137)
155819 2003-06-29 05:49:00 **Bump** stu140103 (137)
155820 2003-06-29 07:01:00 Seen no one can help me here :( does any one know of another computer help desk forum or a forum which I can ask this question on???? stu140103 (137)
155821 2003-06-29 07:20:00 How is the network laid out at the moment?

I'm picking that the webserver is the gateway computer?

I'd also start by getting someone you know to try and access it first. Before you go publishing the details everywhere. 		-=JM=- (16)
155822 2003-06-29 08:33:00 The webserver and FTP Server should be available to your internal network already and everything should be happy.
I'm picking that you want to allow external access to the server now?

Firstly - you will need to download a program from no-ip.com or whoever your free DNS Server is. This program will need to tell the DNS Servers what your IP Address is, and there are several different ways of doing this:
1 - The program may update itself with the server every hour automatically
or 2 - you will need to tell the program to update itself with the server (windows scheduler will do this)

Then, you will need to enable port fowarding - talk to Chill as he has done this, but basically what you want to do, is get your gateway to foward requests on port 80 and port 21 to the webserver computer. The secury way to do this would be to have a strict firewall on the gateway, and another on the webserver only allowing the webserver and ftp server access to the internet.

From there, you realize that both the gateway and webserver will need to be turned on to access your websites/ftp server?
Also, if you use a Router for your internet connection, you will need to pinhole connections through - this will replace port fowarding software.


CyberChuck 		cyberchuck (173)
155823 2003-06-29 09:17:00 > How is the network laid out at the moment?

--- Gateway (Internal ADSL modem, dad's computer)
|
--- Hub
|
--- Test computer (the one with the HTTP/FTP server software on it)
|
--- My computer (the one I am typing this on)

> I'm picking that the webserver is the gateway
> computer?

See above :) 		stu140103 (137)
155824 2003-06-29 10:30:00 Just run the DUC on the gateway and you'll want to forward the ports to the test computer, not sure what method you're using for sharing the connection. -=JM=- (16)
155825 2003-06-30 01:07:00 > The webserver and FTP Server should be available to
> your internal network already and everything should
> be happy.
> I'm picking that you want to allow external access to
> the server now?

Yep :)

> Firstly - you will need to download a program from
> no-ip.com or whoever your free DNS Server is. This
> program will need to tell the DNS Servers what your
> IP Address is, and there are several different ways
> of doing this:
> 1 - The program may update itself with the server
> every hour automatically
> or 2 - you will need to tell the program to update
> itself with the server (windows scheduler will do this)

I all ready have one ;)

> Then, you will need to enable port fowarding - talk
> to Chill as he has done this, but basically what you
> want to do, is get your gateway to foward requests on
> port 80 and port 21 to the webserver computer. The
> secury way to do this would be to have a strict
> firewall on the gateway, and another on the webserver
> only allowing the webserver and ftp server access to
> the internet.

Yep that is what I am going to be doing.

> From there, you realize that both the gateway and
> webserver will need to be turned on to access your
> websites/ftp server?

Yes. 		stu140103 (137)
155826 2003-06-30 01:10:00 > Just run the DUC on the gateway

?:|?:|

> and you'll want to
> forward the ports to the test computer, not sure what
> method you're using for sharing the connection.

ICS 		stu140103 (137)
155827 2003-06-30 01:14:00 When I first put the test server online I will be using the default ports 80/21 but after that I will be using 8080 / 2121 to stop port scanners

Would there be any problem with that??? 		stu140103 (137)
1 2