Re: Connecting CA Express via Internet to AS/400

["Gary Kuznitz " <docfxit@xxxxxxxxxxx>]

Thanks to all of you I figured it out.

In WinRoute Settings, Interface Table, clicking on the ethernet adapter and 
then properties I selected the option in Settings "Perform NAT with the IP 
address of this interface on all communications passing through."  I then 
disconnected CA and re-connected CA (since it isn't smart enough to Auto-
connect even though the option is checked) and it worked.  I now have a 
firewall up and remote signon to the 400 through the internet.

Thank you,  Thank you, Thank you all,

Gary Kuznitz


On 19 Nov 2000, at 9:40, MIDRANGE-L@midrange.com wrote:
> Thanks Larry,
> 
> How did you know I needed those? :-)
> 
> That's great.  In WinRoute I configured port mapping for ports:
> 23
> 446-447
> 449
> 5555
> 8470-8480
> all with a destination of 192.168.1.1 (which is the AS/400)
> 
> I'm getting an error from CA CWBC01003 - Winsock error, function
> returned 10060 that says:  "The address used for the AS/400 system was
> found, but connection to the AS/400 system failed.  Make sure TCP/IP
> has been started on that AS/400 system, and that the host servers have
> been started.  If this does not fix the problem,  verify that the IP
> address used to attempt the connection is correct for the AS/400
> system.  This address is logged in a previous message.  Verify TCP/IP
> address servers (Domain Name Servers) are configured correctly on this
> PC and have the correct address for this AS/400 system.  If the
> address is incorrect, check the HOSTS file on your computer for
> errors.  
> 
> I know TCP/IP is started.  I signon locally all the time.  And I have
> tried entering in the hosts file on the PC  the IP address with the
> 400 name and at a different test the IP address with the domain name. 
> (Which is the same only it has a .com at the end)
> 
> I have been waiting for IBM for 33years to put enough information in
> the error messages for someone to be able to follow a cookbook recipe
> to fix a problem.  Will it ever happen?  Maybe some day a third party
> will jump on the band wagon and realize there is money to be made to
> provide solutions to errors encountered on the 400.
> 
> I can't imagine  there is a server that needs to be started on the 400
> for remote TCP/IP connections that wouldn't be started for local Lan
> connections.  But obviously I am doing something wrong.
> 
> Thanks for all your suggestions.
> 
> Gary Kuznitz
> 
> On 19 Nov 2000, at 10:09, Larry Bolhuis wrote:
> > > for ports open, you need 23, 449, and about 5-6 in the 8000's (i
> > > don't have them handy just this minute).
> > 
> >   Here is the gory detail for the ports required.
> > 
> >  - Larry
> > 
> > When using Client Access over TCP/IP, the following Client Access
> > ports are required to have free access:
> > 
> > PC Function                 Server Name     Port Non-SSL    Port SSL 
> > Server Mapper               as-svrmap       449             449 
> > License Management  as-central      8470            9470 
> > Database Access             as-database     8471            9471 
> > Data Queues                 as-dtaq         8472            9472 
> > Network Drives              as-file         8473            9473 
> > Network Printers    as-netprt       8474            9474 
> > Remote Command              as-rmtcmd       8475            9475 
> > Signon Verification         as-signon       8476            9476 
> > Telnet (PC5250 Emulation) telnet    23              992 
> > HTTP Administration         as-admi >       2001            2010 
> > POP3 (MAPI)                 pop3            5010            --- 
> > Management Central  as-mgtc >       5555            5566 
> > Ultimedia Services  as-usf          8480            9480 
> > Network Drives              as-netd         *8477           --- 
> > File Transfer               as-tran         *8478           --- 
> > Virtual Print               as-vrtp         *8479           --- 
> > DRDA                        DRDA            446             --- 
> > DDM                         DDM             447             448 
> > AnyNet                      APPCoverTCPIP   397 (TCP and UDP) --- 
> > 
> > * These ports used only by 5763XK1.
> > 
> > If any of the above ports are restricted via a firewall or any other
> > mechanism, Client Access may fail to operate. For assistance with
> > configuring ports or working with a firewall beyond the above
> > information, contact the firewall provider or IBM Consult Line.
> > 
> > -- 
> > Larry Bolhuis
> > Arbor Solutions, Inc.
> > (616) 451-2500
> > (616) 451-2571 -fax
> > lbolhuis@arbsol.com
> 
> 
> 


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---