On 8/12/08, Mike Marchywka <[EMAIL PROTECTED]> wrote: > > > > Date: Tue, 12 Aug 2008 09:40:37 +0200 > > From: [EMAIL PROTECTED] > > To: cygwin@cygwin.com > > Subject: Re: Cygwin installation breaks ALL telnet clients > > > > On Aug 12 00:16, David Greenhouse wrote: > >> We are seeing an issue where after installing Cygwin and including the > >> inetutils package in order to get telnet access, none of the telnet > >> clients on the system will work properly (not Cygwin's, Microsoft's, > >> PuTTY, nothing). The issue persists even after removing Cygwin. > > > > Cygwin is just a DLL. It's impossible that it influences telnet clients > > which are not linked against this DLL. You will have to look for the > > culprit elsewhere. > > If it helps any, I would comment that,IIRC, when I set up a dual boot system, > I was a bit surprised to see that network settings in Windoze and Debian > could, IIRC, effect each other. > My memory may not be totally accurate but they did seem to interact. > That is, IIRC, I had set a static IP on one system and it ended up being > applied > to the other one. I'd look for a network configuration "thing" that may not be > stored on disk or reset during OS init. I guess those cards do have EEPROM but > I have no idea what, besides maybe a MAC addres, is in them. > Not sure if this is possible but it is what I remember. I think there > were also issues with clock settings but again my memory isn't real clear. > > In any case, at least check your network settings. It it possible someone > changed > something "irrelevant" during setup.
Well I don't know about the telnet issue as Corinna is right on that one. It is technically impossible for a cygwin application to affect a non-cygwin application directly. It may however be a setting in the OS that got affected. I don't know if I have installed the inetutils package however it may be worth a shot just to see if I can reproduce it myself. As for a Dual-boot affecting each others' networking configuration. It can happen but it isn't due to an OS interaction. Rather Debian is requesting a "static" or specific ip address and the router is caching the lease. When Windows requests a new ip the old lease still exists in the router as being assigned to the adapter' mac address. The router matches the mac address to the lease and hands back the lease to Windows so both Debian and Windows have the same IP but Windows hasn't actually been setup to use it as a "static" address. > > > > > > > > > Corinna > > > > -- > > Corinna Vinschen Please, send mails regarding Cygwin to > > Cygwin Project Co-Leader cygwin AT cygwin DOT com > > Red Hat > > > > -- > > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > Problem reports: http://cygwin.com/problems.html > > Documentation: http://cygwin.com/docs.html > > FAQ: http://cygwin.com/faq/ > > > > _________________________________________________________________ > Get Windows Live and get whatever you need, wherever you are. Start here. > http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home_082008 > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Robert Pendell [EMAIL PROTECTED] "A perfect world is one of chaos." Thawte Web of Trust Notary CAcert Assurer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/