HP3000-L Archives

March 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stigers, Greg ~ AND" <[log in to unmask]>
Reply To:
Stigers, Greg ~ AND
Date:
Thu, 5 Mar 1998 10:23:32 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
Because I'm grasping at straws :-) If I can find a reasonable way to
make this work in the existing environment, life will be much easier,
for at least the rest of the week.

The application we support runs across a telnet connection, basically
displaying the data stream to a WinSocketed connection. We work fine,
going across our WAN to the 3K (our data center is in another state).
The vendor works fine, going across the data center's WAN. The client's
remote office, a company that everyone has heard of, can be counted upon
to fail at certain times of the day, and to work without fail at others,
connecting to their router, going thru their firewall with IP and port
translation (which they insist is not part of the problem), across their
nation-wide WAN, to their office on the opposite coast.

HPRC has performed a TCP and a link trace, and taken a memory dump, and
spent days analyzing the results (and I believe that they have really
gone above and beyond the call of duty here), to conclude that TCP and
inetd are doing their respective jobs, responding to everything it sees.
We are still working to analyze and have analyzed our traces on the
host's LAN segment and on the client's router, for the involved IP
addresses. The remote office is concerned about resolving this so they
can go live, and their parent company is involving us in daily
conference calls, insisting we resolve this immediately, either by
'fixing the HP' (insert unprintable remarks here), or rewrite the
application to use RPCs. Sure, no problem.

We already have a local consulting firm looking at our trace; they have
successfully resolved networking issues for us, and if any consultancies
on this list have experience with these particular technologies (Delphi,
VB, WinSock, TCP, telnet on the 3K, WAN connectivity), please notify me
offlist. In fact, if anyone else is doing something like this that
involve passing application data over a telnet connection across a WAN,
I would love to compare notes.

> ----------
> From:         Stan Sieler[SMTP:[log in to unmask]]
> Sent:         Wednesday, March 04, 1998 9:14 PM
> To:   Stigers, Greg  ~ AND
> Subject:      Re: [HP3000-L] DTC TelnetAccess
>
> Hi,
>
> > a DTC48. Assuming the desire to telnet to the 3K across a WAN, could
> the
>
> Why not just telnet directly to the HP 3000?  (Bypassing the DTC?)
>
> in-bound telnet seems to work adequately as of 5.5 (at least on PP3).
>
> --
> Stan Sieler
> [log in to unmask]
>
> http://www.allegro.com/sieler.html
>

ATOM RSS1 RSS2