HP3000-L Archives

March 2002, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gibson Nichols <[log in to unmask]>
Reply To:
Gibson Nichols <[log in to unmask]>
Date:
Wed, 20 Mar 2002 10:17:19 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Okay, thank you.  Someone provided me with the port numbers.

When allowing the port numbers on the firewall I assume that more
restrictive measures
are also suggested such as filtering IP addresses.  So, the HP e3000 has no
role in
the security of the connection.

"Tom Lang" <[log in to unmask]> wrote in message
news:a78iro$adn@dispatch.concentric.net...
>
> "Gibson Nichols" <[log in to unmask]> wrote in message
> news:a787an$fqm5@eccws12.dearborn.ford.com...
> >
> > If we place a system outside of a firewall how do we configure a DSLINE
> > command
> > to connect through the firewall?
> >
> >
> This is a security issue, so no details will be given here.
>
> The methodology, however, is to configure your firewall to accept the port
> connections from the DSLINE's attempts to connect through the firewall.
The
> firewall administrator must 'open' these port connections. The
administrator
> can see these port numbers, during attempts to connect via the firewall. I
> have the list of ports which your firewall must 'open', but I will only
> provide such information, after you provide a 'more secure' identity.
Please
> understand my caution.
>
> Kindest Regards.
>
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2