From owner-freebsd-bugs Mon Feb 27 10:18:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA01042 for bugs-outgoing; Mon, 27 Feb 1995 10:18:01 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA01032 for ; Mon, 27 Feb 1995 10:17:57 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA02437; Mon, 27 Feb 95 11:11:11 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502271811.AA02437@cs.weber.edu> Subject: Re: your mail To: root@mclo10.weber.edu (Bob Resino) Date: Mon, 27 Feb 95 11:11:10 MST Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199502271756.MAA18028@mclo10> from "Bob Resino" at Feb 27, 95 12:56:32 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Does anyone have any idea why Communications Machine Company > (CMC) Nics on AT&T 3B2's running the CMC Telnetd refuse > connection from my FreeBSD host ? There is a note in the > man (8) page for telnetd (CMC) that states there is extensive > negotiation testing for the early troublesome 4.2 BSD telnet. > > Any help is appreciated. The idea is that option negotiation order will allow you to tell if you are talking to a 4.2 or a 4.3 telnet -- in reality, the 4.2 and 4.3 differences are a result of the differences in OOB data handling between the releases. In particular, 4.2 flubbed the urgent packet handling rather badly; so with those systems, you want to not use urgent packets. This should not effect your ability to connect to CMC. Are you sure that you have the BSD box set up correctly in your local domain name services database? If the CMC telnetd can't do a getpeername successfully, it'll probably refuse the connection. This is *a* possible cause of your symtoms, and not *the* only possible cause. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.