| Title: | POLYCENTER AssetWORKS + Microsoft Systems Management Server |
| Notice: | See note 937.1 for kit access information access |
| Moderator: | RDVAX::LEVY D |
| Created: | Wed Feb 23 1994 |
| Last Modified: | Fri May 30 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 977 |
| Total number of notes: | 3989 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 934.1 | a quick dump.... | ESSB::RJOYCE | Wed Jan 22 1997 12:44 | 58 | |
| 934.2 | PAW over Internet & throgh firewalls? | GO4GUT::PARSONS | Punicenter Support | Mon Feb 10 1997 22:51 | 11 |
This problem turned out to be caused by the SUN box being the other
side of a Firewall (the distribution was over Internet).
Has anyone any comments on trying to use PAW to distribute software
through a Firewall? Anyone tried it?
Thanks,
Tony Parsons,
Sydney OMS
| |||||
| 934.3 | No firewall proxy for PAWComm | SUBSYS::CARLETON | A paradigm shift without a clutch | Wed Feb 12 1997 13:52 | 16 |
Based on my limited understanding of firewalls, you would need to have
an application-level proxy that could run on the firewall machine(s)
that could check and log every transaction between the red and blue
side of the network via PAWComm protocol. In a sense, PAWComm is a
general purpose file moving application like ftp so you could use it
to move any kind of data. Without some kind of per-SRQ firewall
crypto-key, the proxy would have a hard time telling legit SRQ's
from and SRQ containing trade-secret data. No PAWComm proxy
exists and none is planned. You would have to submit a requirement
to CA.
As an alternative, you could use IP-tunneling software to create a
vurtial private network between the sites over which PAWComm could
run. Take a look at the AltaVista Tunneling products.
| |||||