This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 2003 Installing inetd as a service

Andrew DeFaria wrote:
What's the best way to install inetd as a service on Windows 2003. I used to use inetd --install-as-service but I'm thinking a cygrunsrv -I inetd style line would be better.

Also, since what I want to accomplish is the ability to telnet, rlogin, rsh into the 2003 server running the inetd service. Since this is 2003 does the inetd service need to run as just the Local System Account (SYSTEM) or does it need to run as a user who's privileges are elevated?
Still haven't heard an answer for this question.

Meantime I decided to try to start over. I recreated /etc/passwd and /etc/group with mkpasswd -l -d and mkgroup -l -d and ran the ssh-host-config script. (BTW: the old /etc/passwd, /etc/group was a copy of files created and shared with all machines. When created we used -o 0 to change the default offset in uid/gids from 10000 -> 0).

I'm trying to get ssh working now as I deleted the inetd service using inetd --remove-as-service and it marked the inetd service as disabled and "marked for deletion" so I'll have to reboot to get that to finally delete. Meantime attempting to get ssh to work I now get:

$ ssh localhost
Read from socket failed: Connection reset by peer
$ cat /var/log/sshd.log
5 [main] sshd 8680 C:\Cygwin\usr\sbin\sshd.exe: *** fatal error - CreateFileMapping Global\cygwin1S4.S-1-5-21-1957994488-1035525444-725345543-1322.1, Win32 error 0. Terminating.

Also, the Event Viewer states:

Event Type: Error
Event Source: sshd
Event Category: None
Event ID: 0
Date: 6/1/2006
Time: 11:47:15 PM
User: SONS-SC-CC\sshd_server
Computer: SONS-SC-CC
The description for Event ID ( 0 ) in Source ( sshd ) 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: sshd: PID 6808: fatal: mm_request_receive: read: Software caused connection abort.

Any clues?


Andrew DeFaria <>
I used to be schizophrenic, but we're all right now.

-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]