Firewalls generally don't care about the protocol involved as much as
behavior of certain ports. For example one might set a timeout of xx
seconds on everything above port 1024 and a specific 1 hour timeout on
port 23. Depends on the firewall itself, how tunable it is, and how
paranoid the administrator is. Same applies to the OS. Too many
variables. If you are hitting a server in another organization then you
are probably attaching to a NAT firewall which is then forwarding your
packets to some internal server with a non-routable address, perhaps
even through yet another firewall.
Bill Haskett wrote:
Jeff:
I seem to have found the problem. When I changed the "keepalive" values for
the UniData telnet server in UniAdmin > Network Services to 1000 / 1500000 /
5 (1sec / 20min / 5) and tested it it didn't work. So, I restarted UniData
and now it works. Here's what I got:
1 Demo (0)-> BPTEST CNT = 5 ; LOOP ; CRT TIMEDATE() ; SleepSecs = (CNT *
60) ; CRT "...now sleeping for " : CNT : " minutes..." ; SLEEP SleepSecs ;
CNT += 5 ; REPEAT ; END
[snip]
I wonder, is the firewall or O/S timeouts for telnet based on the service
running on port 23, or can the firewall or O/S tell if telnet is connecting
on any port?
Thanks, everyone, for the help. :-)
Bill
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
