Here is the situation. We have 2 TS servers running WIN2K3 and 200 users with THin Clients. We'll call the first server A and the second one B. They normally connect into one IP address and they will be directed to either server A or B depending on load.However; the users can still select the specific TS Server they want to connect to.So User 1 and User 2 can not log into Server B. They get the error listed above in the Title. However User 1 and 2 can log into Server A. So if they use say:192.168.123.2 both of them get in192.168.123.3 both of them can not get in.I've removed User A's profile from .3 and he can still not get in. I've verified no orphan keys inHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileListI've checked the settings in TSCC.MSC, I'ver verified Licensing per user and that they are good, I've given them full admin rights and still they can not get in through the .3 server, they are members of all the same groups within the OU that they are in to be able to log into TS, they were able to login to it fine from this wendsday back. It's not a firewall issue and port 3389 has been verified otherwise it wouldn't be with just these two and on every TC they try. Again, they can get in by using .2.In event viewer of .3 I can see the users SUCCESSFULLY Logging in but then it pops them right out. There are no other error messages at the time of login, just the Success Message in the Security Log.We're bouncing the servers tonight so I'll have the re-start and I pray that they can log in after that on that server but I'm baffeled. Why would only 2 people be getting this issue and most (not sure how many others there might be but I know 30 people logged in today on that server and worked off of it) people are not getting an error. The thin client on their desktop is not the issue because the error follows them no matter what THIN CLIENT they are logging in from. Short of this re-boot and short of deleting the accounts and recreating them, any ideas???1 person got this answerI do too

Found the issue. I did not delete the entire key as listed above. I should have done that for this user since his CentralProfile Key was blank when it needed to be filled in by the system. Deleted his Specific SID Key for the above listed item and viola. User could log in.