|
We have been successfully using SR for almost 6 months now, but I have run into a new problem. My remote users are trying to access an internal web server which acts as a web to host mediator to an offsite mainframe. My web server is in the 172.16.x.x range of addresses, and it that is included in my encryption domain. Connecting to it works fine. However, when it tries to serve the 3270e session from the mainframe (which has an IP in the 170.115.x.x net) it fails to connect, and I can't telnet to the port on that server, either. It is obviously a routing issue, but I've even added the 170 address as an object to my encryption domain and still no-go. When I try to traceroute to the 170 address, it locks up the clients if SR is running. I can see the packets being accepted and decrypted at the firewall. TIA for any help. Mark P.S. Please post to the group or my other account, [EMAIL PROTECTED] I appreciate the consideration. I have suddenly been unable to post from that account after 2 years without problems. Thanks. |
- RE: [FW1] Securemote to "non-internal" addresses ... Mark Whitworth
- RE: [FW1] Securemote to "non-internal" addre... Dan Hitchcock
