search for: login0

...share in A from B. The user from B which try to connect the share in A has the same login in the two domains. So since the upgrade I don't have the same behavior ... From a computer named XXX in domain B I've tried  this command : net use z: \\<computer in A>\<share> /USER:login0 at A (where login0 is the same in A and B for the user). If I write a wrong password I have the system error 86 but if i write the good password (must write it twice) i have the system error 5. In Samba logs are :   ntlm_password_check: LM password and LMv2 failed for user login0, and NT MD4...

...> which try > to connect the share in A has the same login in the two domains. > > So since the upgrade I don't have the same behavior ... > > From a computer named XXX in domain B I've tried  this command : net > use z: \\<computer in A>\<share> /USER:login0 at A (where login0 is the > same in A and B for the user). > > If I write a wrong password I have the system error 86 but if i write > the good password (must write it twice) i have the system error 5. > > In Samba logs are : > >   ntlm_password_check: LM password and...

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host