Question Locked

Windows Server 2003 R2 with Remote Desktop Admin - Can't connect, no error

0 helpful
24 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Using Remote Desktop Connection in Vista, I used to be able to successfully connect to a couple of servers running Windows Server 2003 Enterprise running Remote Desktop Admin (not full Terminal Server licensing in place).

Both of these machines were upgraded to Windows Server 2003 R2. Now, when a Vista (or XP for that matter) client tries to connect to either of those servers with RDC, they find the server (name resolution seems to work), and I'm prompted for credentials. The RDC applet greys out as if it's about to connect, then about 1 second later, nothing happens and I'm back to the RDC prompt (asking me for the server name again). No error. This occurs on both of the R2 servers (both running Enterprise, one is a domain controller, the other is not).

RDC functions fine when connecting to non-R2 2003 servers.

I don't show anything in the security log for these R2 servers that show that credendials were wrong. If I purposely enter the wrong credentials, the same effect, no prompt that the credentials were wrong.

DNS seems to be fine as I can ping and remote connect to these machines using other remote control software (Radmin). I've tried un-installing that thinking it was a problem with R2 and the video hook drivers, but no luck.

Firewall settings on the R2 servers also show that Remote Desktop is enabled as an exception. I've also tried completely turning off the firewall, no luck.

Terminal Services Manager is running fine and showing that RDP-TCP listener is running.

Thanks all.

24 replies

by retro77

Is RDP enabled on the server? My computer, Properties...yada yada...

by mark

Yes, RDP enabled is enabled. If it disable it, I get the usual error from the client indicating it can't connect, but when I enable it, I don't get that error, but I get the strange behaviour (like it's just ignoring it or can't draw the screen, no error). Thanks retroman.

by retro77

You have a group in there as having permissions and the group contains the user account that your are trying to connect with.

Also try not connecting at full screen, dont bring your printers from your client...also set it to not redirect sounds. Try turning all that off and remoting again.

Event viewer: getting errors on either side?

by slagvd

Thanks retro77, you helped me sort this out after YEARS of nuisance. In my case, I had to change colour depth from 32bit to 24bit. Presumably some graphics card incompatibility. So there is a god...

by scott_heath

Have you tried restarting the service? Can you telnet to port 3389 on the boxes in questions? Can you access them from an XP box with RDC 6.0?

by mark

Hi Scott, I have the same effect when trying to access these 2003 R2 boxes from XP as well. I don't see a RDP service to restart, the only services I see are Terminal Server (which can't be stopped or re-started), and Remote Desktop Helper Service, which I restarted, but no luck. I don't have telnet service running on these servers. Port 3389 is open as I completely disabled the firewall on the R2 machine to rule out firewall issues.

When this machine was just regular 2003 Enterprise (not R2), it had no problem with remote desktop administration, but now that it has been upgraded to R2, I get this strange side effect, which behaves unlike anything I've ever seen when remote desktop just doesn't connect. This one seems to connect, but won't display the screen.
Thanks again for your help!

by scott_heath

I forgot you can't restart the terminal server service. Have you rebooted the box?

Were you able to telnet to port 3389? You don't need a telnet server running, if the port is listening it will connect. If it won't then there is either an issue with the service or maybe there has been a network change. Does the communication have to cross routers?

by thevirtualone

What kind of router do you have?
What version is it?
Do you have the latest firmware?
Is it VISTA compliant?

I'm on a mission here.

by mark

Thanks o-VirtualOne.

The router is a Linksys RV042 on firmware 1.3.9, their latest. No info on the site about Vista support. But I get the same effect using RDC on XP (5.x and the latest RDC 6.0). Even between 2003 servers have the same problem. The only servers that allow you to RDC into them is the 2003 nonR2 boxes.

Happy Thursday eh?

by thevirtualone

the service is called RDP. not RDC. (pet peev)

buy a new router. I spend good money for these things and I suggest Watchguard.

by mark

Hey retro, I'm using the domain admin username/password, and tried the local 2003 R2 server admin who have TS privlidges. I tried not using full screen, also turned off forwarding of all local resources like printers and clipboard and sounds, still no luck.

