Re: still having problem: devenv through sshd
On Dec 18 17:34, Derek Lei Liu wrote: Kind of wondering if this thing ever work for anyone. A few weeks back, i had problem to run devenv build script through sshd on windows 2003 server. here is the thread: http://sourceware.org/ml/cygwin/2007-11/msg00473.html The symptom was basically the same script can be executed from remote desktop console, but not through ssh session. the script simplely hang and doesn't spill out any error message. I struggled a lot with it and finally gave up even with Dave's help. I then give up 2003 and moved to XP. The problem with XP is even more subtle now. I can ssh in with password authentication and execute the script just fine (one step closer compare to 2003). However, public key authentication still not working (i am getting the fatal error C1902: Program database manager mismatch; please check your installation). There was a thread discussed this issue so i thought the problem can be worked around by just using password authentication. Since i need passwordless login process, i employeed perl Net-SCP-Expect and Net-SSH. Both module works just fine and are using password authentication (that's what they are designed for). However, remotely executing the build script still give me C1902 errors. I just can't figure out what's the difference between password login interactively and using perl modules. I am stuck again, need some help here. Thanks. Did you try the latest Cygwin 1.5.25-7? There's a small change when creating the user token which might help. I can't promise it does, because it was originally to workaround a problem in 2003 Server, not in XP. Other than that, the Cygwin ML archive has a pointer to a Microsoft Hotfix to workaround this problem in Visual Studio: http://sourceware.org/ml/cygwin/2006-10/msg00383.html 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/
Re: still having problem: devenv through sshd
I am running 1.5.25(0.156/4/2), not sure if that is what you meant by 1.5.25-7. Also, if it isn't, how to completely wipe out cygwin and reinstall again? On this issue, i have tried two reinstallation on two XP machines (just remove c:\cygwin and some registries). I also tried install Visual Studio 2005 service pack1. Also tried the hot fix on one machine. All these efforts didn't work. So my question is: has any one actually have it working on XP? (be able to passwordlessly run devenv through sshd). Can people share experience (hopefully successful experience) on this? thanks Derek - Original Message - From: Corinna Vinschen [EMAIL PROTECTED] To: cygwin@cygwin.com Sent: Wednesday, December 19, 2007 2:48 AM Subject: Re: still having problem: devenv through sshd On Dec 18 17:34, Derek Lei Liu wrote: Kind of wondering if this thing ever work for anyone. A few weeks back, i had problem to run devenv build script through sshd on windows 2003 server. here is the thread: http://sourceware.org/ml/cygwin/2007-11/msg00473.html The symptom was basically the same script can be executed from remote desktop console, but not through ssh session. the script simplely hang and doesn't spill out any error message. I struggled a lot with it and finally gave up even with Dave's help. I then give up 2003 and moved to XP. The problem with XP is even more subtle now. I can ssh in with password authentication and execute the script just fine (one step closer compare to 2003). However, public key authentication still not working (i am getting the fatal error C1902: Program database manager mismatch; please check your installation). There was a thread discussed this issue so i thought the problem can be worked around by just using password authentication. Since i need passwordless login process, i employeed perl Net-SCP-Expect and Net-SSH. Both module works just fine and are using password authentication (that's what they are designed for). However, remotely executing the build script still give me C1902 errors. I just can't figure out what's the difference between password login interactively and using perl modules. I am stuck again, need some help here. Thanks. Did you try the latest Cygwin 1.5.25-7? There's a small change when creating the user token which might help. I can't promise it does, because it was originally to workaround a problem in 2003 Server, not in XP. Other than that, the Cygwin ML archive has a pointer to a Microsoft Hotfix to workaround this problem in Visual Studio: http://sourceware.org/ml/cygwin/2006-10/msg00383.html 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/ -- 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/
still having problem: devenv through sshd
Hi, Kind of wondering if this thing ever work for anyone. A few weeks back, i had problem to run devenv build script through sshd on windows 2003 server. here is the thread: http://sourceware.org/ml/cygwin/2007-11/msg00473.html The symptom was basically the same script can be executed from remote desktop console, but not through ssh session. the script simplely hang and doesn't spill out any error message. I struggled a lot with it and finally gave up even with Dave's help. I then give up 2003 and moved to XP. The problem with XP is even more subtle now. I can ssh in with password authentication and execute the script just fine (one step closer compare to 2003). However, public key authentication still not working (i am getting the fatal error C1902: Program database manager mismatch; please check your installation). There was a thread discussed this issue so i thought the problem can be worked around by just using password authentication. Since i need passwordless login process, i employeed perl Net-SCP-Expect and Net-SSH. Both module works just fine and are using password authentication (that's what they are designed for). However, remotely executing the build script still give me C1902 errors. I just can't figure out what's the difference between password login interactively and using perl modules. I am stuck again, need some help here. Thanks. Derek -- 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/