T.R | Title | User | Personal Name | Date | Lines |
---|
3441.1 | | LAVC::CAHILL | Jim Cahill | Tue Feb 18 1997 10:33 | 22 |
| > they are just terminating the local session, (to port 32)
If I read your description of the configuration correctly, the session to
port 32 is a remote session.
> The connection from the remote port to the LAT service remains active.
> When another user connects to this local LAT service, they are logged
> straight into the remote persons account. Due to the nature of the work
> being done, inactivity logout is not an option. But I need a way of
> terminating the remote session, should the local one fail.
Now I'm getting confused. When they're done using the "local LAT service",
why can't they simply log out of that port, which I believe is port 31?
I'm not sure if we can come up with something which (1) allows users to
"connect to another LAT service of there choice" yet (2) automatically
logs them out of port 31 *and* terminates the remote session when they
terminate the local session.
This is a rather unique configuration.
Jim
|
3441.2 | Finger and Brain co-ordination problems | KERNEL::FREKES | Like a thief in the night | Tue Feb 18 1997 10:46 | 33 |
| Jim
Sorry about that, let me make myself clearer. The configuration is
essentially the same as the one below.
User
______|________________
__|__
| Server1
---|
|
|
Modem Link
|
|
__|__
| Server2
|---|
---------|-----------|----
|
Host
The user establishes a LAT session with the port on server1, via a LAT service.
He gets the local prompt of server2. From here he establishes an new LAT session
to the host. If his session between himself and server1 is terminated, the
session he was using between server2, and the host remains active. The next
user comes along, and gets the same session.
This is what we are trying to resolve.
Steven
|
3441.3 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Tue Feb 18 1997 10:59 | 12 |
| RE: .2
Is the modem link "nailed up" or is it initiated each time the LAT service
to server 1 is initiated? If you can use the modem control signals at server
2 to indicated that the LAT service at server 1 went down, this might be a
silution. This requires modem control to be used on both server 1 and server
2.
Regards,
Dave
|
3441.4 | Already using signal control | KERNEL::FREKES | Like a thief in the night | Tue Feb 18 1997 11:26 | 55 |
| Jim
As you can see they are both already using signal control, in the
absence Modem control
This is the port on Server1.
Port 32: (Remote) Server: DS900TM
Character Size: 8 Input Speed: 9600
Flow Control: XON Output Speed: 9600
Parity: None Signal Control: Enabled
Stop Bits: Dynamic Signal Select: CTS-DSR-RTS-DTR
Access: Remote Local Switch: None
Backwards Switch: None Name: PORT_32
Break: Local Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: LAT Default Menu: None
Dialer Script: None
Preferred Service: None
Authorized Groups: 0, 10
(Current) Groups: 0, 10
Enabled Characteristics:
Autoprompt, Broadcast, DTRwait, Inactivity Logout, Input Flow Control,
Loss Notification, Output Flow Control
This is the port for server2
Port 31: TEST Server: DS900TM
Character Size: 8 Input Speed: 9600
Flow Control: XON Output Speed: 9600
Parity: None Signal Control: Enabled
Stop Bits: 1 Signal Select: CTS-DSR-RTS-DTR
Access: Local Local Switch: None
Backwards Switch: None Name: PORT_31
Break: Local Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: LAT Default Menu: None
Dialer Script: None
Preferred Service: None
Authorized Groups: 0
(Current) Groups: 0
Enabled Characteristics:
DSRlogout, Inactivity Logout, Input Flow Control, Output Flow Control
Steven
|
3441.5 | | LAVC::CAHILL | Jim Cahill | Wed Feb 19 1997 11:32 | 16 |
| The port characteristic "DSRlogout" causes the port to be logged out when
DSR is dropped. If you enable DSRlogout on port 31 and the modems are
configured to drop DSR when CD drops, a user terminating a session between
himself and server1 should:
(a) cause the modem on server1 to drop CD, which should...
(b) cause server2's modem to drop CD (and DSR!) which in turn should...
(c) cause server2 to log out that port (port 31)
If this isn't the behavior you see after enabling DSRlogout on port 31,
it's time to start watching modem signals using either a breakout box or
the MONITOR PORT STATUS command.
Jim
|
3441.6 | Wrong cables | KERNEL::FREKES | Like a thief in the night | Thu Feb 20 1997 02:56 | 9 |
| Jim
Thanks. I had tried that, and it was not working. When you suggested
that I ,ay need a break-out box, I thought that perhaps the cables, and
adapters I was using were not correct. Changed those around, and it all
work fine.
Regards
Steven
|