Event viewer isn't generating any errors on either side of the fence. I'm guessing something unique in 2003 R2 vs. regular 2003 has messed up RDP. This machine has no software on it either, just a vanilla install of 2003 enterprise server, then applied all updates, RDP ran fine, then upgraded it to 2003 R2, and this started. What's weird is I can duplicate it on 2 other machines, all different brands (HP server and another a Dell), same effect, one of them is a web server, same problem with that one, once it got upgraded to R2, no RDP anymore. I verified that 2003 R2 does not require full Terminal Server licencing, it still comes with the remote desktop for administration free license (2 per box I think to allow 2 users to RDP into the machine for admin purposes using RDC).

Thanks for all your help.

by wescrook

I also have the same problem from ANY machine (RDP 5x or 6.0) and it's server 2003 NON- R2 on the other end...

...tried all that's been said in this forum - nuthin' yet!

Wes

by mark

Hey wes, no luck on my end yet. Tried everything, although MSFT support is stumped, they have a bunch of other open cases on the same topic, specific to R2. I can easily re-create this on many machines even using VPC. Everything works fine until you install upgrade to R2.

In your case, you don't have R2, but are you running SQL 2000 or 2005 (any edition) on the same box? I ask as SP4 of 2000 and SP2 of 2005 broke RDP on two of my non-R2 boxes.

by wescrook

....yesterday....

It was the default Windows drivers for my x600 video card that I threw in there. I downloaded the XP drivers (which work in ws2k3) and that solved my problem! Seems like the default Windows drivers were messing up emulation somehow...

Thanks!

by mark

Hi Scott, telnet servername 3389 just yields a flashing cursor, no error, so I'm not sure if I'm connecting successfully? I think I am , because if I telnet to a port that is not open, I am told "Could not open connection to the host on port xxxx. But telneting on 3389 does seem to connect.

Same effect on the second R2 server. 3389 seems to accept the telnet connection.

I have rebooted both servers multiple times.

Thanks again Scott for your help.

by scott_heath

Well at least we know that the service is in fact listening and accepting connections.

Just for grins, have you tried specifiy the port? Have you tried connecting using the /console option? Have you checked TS Manager to make sure it doesn't think you are connected? Have you check the App and Security logs on the client and server?

Let me know if you have any questions.

by mark

Hi Scott, just wanted to thank you for your assistance, it ended up being the ATI Catalyst Suite which is installed with the video driver (these servers have ATI Radeon X550's in them).

Removing the Catalyst Suite and using just the ATI driver alone did the trick. Don't know why as the Catalyst doesn't change the video driver, it just gives you a control panel utility. Go figure.

I've submitted a KB article request to AMD as it seems to effect at least 5 different Radeon cards that I have.
Thanks again,
Mark

by mark

I believe these servers both have the same ATI Radeon X600 in them, although they're using the ATI XP/2003 driver from the website, not the default Windows driver. But perhaps it's related (video hook or version of the catalyst driver).

Out of interest, we're your side effects the same as mine? See my original post about how RDP was behaving from the client PC.

THanks!

by mark

Wescrook, thank you, you're post led me to further investigate the ATI drivers and tweak them a little more. Although I had the latest ATI drivers with Catalyst, I decided to remove the complete suite and re-install without the Catalyst suite, just the vanilla ATI driver. Behold, RDP is now functioning.

Thanks Wescrook! And thank you TheVirtualOne, Scott and Retro for all your help as well.

by wescrook

In response to your reply 2 posts ago, yes, my symptoms were exactly the same - attempt to connect, gray out for about 2 seconds, then return to the connection window with no error whatsoever.

Glad I could be of help!

by mark

Hi Retro, just wanted to thank you for your assistance, it ended up being the ATI Catalyst Suite which is installed with the video driver (these servers have ATI Radeon X550's in them).

Removing the Catalyst Suite and using just the ATI driver alone did the trick. Don't know why as the Catalyst doesn't change the video driver, it just gives you a control panel utility. Go figure.

Thanks again,
Mark

by sina.ebadi

I had the same problem and your final comment did help me!!

by mark

Hi VirtualOne, just wanted to thank you for your assistance, it ended up being the ATI Catalyst Suite which is installed with the video driver (these servers have ATI Radeon X550's in them).

Removing the Catalyst Suite and using just the ATI driver alone did the trick. Don't know why as the Catalyst doesn't change the video driver, it just gives you a control panel utility. Go figure.

Thanks again,
Mark

This discussion is closed to new replies.