HP3000-L Archives

June 1995, Week 3

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:
"James B. Byrne" <[log in to unmask]>
Reply To:
James B. Byrne
Date:
Mon, 19 Jun 1995 20:01:17 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Many thanks to those of you who responded with advice and suggestions.  As of
today we have achieved a minor miricle.  We actually managed to have both our
remote site connect to the HP3000 via the DTC based X.25 card.  Unfortunately
there remain a large number of details and problems which need to be resolved
before we can make the switch over.  I have a few more questions which I would
appreciate answers to.  Please respond via e-mail if you can provide any part of
this information.
 
1.      How does the DTC resolve incoming addresses?  We were able to connect but
only as a non-nailed terminal.  We have a requirement that the incoming calls go
to a predetermined set of LDEV's, which we have defined as being 1501 through
1508.  What format does the DTC expect the calling packet to have in its
address? "########DLDEV#"? or "########,LDEV#", or perhaps "########,Dldev#", or
even "########DDEVNAME"? or what?
 
2.      We still cannot get out outgoing printer connect requests to be answered
by the Gandalf MUX.  This may not be the HP's fault as we have detected that the
printer is attempting to connect from the MUX! Don't ask me why, that's
tomorrow's problem.  However, if anyone out there is running a printer off of a
remote PAD I would appreciate configuation details.
 
Again, thanks for the help, especially to Olaf Traustason.
 
Jim

ATOM RSS1 RSS2