• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

RDP / switch does not work

OutHouse

Lifer
This is a new install of XP and i can not use the /console switch in RDP to connect to any of my servers. I can connect just fine without using the switch. I need that function to work i have apps that run under a specific login that i need to have access too.

i have googled and googled and the only thing i found is that the /console does not work with windows 2008 and to use /admin. i tried that just for fun but got the same error.

the error is

"The server name specified is invalid"

the server(s) names are correct i get that error when use the /switch.


any ideas???
 
Don't know if it helps, but I just tried the /console with vista x64 and it worked. Do you have version 6 installed?
 
It has to do with the group policy, and the ability to logon locally. I ran into this a couple of times on terminal servers, but not on a regular server.

Unfortunately I do not remember the exact spot to change it in the GP.
 
If he didn't have permissions to logon over RDP, he would still get a logon screen. It sounds more like the OP is putting the /console switch in the wrong place.

OP, try this: click start, run and then type "mstsc /console /v:servername" and see if it connects.

When you just run mstsc, I believe you need to enter the servername then /console. I'm not sure, because I always use run method above.
 
Originally posted by: stash
If he didn't have permissions to logon over RDP, he would still get a logon screen. It sounds more like the OP is putting the /console switch in the wrong place.

OP, try this: click start, run and then type "mstsc /console /v:servername" and see if it connects.

When you just run mstsc, I believe you need to enter the servername then /console. I'm not sure, because I always use run method above.


It has to do with using the /console switch. I would bet a nickel that if he tries to connect to the server without using that switch as administrator, that he will be able to logon. Using that switch is treated as if he was logging on locally at the server, and if the GP is set to prevent certain users from logging on locally, including the administrator, then it will give that error message.
 
I just checked one of the servers we had to change this on.

This server is using the default group policy.

The spot is under: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Allow Logon Locally

We then defined the policy and added the domain/administrators group.
 
As I said, when you aren't able to logon because of incorrect user rights, you get a very specific error: "the local policy does not allow you to logon interactively"
 
In two cases where this was an issue, the error message was not about logging on locally. I do not remember what it was, but making the GP change fixed it.
 
Back
Top