T.R | Title | User | Personal Name | Date | Lines |
---|
1913.1 | Need another port | OSL09::BJORNMY | Open but Secure | Mon Apr 14 1997 05:36 | 10 |
| Note: port 25 is smtp, port 23 is telnet.
You have to select another port, for instance 1001 on the firewall and
set up the generic proxy to connect to port 23 on the host you want to
connect to. You then do a telnet 1001 to the firewall and it will give
you the login prompt on the internal server.
Beware of security implications!
Bj�rn
|
1913.2 | web generic proxying | SNOFS1::stylia.sno.dec.com::snov14::stylianoua | | Fri Apr 18 1997 00:56 | 3 |
| What about getting to internal web servers?
AS
|
1913.3 | | CHEFS::zkodhcp-29-48-237.zko.dec.com::PITT | Gone with the winsock ... | Fri Apr 18 1997 14:37 | 6 |
| We've got a customer in the UK using generic relay for
inbound WWW access. You should however discourage it
from a security point of view. Can't the WWW Server be
placed in green net instead?
T
|
1913.4 | | SNOFS1::stylia.sno.dec.com::snov14::stylianoua | | Tue Apr 22 1997 00:37 | 15 |
| NT version
ok but would the user need to use the gatewayname.com:port
to get access or ip address.
Unix version - with screend implmentation to get to internal web servers.
If there were 2 web servers internally, say
www.site.com
www2.site.com
would the dns on the firewall resolve these names
Andrew S
|