| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 256.1 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Thu May 22 1997 14:37 | 6 |
|
The AAJ stuff shows that SSU is trying to enable multiple sessions, but
the other end isn't recognizing the protocol. Do you have the protocol
appropriately switched on ?
/Eric
|
| 256.2 | ?? | QUAKKS::DWORSACK | | Fri May 23 1997 11:53 | 5 |
| how tho check ???
it says default protocal. what could it read ?
jim
|
| 256.3 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Fri May 23 1997 16:03 | 14 |
|
I'm talking about the TDSMP (Terminal Device Session Management Protocol) which
is the basic protocol that SSU uses for switching between sessions.
The sequence <ESC>!AAJ or something like that would be the initial directive
to enable multiple sessions.
So make sure "multiple sessions" are enabled at both ends (the FLOP end
and the SSU end) and that nothing is filtering out escape characters.
Any other readers here that use FLOP that can lend this person a hand ?
I was an SSU developer but I don't run FLOP !
/Eric
|
| 256.4 | Use SSU instead of server | GIDDAY::GILLINGS | a crucible of informative mistakes | Sun May 25 1997 20:45 | 71 |
| I use FLOP (in fact, I'm running on it right now). I don't use the
terminal server as the other end, I prefer to use an OpenVMS system.
The main advantage is that you can enable virtual terminals under
OpenVMS and thereby reconnect to your sessions after losing the
phone line. You can also be sure you're running the right protocol.
By chance, I still have the transcript of my initial connection in
a scrollback, so here it is:
CONNECT 14400 EC/V42BIS
# [server password]
Username>
Username>
Username> gillings [authentication]
Password>
Local -450- Attempting to authenticate user: [email protected]
Local -451- Authentication successful
Network Access SW V2.0 for DS700-16 (BL10C-40)
CSC DS700
(c) Copyright 1996, Digital Equipment Corporation - All Rights Reserved
Local> c xara
Local -010- Session 1 to XARA established
Unauthorized access prohibited
Username: GILLINGS
Password:
Welcome to OpenVMS AXP (TM) Operating System, Version V6.1 on node XARA
Last interactive login on Wednesday, 21-MAY-1997 10:34:14.85
Last non-interactive login on Monday, 26-MAY-1997 00:59:57.12
You have 10 new Mail messages.
Terminal is VT300 series, 80 x 24
XARA GILLINGS$
XARA GILLINGS$
XARA GILLINGS$
XARA GILLINGS$ ssu
XARA GILLINGS$
The blank line is the terminal switching from being the LAT session
into the first SSU session. By symbol "ssu" is defined as:
SSU == "$SSU -loginothers -nologout -nodisable"
Image Identification Information
image name: "SSU"
image file identification: "SSU V2.0"
link date/time: 30-NOV-1993 09:42:50.56
linker identification: "A10-62"
On this system, I have TTY_TIMEOUT set quite high
TTY_TIMEOUT 320000 900 0 -1 Seconds D
nearly 4 days. That allows me to have all my FLOP sessions "hibernate"
over the weekend and reconnect by connecting back to the disconnected
LAT session.
For most terminal servers I think the command to activate TDSMP is
ENABLE MULTI, but since I never use it I can't be sure.
John Gillings, Sydney CSC
|
| 256.5 | getting closer ?/ | QUAKKS::DWORSACK | | Tue May 27 1997 10:13 | 10 |
| >So make sure "multiple sessions" are enabled at both ends
i tried that option on the terminal server, but all i got when
i opened another session/window was another window to the decserver
prompt... i usually get the window straight to my workstation.
JOHN, SHOW ME A SHOW PORT FROM YOUR DECSERVER.
thanks guys,,, johns show port should help me..
|
| 256.6 | | ACISS2::LENNIG | Dave (N8JCX), MIG, @CYO | Tue May 27 1997 15:05 | 11 |
| If you enable sessions to the terminal server (as opposed to a host
with the SSU utility), then opening another session WILL give you
another terminal server prompt...
Oh wait a minute... with the later versions of FLOP, I got Jeff to
add support for service names; are you specifying this when you
start FLOP? Perhaps your terminal server doesn't support this.
I agree with .-?; use SSU on your host rather than in the server.
Dave
|
| 256.7 | still broken... | QUAKKS::DWORSACK | | Wed May 28 1997 11:37 | 52 |
| > I agree with .-?; use SSU on your host rather than in the server.
this IS what i do...
ok, i'll restate the problem.
i call a bank of modems, which are connected to a terminal server
(very simular to watn)... then i connect to netway (again same as
watn). then i telnet to my workstation in my cube, and login, and
do ssu == "$SSU.EXE -NOLOGOUT -LOGINOTHERS -NODISABLE"
then if i go to my flop window and select
"Create new DECterm session" i have another window directly to my
workstation (not the terminal sever).
i think my problem is stated a couple back,
>So make sure "multiple sessions" are enabled at both ends (the FLOP
>end
>and the SSU end) and that nothing is filtering out escape characters.
but i cant seem to figure what characteristic i'm missing to keep
it from filtering out the esc sequence... :-(
John Gillings did give me a show port, but i cant seem to figure
how to change my protocol on the port...
ive also tried passall and pasthru as session characteristics, but no
help.
puzzled ???
Port 4: gillings Server: CSCDS700
Character Size: 8 Input Speed: 115200
Flow Control: CTS Output Speed: 115200
Parity: None Signal Control: Enabled
Stop Bits: Dynamic Signal Select: CTS-DSR-RTS-DTR
Access: Dynamic Local Switch: None
Backwards Switch: None Name: PORT_4
Break: Disabled Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: LAT Default Menu: None
Dialer Script: None
Preferred Service: None
Authorized Groups: 57
(Current) Groups: 57
Enabled Characteristics:
Authentication, Dialup, DSRlogout, Inactivity Logout,
Input Flow Control, Message Codes, Output Flow Control, Password,
PPP,
SLIP, Verification
|
| 256.8 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Thu May 29 1997 15:04 | 20 |
| watn). then i telnet to my workstation in my cube, and login, and
do ssu == "$SSU.EXE -NOLOGOUT -LOGINOTHERS -NODISABLE"
The above won't start ssu, it merely defines the symbol ! You then need
to use the symbol.
As for your question about how to enable the protocol, the only two ways
I know are for ssu and for dec terminal servers. ssu normal enables
the protocol if you use the symbol you defined up above, or merely start
ssu with
$ mcr ssu
On terminal servers, you say
set port multi enable
/Eric
|
| 256.9 | thanks... | QUAKKS::DWORSACK | | Thu May 29 1997 16:15 | 19 |
| >The above won't start ssu, it merely defines the symbol !
eric, i really thank you for your time in here, but i was just
showing the symbol so you ddidnt have to ask me what qualifiers i use
in you next note !!
>As for your question about how to enable the protocol, the only two ways
>I know are for ssu and for dec terminal servers. ssu normal enables
>the protocol if you use the symbol you defined up above, or merely start
>ssu with
but as i said, i really dont want multi sessions from the lat box !!
i want the terminal server to pipe the mulitsessions THRU its box, so
i have multi sessions between my server on my OFFice box and the
vaxstation running flip at home...
again, i've tried all kinds of passthru and passall commands on the decserver
but i still get those characters when i run ssu on the server at my office.
when i do multi enable(like eric mentioned before) i do not get the garbage
characters, and then i get multi sessions from the lat box.... SOMTHING is
not alowing those to pass back to my vaxstation at home ... sigh...
|
| 256.10 | | ACISS2::LENNIG | Dave (N8JCX), MIG, @CYO | Fri May 30 1997 13:58 | 19 |
| You mentioned telnet in the final hop.
Make sure the telnet setup is fully transparent.
(Don't ask me what to check, I don't know.)
BTW, you don't indicate where the your node vs the dial-in are, but
given a major chuck of the US is all on one extended LAN, it might
be possible for you to enable the right group codes on your system
to allow it to be seen by the terminal server you are dialing into,
thus removing the need for all the extra connects/telnets/etc.
The terminal server output you posted in .0 doesn't show the group
codes enabled for that server; you'll need them to try this out.
The output in .0 also would seem to indicate (though you'll need to
look at SHOW SERVER output to confirm) that it already has TCP/IP
enabled on it. If so, you should be able to telnet directly from the
dial-in terminal server to your node without the intervening hops.
Dave
|