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.
OK so
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.
OK so
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.
>>> OK so it addresses DCs
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.
OK so
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.
> OK so it addresses DCs to check some s
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 controllers fo
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.
> and how exactly did I screwed up my setup if I
Hi Andrey.
So why are they not needed as your comment doesn't really explain that
and how exactly did I screwed up my setup if I can actually access the
server with a domain user account no problem? Perhaps it's not how it
works but it somehow works so again would be good to know why. It's only
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
> 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 getting domain
admins to create a generic "cyg_se
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
> is to understand how to allow access for domain groups. I read t
11 matches
Mail list logo