From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Problems with ssh when I log into my PC using my corporate domain while working from home
Date: Thu, 23 Apr 2020 21:33:38 +0200 [thread overview]
Message-ID: <87h7xa5759.fsf@Rainer.invalid> (raw)
In-Reply-To: <49c12452-3402-54ff-57ba-f61757d99ae0@mehconsulting.com> (Mark Hansen's message of "Thu, 23 Apr 2020 11:10:24 -0700")
Mark Hansen writes:
> I think Windows knows who I am. I log into the machine using my normal domain login
> credentials. The machine looks the way it does when I log in when the machine is in the
> office - the desktop is the same, etc. - it's not acting like I'm a new user or anything
> like that.
That doesn't necessarily tell you anything about what happens when you
try to log in via ssh (which creates a new session and requires an
independent login). Again, the fact that Cygwin shows you a different
user name already tells you that there is something quite different from
when you are in the office. If you can strace id you might get a clue
of what is going on with the queries to the AD sever in both cases
(i.e. what server it asks and whether it gets an answer).
> Everything on the Windows side seems to be working fine. The only issue I've found is with
> Cygwin. Is there a way (short of removing and reinstalling Cygwin) that I can get Cygwin
> to recognize my current user so ssh and git can know where my home directory is located?
Yes, you can force a home directory via config files, but you should
keep in mind that this can fail in even more mysterious ways should the
environment change again.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
prev parent reply other threads:[~2020-04-23 19:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 15:33 Mark Hansen
2020-04-21 21:52 ` Mark Hansen
2020-04-23 11:54 ` Mark Hansen
2020-04-23 12:51 ` Marco Atzeri
2020-04-23 15:25 ` Mark Hansen
2020-04-23 19:19 ` Marco Atzeri
2020-04-23 19:30 ` Marco Atzeri
2020-04-23 21:50 ` Mark Hansen
2020-04-24 5:11 ` Brian Inglis
2020-04-23 17:26 ` ASSI
2020-04-23 18:10 ` Mark Hansen
2020-04-23 18:57 ` Norton Allen
2020-04-24 13:43 ` Mark Hansen
2020-04-23 19:33 ` Achim Gratz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7xa5759.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).