Xref: utzoo comp.protocols.tcp-ip:14879 comp.os.vms:35406 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!decwrl!deccrl!news.crl.dec.com!decvax.dec.com!peano.zk3.dec.com!spider From: spider@peano.zk3.dec.com (Spider Boardman OSG/CSSE) Newsgroups: comp.protocols.tcp-ip,comp.os.vms Subject: Re: UCX and CDCnet problem Message-ID: Date: 13 Feb 91 03:00:41 GMT References: <12316.27ae98c0@ecs.umass.edu> Sender: news@decvax.dec.com.UUCP Followup-To: comp.protocols.tcp-ip Organization: DEC Open Systems Group Customer Service Lines: 20 In-reply-to: k2@bl.physik.tu-muenchen.de's message of 6 Feb 91 08:16:24 GMT In article k2@bl.physik.tu-muenchen.de (Klaus Steinberger) writes: >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. There is a patch available for this particular problem in UCX, which you should be able to get from your Customer Support Center (CSC). CDCnet I can't help you with. -- Spider Boardman spider@decvax.dec.com DEC OSG/CSSE ...!decvax!spider I don't speak for DEC, and vice versa.