inetd doesn't work until stopped and restarted

[Charles Wilson]

This probably has to do with the order in which Windows System services
are started. e.g. if inetd depends on, say, 'windows socket services'(*)
then if inetd is started at bootup *before* WSS, it'll fail. However,
once the machine is running, then you can restart inetd and it'll work
because WSS is up.

I seem to remember some article in the Microsoft Knowledge Base about
this, and how to resolve it -- but no specifics. Hunt around at
support.microsoft.com.

(*) 'WSS' is an imaginary service I made up. But you get the idea.

--Chuck


Richard Stanton wrote:
> 
> I have ftpd, telnetd, sshd etc all running fine via inetd (with the
> exception of the missing ftp directories), except for one thing.
> 
> inetd is set up to start automatically as an NT service. If I reboot, then
> try to connect to my machine, things don't work. For example:
> 
> [c:\]ssh mortgage
> ssh_exchange_identification: read: error 0
> 
> [c:\]ftp mortgage
> Connected to mortgage.berkeley.edu.
> 421 Service not available, remote server has closed connection
> ftp>
> 
> If I stop and then restart inetd, all is fine. For example,
> 
> [c:\]net stop inetd
> The CYGWIN inetd service is stopping.
> The CYGWIN inetd service was stopped successfully.
> 
> [c:\]net start inetd
> The CYGWIN inetd service is starting.
> The CYGWIN inetd service was started successfully.
> 
> [c:\]ssh mortgage
> stanton@mortgage's password:
> 
> Any idea what the problem is?
> 
> By the way, CYGWIN=binmode tty ntsec
> 
> Richard Stanton
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com