We have a customer who has stores connecting through the internet with
AccuTerm telnet and they are having problems with dropped connections.

If they leave the terminal up and running but they are not using it, the
connection will drop and they have to hit the Reconnect button in AccuTerm.
Then they get a message similar to the following some times.

*** Nailed port 8068 failed to connect: PIB 68 already active ***

I know that flaky Internet connectivity is the real problem and I know how
to clear the port, but are they any good tricks to implement to minimize or
eliminate this situation. I spoke with Pete at AccuSoft and he recommended
enabling the keep-alives, but then he went on to say that D3 does not really
work with this option.

Thanks,

Steve
--
www.perfectionsoftware.com

We have better luck with just regular old floating telnet.
Place "TRAP DCD EXIT" in the user coldstart.
For each telnet port session use "DCD ON".
Copy the "OFF" command to ":OFF".
Change "OFF" to a basic program that checks if a telnet session then "EXIT"
else ":OFF".
Additionally add a user call "EXIT" or "BYE" that has the new "OFF" command
as attribute 12.

Additionally check what you have "timeout" set for, user mode "u6b".
If you are using "timeout" and have it set to something other than zero (0),
that may be your problem.

Steven S wrote:

How do you determine if it is a Telnet port?

Steve
--
www.perfectionsoftware.com
"System Admin" <lsweesy (AT) acsalaska (DOT) net> wrote

Steven S wrote:
Acutally, no it's not. This is one of the big reasons I've been going
to Mandrake Linux and the Gnome telnet client. I've got remote
locations setup the same as you, and had the same problem. I've also got
numerous Accuterms telneting into the same nailed ports locally thru a
local lan (no internet). And I have dropping problems with them, the
same as the remote locations. It seems to be a timeout issue. I can't
tell you if it's a Windows or AccuTerm issue, but the problem is real.
If AccuTerm sees fairly constant activity, it doesn't drop. But if it's
just setting at TCL, for example, it usually does drop, sooner or later.
And according to conversations I've had with Pete, the stay-alive
doesn't work with nailed telnet ports.

Now, against this background, Gnome telnet clients on Mandrake linux
*never* drop a connection because of time-outs. If they drop, it really
was because of internet connection issues. Locally, they just never
drop. Period. I've discussed this behavior with Pete, and his response
was that the Gnome telnet client must be "cheating" some how. My
response was that he'd better learn how to "cheat". Personally, I'd love
to see a linux version of AccuTerm.

Art

Hello,

We also are constantly getting terminals dropping on d3/AIX using
nailed ports "d3 -<pib>". We used to used DG/d3 where we could just
nail TCP ports to pick ports and we never experienced this problem.

We use ViaDuct / ProComm Plus. If there is some voodoo config you
figure out how to stop these types of disconnects I'd love to know

Thanks,

-Adam


On Thu, 11 Sep 2003 21:11:50 GMT, Art Martz <artmartz (AT) triad (DOT) rr.com>
wrote:

ashelley (AT) inlandkwpp (DOT) com wrote:
Hmmmm, AccuTerm drops, Viaduct drops, Gnome/linux doesn't. Would seem
to point to a windows issue. Surprise, surprise.

Art

If your are on D3/NT do a "dev-list t"

"Steven S" <srs (AT) perfectionNoSpamsoftware (DOT) com> wrote

Two things you can check:

1. many 'always on' connections aren't on all of the time. Many sense
periods of inactivity and close and reopen on further activity. This is
especially true with DSL connections. Many have 'logging' options you can
enable to watch the connection. You can try also connecting with the windows
telnet client and seeing if it drops at the same time. If that's the case
you can set-up a script on the PC that fires off every x minutes to keep the
connection up.

2. One of our clients just had a lot of problems with a Broadcom Gigabit
card after loaded SP4 on Win2K. Swapping the card out for a different brand
resolved the issues.

Good luck
Colin Alfke
Calgary, Alberta

"Steven S" <srs (AT) perfectionsoftware (DOT) com> wrote

Now that you mention Via Duct, this situation rings a bell. One of my
customers running on D3/Linux using Via Duct was having a similar problem.
Sessions would drop not only during periods of inactivity, sometimes while
they were doing data entry. We had the ports configured correctly and all
that jazz.

We got Via Systems involved. Geez, it was a couple of years ago. I seem to
remember it was a networking problem, perhaps having to do with DHCP and IP
addresses getting reassigned too frequently or something along those lines.
I'm sure some of the networking experts out there can shed some light on the
subject.

Anyway, the guy who maintained their in-house network made a change or two
and the problem went away.

--

Jeffrey Kaufman
Key Data Systems Group
www.keydata.us
559-432-3832
559-432-4657 fax

Western Pacific Supply
www.westpacsupply.com
888-WestPac

<ashelley (AT) inlandkwpp (DOT) com> wrote

"Steven S" wrote in message > I know that flaky Internet connectivity is
the real problem and I know how
We have a site which will telnet into our system with AccuTerm. Initially
we had the same problem. We are both on DSL. We are on D3/Linux. Our
ports for the remotes are floating, not nailed. After we checked the
keep-alive option, we have not had any problems. I should have posted my
problem here at the beginning. It would have saved some time. But
everything is working fine, at least for now.

Dwain Camp
Fort Worth