LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (January 1998, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Thu, 22 Jan 1998 08:01:17 -0600
Reply-To:   "Collins, Craig" <COLLICR1@MAIL.STATE.WI.US>
Sender:   "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:   "Collins, Craig" <COLLICR1@MAIL.STATE.WI.US>
Subject:   Securing SAS/Connect using IP through a firewall?
Content-Type:   text/plain; charset="iso-8859-1"

Has anyone had experience in securing SAS/Connect through a firewall? We are concerned about opening a range of ports for IP communication from any source through our firewall and to our mainframe.

If you have identified another way to secure these ports so that only SAS can be using it instead of opening them to the world, I would be very interested.

Part of the problem as we see it is that we must have one open port available for each concurrent user of SAS/Connect connecting with this method. This means we can't just open one port for 5 users, we must instead have 5 ports.

Ideas?

Craig Collins State of Wisconsin Info-Tech Services Collicr1@mail.state.wi.us


Back to: Top of message | Previous page | Main SAS-L page