Having a hard time with sharing in Vista

I have scoured the internet looking for a solution to this problem and came up with nothing. Thanks to everyone in advance for your help with this problem.

Here is what I am trying to do:

Share printer and files on a home network between the following computers:
#1 Desktop w/Vista Home Premium(64) - referred to as DT
#2 Laptop w/Vista Home(32) - referred to as LT32
#3 Laptop w/Vista Home Premium(64) - referred to as LT64

Problem:

When I try to connect to DT using LT64 I get a dialog window prompting for user name and password. When I enter UN/PW I get a message stating

"Logon Unsuccessful: Windows is unable to log you on. Be Sure that your user name and password are correct."

LT32 is able to connect to DT with no issues. As far as I know I have setup LT32 and LT64 exactly the same except that username/pw is different (different people use the computers) and LT64 was purchased approximately 1 month later than LT32.

Background:

- All three machines have the same workgroup.
- I have enabled all options in the Network Sharing and Discovery area on DT (including Password Protected Sharing).
- DT is the primary machine and is connected directly to the internet/printer. The other machines connect through DT. As stated before, this is not an issue for LT32.
- I have established user accounts (administrators) on DT that mach the user accounts on both laptops.
- The username used by LT32 to connect to DT is Laura.
- The username used by LT68 to connect to DT is Charlie.
- The passwords for Laura and Charlie are universally the same.

What's really weird:
If I create a user account on LT64 that corresponds with an administrator user account on DT other than Charlie (example:mom) I am able to connect without issue. I have tried deleting the user account Charlie on both LT64 and DT and creating a new set using a different name and still encounter the same error. It's like DT will not grant permission for any new users.

I am going to the store to get a six pack because I've tried everything I can think of short of trying to drink this issue away. Any help that anyone can offer would be GREATLY appreciated.

Thanks to everyone for their help,

--Chief Northstar--

Welllll...I solved my own problem! It figures that after a week of trying different things I finally find a solution after I make a request for help. Anyway, here's what was going on.

As you probably know, in order for two vista machines to connect through a network, there must be identical user accounts established on both computers. When I purchased the new laptop LT64 (see original post) the system came with a pre-existing username: Owner. DT had a pre-existing account, Charlie, which my father (name Charlie!) already used so I just changed the name of the Owner account on LT64 to Charlie. Seems reasonable, right?

Well, it turns out that when you change the name of a user account, it doesn't actually change at all. All that changes is the displayed name, but all internal opperations are still conducted using the name that was supplied for the user account at the time of its' creation. Therefore: even though I changed the name of the account on LT64 to Charlie the system was still attepmting to access DT as Owner!

In order to solve this conflict I took the following action:
- Created user account Owner on DT
- Changed name of user account Owner to Charlie on DT
- Changed name of user account Owner to Charlie on LT64

Result:
My computer illiterate father, Charlie, can now log onto his laptop using his name and access network files and ther printer directly and automatically.

I found the inspiration to this solution on the following page: Setting up user accounts in Windows Vista

Specifically helpful is the bit about the NET USER command. Entering the NET USER command in the terminal without operators will list all network users by their TRUE name, not the display name. This command can also be useful in managing other account features, provided you are comfortable opperating with the terminal.

I hope this solution helps others who may have experienced similar problems, and thanks again to those of you who took the time to read and consider my problem

--Chief Northstar--