After a lot of struggling with trying to get sshd work with regular
domain accounts I found an alternative bit of software I then installed
for a test. After a failed test, looking thrugh the logs of that ssh
server I found an interesting piece of information possibly explaining
why it wouldn't
Looks like I hit a wall with this problem. I would appreciate if someone
could help out with this issue.
On 2015-08-17 21:39, yaro...@hotmail.com wrote:
I have Cygwin installed on a couple of servers in a domain
environment. Of all machines regular user accounts can ssh to only one
box.
Once i
On 2015-08-17 21:39, yaro...@hotmail.com wrote:
I have Cygwin installed on a couple of servers in a domain
environment. Of all machines regular user accounts can ssh to only one
box.
Once installed I configured Cygwin using the following in a .bat file.
c:\cygwin\bin\bash --login -c "chmod +
I have Cygwin installed on a couple of servers in a domain environment.
Of all machines regular user accounts can ssh to only one box.
Once installed I configured Cygwin using the following in a .bat file.
c:\cygwin\bin\bash --login -c "chmod +r /etc/passwd"
c:\cygwin\bin\bash --login -c "chmod
On 2015-07-22 23:46, Andrey Repin wrote:
Greetings, Jarek!
So why are they not needed as your comment doesn't really explain that
Read 1.7.35 changelog.
In short, username resolution was completely reworked, thanks to Corinna, and
Cygwin now directly address domain controllers for it
On 2015-07-22 23:46, Andrey Repin wrote:
Greetings, Jarek!
So why are they not needed as your comment doesn't really explain that
Read 1.7.35 changelog.
In short, username resolution was completely reworked, thanks to Corinna, and
Cygwin now directly address domain controllers for it
On 2015-07-21 22:36, Andrey Repin wrote:
Greetings, Jarek!
So why are they not needed as your comment doesn't really explain that
Read 1.7.35 changelog.
In short, username resolution was completely reworked, thanks to Corinna, and
Cygwin now directly address domain controllers for it
On 2015-07-21 02:25, Andrey Repin wrote:
Greetings, Jarek!
Hey Andrey.
So why are they not needed as your comment doesn't really explain that
Read 1.7.35 changelog.
In short, username resolution was completely reworked, thanks to Corinna, and
Cygwin now directly address domain contro
controls the
access?
On 2015-07-20 00:38, Andrey Repin wrote:
Greetings, Jarek!
I'm still quite new to Cygwin. I'm using the most recent version to
install the ssh component on Server 2012R2 member server since it
happened to become a requirement for certain users. The problem I have
On 2015-07-20 19:52, Matt Seitz (matseitz) wrote:
From: Andrey Repin
http://cygwin.com/faq/faq.html#faq.using.sshd-in-domain
Any suggestions if you can't get your domain admin to create a generic
"cyg_server" account for you?
I suspect some people in corporate environments may have trouble g
I'm still quite new to Cygwin. I'm using the most recent version to
install the ssh component on Server 2012R2 member server since it
happened to become a requirement for certain users. The problem I have
is to understand how to allow access for domain groups. I read the new
version doesn't eve
This is installation process of DBD::Sybase (I installed DBI before
DBD::Sybase)
$ perl Makefile.PL
Unknown Client Library version - assuming FreeTDS.
By default DBD::Sybase 1.05 and later use the 'CHAINED' mode (where
available)
when 'AutoCommit' is turned off. Versions 1.04 and older inste
I have some problems with using DBD::Sybase. At first I couldn't run
"make" successfully but after few tries I managed to do it. Now I have
problem with this message : install_driver(Sybase) failed: Can't load
'/usr/lib/perl5/site_perl/5.8/cygwin/auto/DBD/Sybase/Sybase.dll' for
module DBD::Sybase:
13 matches
Mail list logo
