Solved

RDP to 2003r2 x86 Std only works in Console mode.

Posted on 2009-07-07
6
999 Views
Last Modified: 2013-11-21
I have a Windows 2003 R2 server that I can log on directly to the console, RDP in via console, but if I RDP in on a normal RDP Session, it fails.

You're prompted to log in, and the screen changes to blue, like you'd normally expect, but after about a minute of staring at an empty desktop, it simply closes the connection.

There are no errors in the app or system logs.  I enabled Terminal Services, then disabled Terminal Services, but am still having the same problem.  RDP is enabled, and I have rights, but not sure where to go from here.  If I watch Task Manager, I can see the new sessions listed as Active when trying to RDP in, but then they just disappear like the user logged off.
0
Comment
Question by:cougar694u
  • 3
  • 2
6 Comments
 
LVL 13

Assisted Solution

by:leegclystvale
leegclystvale earned 50 total points
ID: 24794551
Have you allowed your username to log onto TS server through the TS security policy?
0
 
LVL 2

Author Comment

by:cougar694u
ID: 24796041
It's in remote admin mode, not in TS mode.  Yes, I have rights to log in.  Other DA's are having the same problem, as well as LA's.
0
 
LVL 2

Assisted Solution

by:skshoup
skshoup earned 200 total points
ID: 24796262
What client machines are you connecting from?  XP, Vista, Windows 7, Server 2003?

 You might also want to check your Terminal Services Configuration on the server.  Check Start -> All Programs -> Administrative Tools -> Terminal Services Configuration -> Connections -> RDP-tcp

Right-click and click Properties.

Check the property tabs for that connection...Specifically the Network tab...the default number of connections should be 2...maybe that got changed?
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 2

Author Comment

by:cougar694u
ID: 24796480
Client machines = Win2k8r2, Win7, Win2k8, Win2k3r2, Vista, and WinXP.

Yes, the configured max connections is 2.

RDP works, I'm not getting denied, but when NOT in console/admin mode, you supply your credents, then it flashes the Applying Personal Settings, that dialog goes away, the background goes blue like it's loading the profile, then no icons and no task bar.  It sits there for about a minute, then closes the RDP session.

During this time, I can look at Task Manager and it says that session is Active.

Again, nothing in the Event Logs show any errors.

I'm currently RDP'd into the server via console/admin mode and can watch when other users try to RDP in and it fails.
0
 
LVL 2

Assisted Solution

by:skshoup
skshoup earned 200 total points
ID: 24796596
Check this out on the permissions side - same place as you were before for the connection properties..this is from Microsoft on how to limit to console only, so maybe you can work this in reverse...

Note the "In the Permissions for Everyone area, click to select the Deny check box to deny permission for Guest Access, and then click OK."  Maybe one of the built-in groups has "Deny" accidentally checked.  Last time I bumped into this...it was a permissions issue.

How to limit the number of remote sessions on a terminal server
To open the Terminal Services Configuration Tool, click Start, point to Administrative Tools, and then click Terminal Services Configuration.
In the console tree, click Connections.
In the right pane, right-click RDP-Tcp, and then click Properties.
On the Network Adapter tab, click to select 1 from the Maximum connections drop-down list.
On the Permissions tab, click Add, type Everyone in the Enter the object names to select (examples) box, click Check Names, and then click OK.
In the Group or user names area, click to select the Everyone group.
In the Permissions for Everyone area, click to select the Deny check box to deny permission for Guest Access, and then click OK.

Note This setting permits only one remote connection and only through the console, also known as session 0. To make a Remote Desktop connection to the server, use the mstsc.exe /console command to connect to the console session of a terminal server on a Windows XP-based computer or on a Windows Server 2003-based computer.
0
 
LVL 2

Accepted Solution

by:
cougar694u earned 0 total points
ID: 24797148
Found the problem:

Apparently the application that was installed on this server required TS, but the app owner removed TS.  When I reinstalled TS, the application was trying to be launched via TSCC > RDP-Tcp > properties > Environment > Start the following program when the user logs on.  I set that to run initial program specified by user profile and all is well.

I'm guessing that when TS was originally installed, and the app was set up, it worked, but uninstalling TS broke the app because it's a requirement (or was installed under TS prior to it's removal).

If I try to manually launch the app, it dies, thus probably the cause of my headache.
0

Featured Post

Gigs: Get Your Project Delivered by an Expert

Select from freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box. This is what Event viewer showed after trying to start the WDS service:  An erro…
This is my 3rd article on SCCM in recent weeks, the 1st (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_4466-A-beginners-guide-to-installing-SCCM2007-on-Windows-2008-R2-Server.html) dealing with installat…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

785 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question