| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 777.1 | | MRJINX::PHILIP | And through the square window... | Fri Jun 02 1995 16:29 | 8 |
| Rodger,
We do nothing to supplement the data stream from the users terminal,
are you sure that the terminal has not been reset so that it transmits
only a line-feed instrad of a carriage-return/line-feed pair?
Cheers,
Phil
|
| 777.2 | Actually a DECserver setup issue...Help! | 34823::HAYES_J | | Wed Jun 07 1995 08:11 | 10 |
| We are experiencing this same problem with the missing <CR>. We did
track it down to a DECserver 700-16 setup problem. Unfortunately, we
haven't been able to fix the problem. We are also having problems with
figuring out the modem control on the port side.
Can anyone point me at where I can find the correct setup for a
DECserver 700-16 for use with PCM (must be with telnet!)?
thanks,
John Hayes
|
| 777.3 | | ZEDAR::simon | Simon Jackson 830 x3879 | Wed Jun 07 1995 13:00 | 5 |
| Hmm,
we use DECserver 90M servers in our test area, but I shall try
to get hold of a DECserver 700 at see if I can simultate the problem.
Cheers Simon...
|
| 777.4 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri Jun 09 1995 01:07 | 11 |
| John,
The last time I dinked with a 700 the default TELNET characteristics
looked fine to me. Get into the server and tunr privs on and do
Local> SHOW PORT x TELNET
and post the results. it would be helpful to see the output of the
command from when it's working correctly and when it's broken.
Regs,
Dan
|
| 777.5 | update - terminal server rev problem found | MUZICK::KUNG | | Tue Jun 13 1995 00:02 | 13 |
| A quick update from Jim Kingsley/John Hayes:
The terminal server they were using was found to be 2 revs behind
software-wise. Jim is off getting the ts upgraded and then trying
to get it work with PCM again. He believes that is probably it,
and that this issue is not with PCM but with the terminal server
swe. He also suggested that, since the log and console messages
were both jumbled, it's a safe guess that whenever this happens,
it's probably not PCM but the source of the messages that's causing
these problems.
Jim will keep us posted. Thanks again to PCM engineering and support
team for keeping up with this one!
|
| 777.6 | Update- STILL doesn't work... | POBOX::HAYES_J | | Thu Jun 15 1995 03:46 | 130 |
| We continue to have problems finding the right combination to make our
DECserver 700-16 work. Yes, this is not a PCM problem (I can shutdown
PCM and telnet into the port and reproduce the same problem via telnet),
but since PCM needs it to work anyway...
The 2 problems (which may be related) are:
1) Flow control, the terminal server buffer overflows and we get the
overflow character, "^G" (we can reproduce this at will with pg).
2) When we reboot a system, we loose the <CR> (regardless of newline
settings) and get the stair step.
Our original call with CSC was opened 20 days ago!!!!!!!!!!!
HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
John Hayes
pobox::hayes_j
DTN 474-5068
Here is the setup info from our DECserver 700-16
Local> show server
Network Access SW V1.5 for DS700-16 BL95-33 ROM V4.0-0 Uptime: 0
00:14:17
Address: 08-00-2B-BB-67-F1 Name: TEK1CM01 Number: 0
Identification:
Circuit Timer: 80 Password Limit: 3
Console Port: 1 Prompt: Local>
Inactivity Timer: 30 Queue Limit: 100
Keepalive Timer: 20 Retransmit Limit: 8
Multicast Timer: 30 Session Limit: 64
Node Limit: 200 Software: WWENG2
Service Groups: 0
Enabled Characteristics:
Announcements, Broadcast, Dump, Lock
Local> show port 7
Port 7: (Remote) Server: TEK1CM01
Character Size: 8 Input Speed: 9600
Flow Control: XON Output Speed: 9600
Parity: None Signal Control: Disabled
Stop Bits: Dynamic Signal Select: CTS-DSR-RTS-DTR
Access: Remote Local Switch: None
Backwards Switch: None Name: PORT_7
Break: Local Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: Telnet Default Menu: None
Preferred Service: None
Authorized Groups: 0
(Current) Groups: 0
Enabled Characteristics:
Failover, Input Flow Control, Lock, Loss Notification, Message
Codes,
Output Flow Control, Verification
Local> show port 7 telnet
Port 7
Profile: Character
Echo: Remote Newline From Term: <CR>
Toggle Echo: ^E Newline From Host: <CRLF>
Binary: Disabled Newline To Term: <CRLF>
Xmit Char Size: 8 Newline To Host: <CRLF>
Rcv Char Size: 8 Input Flow Control: Enabled
Signal Req: Enabled Output Flow Control: Enabled
IP: +s +f ^Y Verification: Enabled
SYNCH: +s -f ^X Switch Character: Enabled
AYT: -s -f ^T Quote: None
AO: -s +f ^O
EOR: -s -f None
BRK: -s -f None
Local> show port 7 counters
Port 7: (Remote) Server: TEK1CM01
Seconds Since Zeroed: 1365 Local Accesses: 0
Framing Errors: 6 Remote Accesses: 2
Parity Errors: 0 Input Characters: 5854
Overrun Errors: 95 Output Characters: 183
Local>
Local> show port 7 status
Port 7: (Remote) Server: TEK1CM01
Access: Remote Current Service:
159.198.160.25
Status: Connected Current Node:
159.198.160.25
Sessions: 1 Current Port:
1648
Input XOFFed: No Output Signals: DTR RTS
Output XOFFed: No Input Signals: DSR RXD
Local> show port 7 telnet server
Port 7
Xmit Char Size: 8 Newline From Term: <CRLF>
Rcv Char Size: 8 Newline From Host: <CRLF>
IP: None Newline To Term: <CRLF>
AYT: None Newline To Host: <CR>
AO: None EC: None
EOR: None EL: None
NOP: None BRK: Break
Echo Negotiation: Initiate
|
| 777.7 | Cross post to term servers | ZEDAR::simon | Simon Jackson 830 x3879 | Thu Jun 15 1995 12:49 | 8 |
| John,
Im not giving up on this one, but have you cross posted it in
the Terminal Server notes conference. you will get the boys in the
know for the terminal server involved as well.
By the way what rev of SW is running on the term server?
Cheers Simon...
|
| 777.8 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Jun 15 1995 21:28 | 6 |
| per -2.
>Network Access SW V1.5 for DS700-16 BL95-33 ROM V4.0-0 Uptime: 0
> 00:14:17
|
| 777.9 | DECserver 700 Telnet configuration problem? | POBOX::KINSLEY | Nothing endures but change | Fri Jun 16 1995 05:26 | 21 |
|
RE: 777.7 cross posting??
This note stream was cross posted in the Terminal Servers notesfile # 2496
last night -- now that we believe we have isolated the problem.
After quite a bit of testing we have isolated the problem to the terminal
server. We can reproduce the behavior with a terminal directly attached to
the DS700-16 port. In addition the PCM logfile has the same scrambled data
stream as a console window.
I have worked with someone from the CSC Terminal Server support team.
They informed us that the DS700-16 was running old software V1.3 and
suggested/insisted on upgrading the software as a necessary problem solving
step. We upgraded last night to V1.5 of the software which did not solve
the problem. We entered the new notes last night after we finished an
upgrade and ran some tests.
Any telnet/DS700 configuration experts out there?
jk
|
| 777.10 | DS700 data overrun problem solved | POBOX::KINSLEY | Nothing endures but change | Sat Jun 24 1995 21:45 | 13 |
| Finally got this problem solved by acquiring a DS700 patch from the CSC.
The first fix/solution from the CSC was an upgrade from Network Access
Server (NAS) V1.3 to NAS V1.5 BL33 via a Flash RAM.
When this did not solve the problem the Terminal Server team found an April
1995 version of the NAS software. We acquired the new software on 6/22/95
Network Access SW V1.5 for DS700-16 BL95-34. This eliminated the buffer
overrun error condition.
Simple problem -- to bad it took (1 month from initial call to the CSC) so
long to find out that the latest version of the NAS software solved the
problem.
|