Date: Tue, 14 Feb 2017 22:37:31 -0700 From: The Doctor <doctor@doctor.nl2k.ab.ca> To: Jason Tubnor <jtubnor@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: Bhyve / Windows Server 2016 Issue Message-ID: <20170215053731.GA17866@doctor.nl2k.ab.ca> In-Reply-To: <CACLnyC%2BCnfmPkA7aB%2B5CgOXG%2BaBh2PfNw_CiUy%2BP2=oLJcdLkA@mail.gmail.com> References: <20170214043301.GA33578@doctor.nl2k.ab.ca> <CACLnyCKnwQgDzK=F504t-kKBQFEBGECpCzydkbkmV5EvQJFxhw@mail.gmail.com> <20170214144658.GA18325@doctor.nl2k.ab.ca> <CACLnyC%2BCnfmPkA7aB%2B5CgOXG%2BaBh2PfNw_CiUy%2BP2=oLJcdLkA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Wed, Feb 15, 2017 at 05:31:44AM +1100, Jason Tubnor wrote: > On 15 Feb 2017 1:47 a.m., "The Doctor" <doctor@doctor.nl2k.ab.ca> wrote: > > > > I can log into my virtual W2k16 boxes > , but remotely, I get an error. > > Even using VNC the Password seems not to work. > > Wondering if this was w2k16/bhyve realted. > > > > Sounds like a Windows config error. Mine are vanilla installs via VNC. > Win10 was the only one I needed to turn on remote access via rdp. Well it it interesting that in either VNC or RPC the password is 'incorrect'. Message I get in the Windows logs are Event ... Microsoft Windows security auditing. Details TargetUserName (user) Status 0xc000006d FailureReason %%2313 SubStatus 0xc000006a LogonType 3 LogonProcessName NtLmSSp AuthenticationPackageNAme NTLM -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!!home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170215053731.GA17866>