|
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] Dial-up isn't a problem. The problem shows up when the iBox tries to send something back to the client (like a compile error listing or a completion message). All the iBox knows is the public IP address (on the outside of the RT314). So it checks with the firewall, which of course ignores it; eventually the iBox job times out. This gets the IP address and does STRCODE for you. HTH! Thanks, Reeve START: PGM PARM(&PASSWORD) DCL VAR(&PASSWORD) TYPE(*CHAR) LEN(10) DCL VAR(&USER) TYPE(*CHAR) LEN(10) DCL VAR(&DEVD) TYPE(*CHAR) LEN(10) DCL VAR(&RCV) TYPE(*CHAR) LEN(893) DCL VAR(&RCVLEN) TYPE(*CHAR) LEN(4) DCL VAR(&ERR) TYPE(*CHAR) LEN(100) DCL VAR(&FORMAT) TYPE(*CHAR) LEN(8) + VALUE('DEVD0600') DCL VAR(&IP) TYPE(*CHAR) LEN(15) RTVJOBA JOB(&DEVD) USER(&USER) CHGVAR VAR(%BIN(&RCVLEN)) VALUE(893) CALL PGM(QDCRDEVD) PARM(&RCV &RCVLEN &FORMAT + &DEVD &ERR) CHGVAR VAR(&IP) VALUE(%SST(&RCV 878 15)) SNDPGMMSG MSGID(CPF9897) MSGF(QCPFMSG) MSGDTA('IP + address:' *BCAT &IP) TOPGMQ(*EXT) + MSGTYPE(*STATUS) STRCODE RMTLOCNAME(&IP) USERID(&USER) + PASSWORD(&PASSWORD) -----Original Message----- From: code400-l-admin@midrange.com [mailto:code400-l-admin@midrange.com]On Behalf Of Edwards, Douglas Sent: Wednesday, November 21, 2001 3:47 PM To: "CODE400-L@midrange. com" ; "Reeve Fritchman" Subject: RE: Network connection Reeve, We had the same issue here with a programmer who worked remote. We use a STRCODE server session, with a home-grown command & CL program setup to retrieve the IP address and fill in the Remote Location Name with this retrieved IP address. It would as you pointed out retrieve the internal address rather than the external. So we had to add a parm to our command to allow the IP address to be manually keyed instead of retrieved. It works, but the programmer must find this external IP address and key it in manually (quite a pain). It would be nice if there was some other way... Anyone have a better way? Doug Edwards ______________________________ Reply Separator _________________________________ Subject: Network connection Author: "Reeve Fritchman" <SMTP:reeve@ltl400.com> at ALLTELEXCH Date: 11/21/01 1:20 PM I'm having trouble starting a CODE/400 server when working through my network connection. I have two systems connected to a Netgear RT314 Gateway Router (no ROTFLYAO, please) and then into a cable modem up to the 820 via a firewall. The RT314 provides NAT and some firewall protection. The IP address seen by the RT314 is not fixed (today it's 65.34.yada.yada); within the LAN, the RT314 is 192.168.0.1 and the other systems are ".2" and ".3". When I use a dial-up connection (without the RT314), everything works fine (because CODE/400 knows my IP address). I think this shows the server is not causing the problem. I assume the RT314 is the issue. The iBox is giving me EVF4000, "A remote host refused an attempted connect operation." (3425). I'd be grateful for any help... Thanks, Reeve _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. --
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.