|
Try to Traceroute from the internet to the AS/400. Also try to traceroute from the AS/400 to the internet. That should give you a clue as to what is going on. Denis Robitaille Directeur services technique TI 819 363 6130 SUPPORT Jour (EST) Daytime : 819-363-6134 En-dehors des heures (EST) After hour : 819-363-6158 Network Status : 819-363-6157 >>> sbalkaya@xxxxxxxxxxxxx 2004-10-22 06:57:28 >>> I have added Default route on my AS400 but nothing has changed Chris. Is there any other thing that i should take into consideration ? ----- Original Message ----- From: Chris Bipes To: 'Midrange Systems Technical Discussion' Sent: Thursday, October 21, 2004 11:48 PM Subject: RE: Connect via telnet to the internal AS/400 from the internet. Do you have a default route on your AS400 to your Linksys Router? I would first enable SSL for your AS400 Telnet server and open 992 not the unsecured 23. But either way, you will need to do one of the two: 1. have a default route to your Linksys router 2. NAT inbound at our Linksys router to your internal IP scheme. I would: ADDTCPRTE RTEDEST(*DFTROUTE) SUBNETMASK(*NONE) NEXTHOP(LINKSYS router IP address) -----Original Message----- > Hi everybody > > I am not so sure whether this is the right platform for my question but i > hope i will get your help and answers. > > We have an AS/400 on our internal network. We can connect to it via telnet > on the internal network, from any client. We have a DSL internet connection > with a single external IP and a Linksys router. We have forwarded TCP port > 80 on the Linksys router to a Windows Web Server and it works perfectly. > > We similarly want to be able to connect via telnet to the internal AS/400 > from the internet. We have forwarded TCP port 23 on the Linksys router to > the AS/400 , but unable to connect. We get the message "Could not open > connection to the host, on port 23: Connect Failed". > > Any help would be greatly appreciated. -- 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. -- 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. *** eSafe scanned this email for malicious content *** *** IMPORTANT: Do not open attachments from unrecognized senders ***
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.