Xref: utzoo comp.protocols.tcp-ip:14765 comp.os.vms:35156 Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!NewsServ!bl.physik.tu-muenchen.de!k2 From: k2@bl.physik.tu-muenchen.de (Klaus Steinberger) Newsgroups: comp.protocols.tcp-ip,comp.os.vms Subject: Re: UCX and CDCnet problem Message-ID: Date: 6 Feb 91 08:16:24 GMT References: <12316.27ae98c0@ecs.umass.edu> Organization: The Internet Lines: 45 ucc@ecs.umass.edu writes: >We are running UCX v1.3A. (The "A" if for a patch recommended >by CSC that was applied). Our hardware is 2 6210s running >VMS 5.4, clustered. >We have an elusive problem, where at times, and not always >on the same node, when a user tries to access the VAXcluster with a >telnet process from a CDCnet device, (TDI) the user >gets the message "USER AUTHERIZATION FAILURE", after typing >in the password. However the password is correct and not expired, >or preexpired. >Has any body any ideas about this situation? I have no idea on the "USER AUTHORIZATIOn FAILURE", but we also have trouble with CDCnet -> UCX1.3A Our problem: If somebody trys to connect from a CDCnet node to our VAX, the connection sets up, but he get no prompt, until he/she types in a Break-character. With some debugging, we found out, that the VAX doesn't respond immediately with a login prompt, if the other side doesn't support the Terminal Type option (as in CDCnet!). The prompt appears after some input, like a local terminal. That dolt CDCnet isn't able to send a character at this stage, only BREAK got it to send something! So there are two problems, one side is UCX which barfs on a missing Terminal Type Option, and CDCnet which isn't able to send at this stage. Sincerely, Klaus Steinberger -- Klaus Steinberger Beschleunigerlabor der TU und LMU Muenchen Phone: (+49 89)3209 4287 Hochschulgelaende FAX: (+49 89)3209 4280 D-8046 Garching, Germany BITNET: K2@DGABLG5P Internet: k2@bl.physik.tu-muenchen.de