[comp.sys.next] modem communication problem

christ@tybalt.caltech.edu (Christian L. Keppenne) (05/31/89)

the following problem has been giving ne headaches since i have ny NeXT.
i am using a modem to connect to a JPL computer. the modem there has a 
security system installed that asks you for your userid and password before
it authorizes you to access a communication server from which you can finally
log in onto the computer you want.
i used to do this with my mac 2 and the modem set on the same typical
 parameters: 8 bits characters, 1 stop bit, no parity, and everything worked
 fine. however, since i got the NeXT, i manage to access the communication
 server, which means that the userid and password i type (not echoed on the
 screen in the transcript below) are recognized and understood.
 i then try to type "c[space bar]" which should be extended to connect by
 the system, but it does not want to recognize my space bar. it does not 
understand my return characters either, and i have to disconnect by entering
my tip escape sequence "~."
i had a friend who also has a NeXT but another modem trying to dial in 
but he encountered the same problem.
on the other hand, i have no problem whatsoever in connecting to the caltech
[/nication server and from there to a caltech computer.

i am hoping that someone out there might have experienced the same kind of 
problem in connecting to his/her local system and would be able to give me
some clue on how i should try to solve this problem.
it would be easier if i could tell some communication wizard my userid and password so that he can try for himself and diagnose the problem but i am not
 authorized to do so on the network of course.
 
 i include a transcript illustrating what happens when i try to connect 
 (the problem occurs with both terminal and shell) and a copy of my
 /etc/remote file. if you have any idea , i would surely appreciate 
 receiving your e.mail and would call you if you give me a phone number.
 
 thank you in advance.
 
 Christian Keppenne
 
 christ@tybalt.caltech.edu | alubias@caltech.bitnet
 
 
 
 
 here is the transcript:
 
 NeXT 59>  tip a2400
connected
atdt 3936736
CONNECT 2400

HELLO, PLEASE ENTER USER NAME:
PASSWORD:
HOST ACCESS PERMITTED

Welcome to your Communications Server
CS/1T> ~
[EOT]
NeXT 60> 

and here is the /etc/remote file: 
 
 a9600|Hardwire on ttya at 9600 baud:\
	:dv=/dev/ttya:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
a2400|Hardwire on ttya at 2400 baud:\
	:dv=/dev/ttya:br#2400:el=^C^S^Q^U^D:ie=%$:oe=^D:
a1200|Hardwire on ttya at 1200 baud:\
	:dv=/dev/ttya:br#1200:el=^C^S^Q^U^D:ie=%$:oe=^D:
b9600|Hardwire on ttyb at 9600 baud:\
	:dv=/dev/ttyb:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
#
# General dialer definitions used below
#
dial1200|1200 Baud Hayes attributes:\
	:dv=/dev/cua:br#1200:at=hayes:du:
dial300|300 Hayes attributes:\
	:dv=/dev/cua:br#300:at=hayes:du:
#
# UNIX system definitions
#
UNIX-1200|1200 Baud dial-out to another UNIX system:\
	:el=^U^C^R^O^D^S^Q@:ie=#%$:oe=^D:tc=dial1200:
UNIX-300|300 Baud dial-out to another UNIX system:\
	:el=^U^C^R^O^D^S^Q@:ie=#%$:oe=^D:tc=dial300:
#
tip0|tip1200:tc=UNIX-1200:
tip300:tc=UNIX-300:
cu0|cu300:tc=UNIX-300:
cu1200:tc=UNIX-1200:
dialer:dv=/dev/cul0:br#1200:
#--------------------------------------------------------------------
#The attributes are:
#
#dv	device to use for the tty
#el	EOL marks (default is NULL)
#du	make a call flag (dial up)
#pn	phone numbers (@ =>'s search phones file; possibly taken from
#			      PHONES environment variable)
#at	ACU type (vadic, ventel, hayes, courier)
#ie	input EOF marks	(default is NULL)
#oe	output EOF string (default is NULL)
#cu	call unit (default is dv)
#br	baud rate (defaults to 300)
#fs	frame size (default is BUFSIZ) -- used in buffering writes
#	  on receive operations
#tc	to continue a capability

 
 
 christ@tybalt.caltech.edu | alubias@caltech.bitnet

jharris@jato.Jpl.Nasa.Gov (Jim Harris) (06/06/89)

354-5358. Good luck.