Terminal Services - Default "Log on to:"

After applying quite a number of Windows updates, something has gone awry with Terminal Services.

Any new connection that does not define the domain name via the username (i.e. user@domain.com or domain.com\user) will default to attempting the credentials as localhost\user.

I understand that I can force Terminal Services to default to my domain, but then that requires my users to enter their credentials again.

My understanding is that Terminal Services uses the last logged in cache but my experience is otherwise after these windows updates.  It keeps defaulting back to the localhost unless I force terminal services to prompt for credentials or define the domain in the username field.

This is a Windows 2003 SE with SP2.

I've also tried editing the "AltDefaultDomainName" and "AltDefaultUserName" in HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon, but to no avail.  I'm pretty much down to selectively removing Windows updates to see which one has affected this change.  Any ideas to the contrary will be much obliged.
Who is Participating?
patternedConnect With a Mentor Author Commented:
Son of a monkey-nut.
This is so retarded.

Anyone who runs into this problem, it is not a windows update that causes the issue.

I usual do remote reboots and login via console and when I log in I use the domain\user combination, thus (I assume, I haven't researched) not setting the default.rdp that FOTC referred to earlier.

I'm kicking my self right now.
is this happening on all machines or just your machine?

if its just yours, you may want to try deleting the file "Default" located in the users "my documents / documents" folder. you will have to enable hidden files and folders to see it.
patternedAuthor Commented:
This is all machines.  Newly added to the domain machines, I've tested.

Local settings shouldn't matter in a domain environment.  If you're logged in under the domain, the default login to a Terminal Server should be the domain.

After some more poking I found this out:

On my XP machine running RDP 6, it will save the settings after the first login to the Windows 2003 server, however I still have to change it the first time.  Any connection to any other server defaults to my domain.

On all my clients (who are running RDP 7) they will not save the settings unless I specify the domain in the user field.
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

got me...it could having something to do with having a mixed bag of 6 & 7 clients. do you have any GPO settings applied with TermSvc settings?
patternedAuthor Commented:
No GPO settings, as they would be applied across all servers and those are not exhibiting the problem.

I only have 2 or 3 machines running 6..
This wasn't an issue until the updates came down the pipe.  I guess I'm forced to hunt and peck.. oh god the pain.  I feel it already.
lol sorry....couldn't you just update them all to v7?
patternedConnect With a Mentor Author Commented:
That wouldn't solve my problem.

RDP 7 doesn't default to the domain for login!  I have to define it in the user field.. and I don't want to run around to everyone and add domain\user to all my clients.  Too much of a hassle and I can't depend on them to figure it out.

I'm the only one who uses RDP 6, anyway.
patternedAuthor Commented:
Don't initially log into the machine via console with "domain\user" or "user@domain".  This will cause RDP clients to default to authenticating to the localhost.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.