Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem connecting to server console (mstsc -v:xxx.xxx.xxx.xxx -consol

Status
Not open for further replies.

SenTnel

Technical User
Dec 9, 2003
45
DO
Hi all !

I have a virtual dedicated server that accepts remote desktop connections with no problem, but I need to install an application that when the installation proccess starts pops a message telling me that it cannot install via remote desktop, that it has to be console mode.

So when I try to connect using:
mstsc -v:xxx.xxx.xxx.xxx -console
the connection proccess starts, the win 2003 server login screen opens up, I type my username and password
(administrator credential), the server attempts to authenticate, then the screen just goes
away, desappears, without any message or warning (like "your not allow to login", or any other message) telling me what the problem is.

So I have no clue as why I can log in with remote desktop, but can't access in console mode and no error message or warning at all.

Suggestions?

Thanks!
 
ok, so no error msg at all?..

go into event viewer and look for some activity at that time......

i think i know what the problem is as i had a similar problem which took me a while to finally figure out..

it is to do with fonts..
 
Thanks Dublin!

I checked the event viewer, nothing unusual, no error messages, just regular logon / logoff events, as if they were regular, I mean, like I explained, I entered username and password, few seconds later the screen desappears, and now I realized that it does logon and then logoff inmediately after. The event viewer register "succesfull logon" and right after a "succesfull logoff".

Please tell me about the problem you had and how you solved it.

Again, Thanks!
 
well i didn't really solve it at all.............it was to do with Type 1 fonts in the registry!

your problem could be different though. I had to go into registry and then rename a particular font. I don't remember the name now but search on google and you should find the solution...................but my solution was VNC and the other program called remote desktop.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top