Re: Telnet sessions disconnecting -- Any Solution yet?

["Jim Franz" <franz400@xxxxxxxxxxxx>]

Carl - is your router or any firewall blocking ports?
Need port 53 for DNS.This is a list of common (not Client Access) ports
See Client Access home page for CA ports
7 (Echo)
21 (FTP)
23 (TELNET)
25 (SMTP)
53 (DNS)
79 (Finger)
80 (HTTP)
110 (POP3)
119 (NNTP)
161 (SNMP)
162 (SNMP Trap)

Check out this site - has lots of info on dsl setups. From main page select
"Routers" in left box and has specific Linksys info.
Also has a Tests & Tools section.
http://www.dslwebserver.com/

still looking for an answer (but my cable modem works fine & always has with
Client Access)
jim franz


----- Original Message -----
From: "Carl Galgano" <cgalgano2@ediconsulting.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, July 23, 2002 7:43 AM
Subject: RE: Telnet sessions disconnecting -- Any Solution yet?


Hi Jim:
Not sure if you saw my last post, that when I connect via IP address rather
then name to my AS400 it does not time out.  I have had an inactive session
connected now for about 6 hours.  Still going thru the same linksys/DSL
connection I spelled out in a prior post.
This is too weird.  Can anyone else out there verify or refute the idea that
connecting via a host name, rather than an IP address is a problem.
cjg

Carl J. Galgano
EDI Consulting Services, Inc.
550 Kennesaw Avenue, Suite 800
Marietta, GA  30060
(770) 422-2995 - voice
(419) 730-8212 - fax
mailto:cgalgano@ediconsulting.com
http://www.ediconsulting.com
AS400 EDI, Networking, E-Commerce and Communications Consulting and
Implementation
http://www.icecreamovernight.com
Premium Ice Cream Brands shipped Overnight

"You ain't gonna learn what you don't want to know" - rw

-----Original Message-----
From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]
On Behalf Of Jim Franz
Sent: Monday, July 22, 2002 9:23 PM
To: midrange-l@midrange.com
Subject: Re: Telnet sessions disconnecting -- Any Solution yet?


Carl - I think you would be the perfect candidate for IBM. They need resolve
this, even if another vendor's product is at fault. Just like all their work
mapping various printer data streams and documenting it, this is a good
thing to do. The following IBM Knowledge Base doc describes telnet timemark
and how to adjust.
http://www-912.ibm.com/s_dir/slkbase.NSF/7250f367f6396d2f86256a4f007973d5/4a
dccb91a24d9ed28625694900513857?OpenDocument&Highlight=0,keep,alive



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.