Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Andrew DeFaria Newsgroups: gmane.os.cygwin Subject: Another failure to get telnet/inetd to work in 1.3.12 Date: Thu, 11 Jul 2002 15:55:50 -0700 Lines: 50 Message-ID: <3D2E0CF6.8080202@Salira.com> Reply-To: cygwin AT cygwin DOT com NNTP-Posting-Host: 206.184.204.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1026428097 3009 206.184.204.2 (11 Jul 2002 22:54:57 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Thu, 11 Jul 2002 22:54:57 +0000 (UTC) Cc: Andrew DeFaria User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en I know others have had problems with this but I think I understand how it's supposed to work fairly well and it has been working for me for quite some time. Recently it has broken. I cannot telnet into my own XP box with Cygwin 1.3.12. I have inetd set up properly, I have CYGWIN set to ntsec in my Windows System Environment. I have Cygwin's bin in my PATH in my Windows System Environment and I have rebooted to ensure that these changes have been made effective. Inetd starts as a service and all of this has worked before flawlessly. In fact, my Windows XP box at home works OK. When telnet is attempted when inetd is running as a service I get connection refused. I also get connection refused for rlogin, ftp, etc. If I stop the inetd service and run inetd -d at a command line then everything works (with the curious exception that telnet does not prompt for a username but otherwise works). So then what's going on here? Why, when telnet/rlogin/ftp is stated from inetd that was fired up as a Windows service it fails but not when it's stated from the command line? The usual reason is that the system environment variables are not set, but mine are indeed set. Also, how would one debug this? Ah ha. Here's something strange. In the Event Viewer each inetd service has an error like: Event Type: Error Event Source: inetd Event Category: None Event ID: 0 Date: 7/11/2002 Time: 3:49:22 PM User: NT AUTHORITY\SYSTEM Computer: ADEFARIA Description: The description for Event ID ( 0 ) in Source ( inetd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: inetd : Win32 Process Id = 0xA1C : Cygwin Process Id = 0xA1C : ssh/tcp: unknown service. Why doesn't inetd think that any of it's services are "known"?!? Bonus points for anybody who can explain and help get rid of the "The description for Event ID ( 0 ) ins Source ( inetd )..." portion of such error messages. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/