Re: running the latest cygwin on a windows 2003 server

2004-01-22 Thread Stefan Zachow
Dave Korn wrote: another question to this topic came into my mind: why is this all happening only to the Windows Server 2003 machine? Ah, but then you go and point out that... Although the SAMBA problem appears on all machines. That's true. It seems that I have two problems here and the

Re: running the latest cygwin on a windows 2003 server

2004-01-22 Thread Stefan Zachow
Thanks a lot to all who helped me. In case one encounters this problem the web-site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncode/html/secure06122003.asp gives an answer. Creating Various Global Objects May Fail: Starting with Windows Server 2003, the creation of

Re: running the latest cygwin on a windows 2003 server

2004-01-22 Thread Igor Pechtchanski
On Thu, 22 Jan 2004, Stefan Zachow wrote: [snip] I only have to figure out how to do set global priviliges Stefan, Did you try the editrights tool? Grab it using Cygwin's setup.exe. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_

Re: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Stefan Zachow
Good morning, How about when you start bash from a command prompt (i.e., open an MS DOS prompt window, cd c:\cygwin\bin, and .\bash.exe --login -i) as a non-administrative user? What if you omit --login? when I enter .\bash.exe --login -i (with or without --login) I get *** CreateFileMapping,

Re: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Stefan Zachow
Further info... 'mkgroup' is strange. It seems that I cannot synchronize with our network databases. A mkgroup -u -d DOMAIN gives the following two lines of output: LookupAccountName (\\Host, Domain Admins) failed with error 1332 LookupAccountName (\\Host, Domain Users) failed with error 1332

RE: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Dave Korn
-Original Message- From: cygwin-owner On Behalf Of Stefan Zachow when I enter .\bash.exe --login -i (with or without --login) I get *** CreateFileMapping, Win32 error 0. Terminating. Fascinating. That's from winsup\cygwin\shared.cc line 96. Can't see why it would fail

Re: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Stefan Zachow
Dave Korn wrote: Try giving your cygwin non-admin user accounts the Create paging files privilege and see if that helps. I _think_ you have to do that using the group policy editor, gpedit.msc. OK, I did - unfortunately without any change. How is this Windows information mapped to cygwin, resp.

RE: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Dave Korn
-Original Message- From: Stefan Zachow Dave Korn wrote: Try giving your cygwin non-admin user accounts the Create paging files privilege and see if that helps. I _think_ you have to do that using the group policy editor, gpedit.msc. OK, I did - unfortunately without any

Re: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Stefan Zachow
another question to this topic came into my mind: why is this all happening only to the Windows Server 2003 machine? The same installation with the same configuration runs well with Windows 2000 or Windows XP. Although the SAMBA problem appears on all machines. It must have something to do with

Re: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Warren Young
Stefan Zachow wrote: why is this all happening only to the Windows Server 2003 machine? Because Microsoft tightened down a lot of things in Win2K3 that previous Windows OSes allowed. I upgraded a server from Win2K to Win2K3 a few weeks ago, and already we've been bit by two of these paranoia

RE: running the latest cygwin on a windows 2003 server

2004-01-21 Thread Dave Korn
-Original Message- From: cygwin-owner On Behalf Of Warren Young Stefan Zachow wrote: why is this all happening only to the Windows Server 2003 machine? Because Microsoft tightened down a lot of things in Win2K3 that previous Windows OSes allowed. I upgraded a server

help: running the latest cygwin on a windows 2003 server

2004-01-20 Thread Stefan Zachow
Dear cygwin experts, I went through the mailing list archive searching for windows 2003 server but the resulting 10 pages didn't really help. Could anybody please provide a hint to my problem running cygwin on a Windows 2003 server? I can only start a cygnus shell when I am a member of the

Re: help: running the latest cygwin on a windows 2003 server

2004-01-20 Thread Larry Hall
At 09:28 AM 1/20/2004, Stefan Zachow you wrote: Dear cygwin experts, I went through the mailing list archive searching for windows 2003 server but the resulting 10 pages didn't really help. Could anybody please provide a hint to my problem running cygwin on a Windows 2003 server? I can only

Re: running the latest cygwin on a windows 2003 server

2004-01-20 Thread Stefan Zachow
Larry, Also, who did you install Cygwin as and did you install it for All users or Just me? The answer to the last part may provide you with the answer you seek. Otherwise, please provide more specific information as requested above. I did install cygwin as Administrator for 'all users'. Since

Re: running the latest cygwin on a windows 2003 server

2004-01-20 Thread Igor Pechtchanski
On Tue, 20 Jan 2004, Stefan Zachow wrote: Larry, Also, who did you install Cygwin as and did you install it for All users or Just me? The answer to the last part may provide you with the answer you seek. Otherwise, please provide more specific information as requested above. I did install

Re: running the latest cygwin on a windows 2003 server

2004-01-20 Thread Stefan Zachow
Igor, What is the exact message you get when you try to run Cygwin programs as another user? Which exact programs fail? Do all the programs fail in the same way? Unfortunetly users that are not in the administrator group cannot even start a bash. That's why I took an Administrative user to

RE: running the latest cygwin on a windows 2003 server

2004-01-20 Thread Dave Korn
-Original Message- From: [EMAIL PROTECTED] On Behalf Of Stefan Zachow Unfortunetly users that are not in the administrator group cannot even start a bash. That's why I took an Administrative user to create the cygcheck output. The bash appears very shortly as a frame and