|
I think there is an IBM document on how to get around this NAT issue. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 02/10/2004 02:42 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject Re: SDM1002 on Service Agent connect via VPN Neil, I'm curious - are those systems live on the Internet - i.e., they have valid Internet addresses? Or do they hop to an iSeries with a valid IP address? I don't believe the VPN method works if you are behind a NAT-type router, unless you have an iSeries outside of your protected network. If the iSeries is a 192.168.x.x type box (or equivalent class A or B), and you can get out via VPN, I'd love to know how, without a box to hop to. I wondered (but have not tried) whether it'd work with a DMZ-type setting on our LinkSys to the iSeries, with port forwarding through the router. Of course, both those are not anything I'd want to do with a production box. Vern At 03:23 AM 2/10/2004 -0500, you wrote: >I have several V5R2 systems with Service Agent (Service Director) >configured, and the connection to IBM via external 7852 modems (SDLC >dial). Works fine - Service Director places Test calls, does the >automatic PTF check weekly - no problems. > >On a couple of systems I configured IBM Universal Connection (VPN over >Internet). SNDPTFORD and SNDSRVRQS *TEST work fine over the VPN >connection. Service Agent refuses to connect and issues SDM1002 messages >(not able to place a service call). I've been testing by creating a Test >problem. WRKPRB shows the test problem as OPEN, and within a minute >changes to PREPARED - and QSYSOPR shows the SDM1002 error message. I can >run SNDSRVRQS *PREPARED and the PREPARED problem is SENT, but Service >Director refuses to do this itself. Any clues ? > >...Neil _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.