What are you authing too? Why don't you just sniff the traffic and see exactly what is going on. So your authing to what exactly another windows 10 machine, windows 8, samba? some NAS. While PIN stuff might be causing you issues. I am on build 10240 which was install from iso from TP install with clean option. nothing in the dialog for domain and just or can put in complete gibberish and still works. This is from win10 to window7 machine - again. But you sure and the hell do not need to send the computer name workgroup or whatever to auth to a share if the machine is not part of a domain.Įdit: And just because I like to be complete in info. So not sure what your issue was or is or what this new guys problem was, etc. This is not part of the auth mech when authing to a machine that is not in a domain so what you send or don't send has nothing to do with the authing to the shares. I then put in whatever as my domain\computer name and works just the same. I then killed the session on the win10 machine who's name is win10 btw and my session on my machine and then tried again to connect and got prompted. I did not put anything in username field and access it just fine So as you can see here my computer is called i5-w7, and that is what is listed as domain. It doesn't matter its just looking for username and password.Īs you can see from screenshots I can send complete gibberish for domain/computer name and it still worksįor all we know the use was putting in the wrong freaking password and then when saw this he typed it in correctly and WOW this works When it has NOTHING to do with it!! It can only look in its local database of users, does not care if the domain is whatever or something or its correct name.
Not a bug its understanding how it works!! Did you already have a session open with guest? if a machine is member of workgroup not a member of domain then the domain name of the user account is completely meanless to that machine.
0 kommentar(er)
