Hi Bill,
I've seen similar problems with DataStage, caused by firewalls timing out
sessions for you.
If you can't change the firewall, not sure what the solution would be.
Regards
- Chris Thornton
_
Chris Thornton DataStage
Bill,
I stay on line to an external Unidata 7.1 server all day long with AccuTerm.
Usually it is some setting on the OS that is closing the connection. Routers
can have timeouts also.
george
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-u2-
[EMAIL PROTECTED] On Behalf Of
You might check the firewall(s) between your workstation and the remote
server to check if they have a telnet timeout.
Bill Haskett wrote:
I have UniData 7.1 running on a local server in our network. I'm testing
UniData 7.1 on an off-site server. When I telnet in to the off-site server
I
: Re: [U2] UniData telnet
You might check the firewall(s) between your workstation and
the remote server to check if they have a telnet timeout.
Bill Haskett wrote:
I have UniData 7.1 running on a local server in our
network. I'm testing UniData 7.1 on an off-site server.
When I
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
I've had problems with the Windows Instrumentation Service holding
onto shared memory that prevented UD from starting - but worked OK with
a reboot. Try stopping that service and starting UD, then restarting
WIMS. I used Process explorer from www.sysinternals.com to find the
conflict.
Not sure
