|
Rob, In the case of Client Access 5250, no it's not just telnet. There are other ports CA uses when you start a 5250 session. Now I believe some of the other 5250 emulation products do use only port 23-telnet, but don't hold me to that. Charles Wilt iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx > Sent: Wednesday, January 19, 2005 10:15 AM > To: Midrange Systems Technical Discussion > Subject: Re: RE: RE: Accessing AS400 Through Port Redirection > > > Isn't 5250 merely telnet, in this case? Isn't that on the > standard port > 23? Or does not Linksys support redirection of port 23? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > daparnin@xxxxxxxxxxxxxxxxxx > Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx > 01/19/2005 10:08 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > midrange-l@xxxxxxxxxxxx > cc > > Subject > Re: RE: RE: Accessing AS400 Through Port Redirection > > > > > > > > > > > There seems to be some confusion as to how you are attempting > access (web > browser, Client Access, etc). I've got a Linksys router that > does FTP > port > redirection to a PC-based ftp server. The router recognizes the FTP > request and automatically redirects to the designated > internal IP address. > A 5250 session is not FTP or HTTP which typical come in on > standard ports > so it won't redirect it. That's why you need to specify a > port. You can > *open* a port to the AS/400 but you will have to specify it when you > connect. > > If you are trying to connect with a web browser and set up HTTP port > redirection to the AS/400 I don't think that would work > because that would > be more like using the AS/400 as a HTTP server which isn't > really what you > want. > > Dave Parnin > Nishikawa Standard Company > Topeka, IN 46571 > daparnin@xxxxxxxxxxxxxxxxxx > > > > > > Vernon Hamberg > <vhamberg@xxxxxxxxxx To: Midrange > Systems Technical Discussion > t> <midrange-l@xxxxxxxxxxxx>@SMTP@CTB > Sent by: cc: > (bcc: David A > Parnin/Topeka/NISCO/SPCO) > midrange-l-bounces@m Subject: > Re: RE: RE: > Accessing AS400 Through Port Redirection > idrange.com > > > 01/19/2005 08:01 AM > Please respond to > Midrange Systems > Technical Discussion > <midrange-l@midrange > .com> > > > > > > It was not clear that you are specifying the external port > when you try to > connect to this IP address from the outside. You must put > :4000 after > the IP address, otherwise there is nothing to forward through > the router. > > http://yourexternalip:4000 > > If you want to come in with Client Access, there is a whole > raft of ports > you need to open up. The VPN suggestion is more secure. > LinkSys makes some > nice VPN routers/appliances that can also do port redirection to some > extent, if needed. You either need a client on the remote > computers or set > up a VPN "dialup" connection in Windows. > > HTH > Vern > > At 06:28 AM 1/19/2005, you wrote: > >Hi Mike > > > >I already have the standard external ports, (80, 21, 23, > etc) mapped to > >the relevant servers within the network and they work fine. I have > always > >been led to believe that mapping alternative ports to these ports on > >different servers is fine but it requires the external port to be > >specified (which I don't mind doing). > > > >I started looking at the redirection to port 80, purely > because I thought > >it would be the easiest to test - a different web page to that of my > >normal web server - figuring that if I could access a web page on the > >AS/400 then it should be fairly straight forward to access > an interactive > >session with Client Access or Mocha TN5250 as the emulator. > > > >I will double check the default route when I get back home on Friday. > > > >Thanks > > > >Jonathan > > > > > > > >-----Original message----- > >From: "Mike Silvers" MSilvers@xxxxxxxxxxx > >Date: Wed, 19 Jan 2005 12:17:50 +0000 > >To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx > >Subject: RE: RE: Accessing AS400 Through Port Redirection > > > > > Ok -- two things -- first -- a web page is not required > to sign on to > > > the 400. Second, from what you described, the external > traffic going > to > > > the web server originates from port 4000 in the external > world. If > you > > > would like the web page to be displayed to the outside world, the > > > external port should be port 80. So -- there should be > no redirection > > > going on. The router should be set to allow port 80 to > pass thru to > > > 192.168.0.100. > > > > > > If you would like to have remote access, I would > recommend one of two > > > ways. The first is Client Access with SSL encryption. > The second way > > > would be a VPN to your network and sign on using either > Client Access > > > (no SSL) or Rumba. > > > > > > Mike > > > > > > -----Original Message----- > > > From: midrange-l-bounces@xxxxxxxxxxxx > > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > Jonathan Mason > > > Sent: Wednesday, January 19, 2005 7:05 AM > > > To: Midrange Systems Technical Discussion > > > Subject: Re: RE: Accessing AS400 Through Port Redirection > > > > > > Hi Mike, > > > > > > No, I use my registered domain address which gets the > request to the > > > router. The AS400 is on a private address, 192.168.0.100, and the > > > router redirects port 4000 to 192.168.0.100:80 > > > > > > Ultimately I want to be able to sign on to the AS400 over > the internet > > > when I'm working away from home - which happens a lot these days. > > > > > > All the best > > > > > > Jonathan > > > > > > -----Original message----- > > > From: "Mike Silvers" MSilvers@xxxxxxxxxxx > > > Date: Wed, 19 Jan 2005 11:40:13 +0000 > > > To: "Midrange Systems Technical Discussion" > midrange-l@xxxxxxxxxxxx > > > Subject: RE: Accessing AS400 Through Port Redirection > > > > > > > When you are trying to access the web page from the > external world, > > > are > > > > you using the url: http://ipaddress:4000/ ? > > > > > > > > -----Original Message----- > > > > From: midrange-l-bounces@xxxxxxxxxxxx > > > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > Jonathan Mason > > > > Sent: Wednesday, January 19, 2005 6:06 AM > > > > To: Midrange-L > > > > Subject: Accessing AS400 Through Port Redirection > > > > > > > > I have a model 150 running v4r5 at home which is > connected to my > home > > > > network. I also have a cable broadband connection to > my network > with > > > a > > > > static IP address and a Draytek Vigor 2104p router > peforming NAT and > > > > Port Redirection. > > > > > > > > I want to be able to access the AS/400 over the > internet, and have > set > > > > up Port Redirection to map a specific port to the AS/400 (for > example > > > > Port 4000 being redirected to the AS/400's port 80). > However, when > I > > > > try to connect from outside of the network I get no > response from > the > > > > AS/400. Looking at the router, I can see that the Port > Redirection > > > has > > > > generated the correct address and port, but the AS/400 > doesn't pick > it > > > > up. > > > > > > > > Is there anything that needs to be configured on the > AS/400 that I > may > > > > have missed? I can see web pages from within the > network, but not > > > from > > > > the outside. > > > > > > > > Any suggestions would be most appreciated. > > > > > > > > Thanks > > > > > > > > Jonathan > > > > > > > > > > > > Jonathan Mason > > > > www.astradyne-uk.com > > > > > > > > -- > > > > 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. > > > > > > > > > > > > > Jonathan Mason > > > www.astradyne-uk.com > > > > > > -- > > > 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. > > > > > > > > >Jonathan Mason > >www.astradyne-uk.com > > > >-- > >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. > > > > > -- > 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. > >
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.