E
Eric L.
Guest
Sorry if this has already been answered, but I had a hard time finding the
right words to search for this issue.
When I am remotely connecting to one of our servers, RDC has the annoying
habit of prefixing the servername I am connecting to before my username.
This is a problem because the terminal server is not an Active Directory
server and therefore my network password does not authenticate; i.e. my
network account is treated as a local account. The error it gives is "The
system could not log you on. Make sure your user name and domain are
correct..."
By default, I would like it to say:
User name: [{username} ]
Password: [ ]
But instead it says:
User name: [{servername}\{username} ]
Password: [ ]
Is there any way to fix this? I would be ok with having it by default put
the windows domain name, an Active Directory Server, or nothing in place of
the terminal server name. I'd like to correct it for everyone in the
network, too, if I could.
I have a feeling there is a simple solution somewhere. Any suggestions are
greatly appreciated!
right words to search for this issue.
When I am remotely connecting to one of our servers, RDC has the annoying
habit of prefixing the servername I am connecting to before my username.
This is a problem because the terminal server is not an Active Directory
server and therefore my network password does not authenticate; i.e. my
network account is treated as a local account. The error it gives is "The
system could not log you on. Make sure your user name and domain are
correct..."
By default, I would like it to say:
User name: [{username} ]
Password: [ ]
But instead it says:
User name: [{servername}\{username} ]
Password: [ ]
Is there any way to fix this? I would be ok with having it by default put
the windows domain name, an Active Directory Server, or nothing in place of
the terminal server name. I'd like to correct it for everyone in the
network, too, if I could.
I have a feeling there is a simple solution somewhere. Any suggestions are
greatly appreciated!