Tenon Intersystems Please see text links at bottom of page for navigation
Please see text links at bottom of page for navigation

Search tenon.com

Thanks to:

WebTen

Re: WebTen behind a Firewall on a private IP address

To: webten@xxxxxxxxxxxxxxx
Subject: Re: WebTen behind a Firewall on a private IP address
From: Christian F Buser <mac-christian@xxxxxxxxxxxxxxxx>
Date: Fri, 09 Nov 2001 15:57:08 +0100
At 13:19 09.11.2001 +0200, you wrote:

>Usually a company has its Public IP addresses that allow connection 
>from the Internet to the Router
>and its Server.  The Server is on a Public IP, so is the router.
>Than you create your Private Network  and you use  N.A.T.  "address 
>translation" .

No. Our access provider wants us to only let the firewall/router respond to the 
public IP address (such as 111.111.111.111) which is translated by the 
firewall/router to the appropriate private IP address (172.16.5.3, for example) 
for the web server, and to another private IP address (172.16.5.4, for example) 
for the mail server. Of course, also the rest of the networtk will be in the 
private numbering sheme. 

>So if you need a PRIVATE Server with a Private Router on a Private 
>network that has no contact to the already secured LAN why having an 
>additional firewall? 

No, the server should be public, but in the private IP numbering. 

>if you mean that you want to have the router understanding  that the 
>Public IP address of the Server is 1_Public and that 1_Public 
>corresponds to 1_Private so that all calls for 1_Public are 
>translated to 1_Private this is possible, but it depends solely, as 
>far as I know, from the possibilities that your router offers and has 
>nothing or little to do with Webten itself. (With 2 Ethernet cards 
>the server can answer to two different physical IP addresses)

This seems to be what I want to do. And I know how to set up a WT-server using 
2 physical ethernet interfaces, 1 for the WT-stack, the other for OpenTransport 
(for everything else other than WT). 

The question was whether WT really can work in such an environment and what 
ports I need to open for this (most probably 80 for WWW, 81 for Squid-cache, 84 
for the admin-server and 21 for ftp). 

>Plus if your LAN is Mac OS based, you can separate TCP/IP and 
>AppleTalk protocols so that TCP/IP is used for Web related 
>applications and AppleTalk for local communications.  Your Macs 
>(Server excluded) are then not accessible via TCP/IP.

This would be nice but regrettably the only Mac will be the server...

Thank you for responding, and best wishesm Christian.


---------                    ----------
Tenon Intersystems' webten Mailing List
To unsubscribe: send mailto://webten-request@xxxxxxxxxxxxxxx
with the body: unsubscribe
Find searchable Mailing List archives at:
http://listsearch.blueworld.com/webtensearch.lasso

<Prev in Thread] Current Thread [Next in Thread>

| Tenon Home | Products | Order | Contact Us | About Tenon | Register | Tech Support | Resources | Press Room | Mailing Lists |

Powered By iTools

Copyright©2003 Tenon Intersystems, 232 Anacapa Street, Suite 2A, Santa Barbara, CA 93101. All rights reserved.
Questions about our website - Contact: webmaster@tenon.com.


Tenon Home  Tenon Home  Tenon Home  Tenon Home Product Info  Tenon Ordering Contact About Register Support Resources Press Mailing Lists