We have a single user that has a laptop with windows vista home. As of the beginning of the week and prior, the laptop was able to access server resources such as a public shared folder, and also used an inventory program that accessed the server for a database. Now it seems it cannot access the server. The network it is trying to access is a server 2003 domain.

When the user tries to access either the folder or inventory program, they are prompted to input credentials but are denied because of improper permissions. The user is inputting the proper information because they can access the server using remote desktop.

The users account is also locking after 1 attempt to make the connection, however security policies are set to 5 attempts before lock-out.

The error that comes up in the event log on the server is a Usernv error with the following message: "Windows cannot determine user or computer name. Return value (1326)."

Would adding a host record to the server DNS correct this issue?

And Yes I understand that Vista Home is not able to join a domain. This laptop was indeed able to access server resources before.

When attempting to contact the share, and you receive the question about credentials, have you tried domain\user or user@domain instead of just the username?

Often times I still run into this.

Yes, I've tried both formats.

The only thing that has changed in the network, was the enabling of password security policies last friday. Even so, the vista home laptop was still able to access the server resources up until yesterday.

One source said that it might be because of a residual rdp session that didn't completely disconnect, but there was no residual session showing in the telnet manager.

This post has been edited by Xero: Nov 6 2009, 08:11 AM

hmm, strange, have you tried rebooting the server? Existing RDP sessions really shouldn't effect your ability to connect to a file share. Have you double checked permissions? Is that user able to connect to the share from a domain joined PC?

User just came in this morning and tried to connect and had success. Not exactly sure why, with the exception of a guess that maybe he really didn't log off his RDP properly the day before. Maybe a disconnected session with his credentials was still showing in the telnet manager and that's why it wasn't letting him connect.

There was no problem connecting through RDP or from another computer that was in the domain.