Remote Desktop connection problems

By jfuller05 ·
I've been using the remote desktop connection for me and a user outside our network to login to our server(a) for certain things. This week, the user calls and says she's not able to remotely connect to the server(a). I tried to remote in (I'm in the network) and I couldn't connect either. However, I was able to remote in to our other server(b).
I can see and access files on the (a), but I cannot connect to it to use remote desktop. Everything is fine with TS licensing, I couldn't find any problems there. Also, even if there were TS problems, shouldn't I still be able to use remote desktop (I believe at least one user can) without TS? I think so, so that makes this problem even stranger to me.
Anyway, the user was able to get her work done another way, but I still want to fix this problem. I believe it would be a hardware issue.
Any suggestions?
The user logins via VPN through our SonicWall, but I don't think that is an issue, since I can't even establish a connection within the network. Port 3389 is open for remote desktop. So it's not a firewall issue.

Server A: Windows Server 2008 standard.
Server B: Windows Server 2008 R2
Client Machines: Windows XP Pro SP3

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -


by christianshiflet In reply to not going to reread all t ...

I believe you stated that this is a DC, as well. Can you (locally logged in from a DC) open up the Domain Controller Security Policy from Administrative Tools. In there go to Local Policies -User Rights Assignment and look for the settings for Allow Logon to Terminal Server, Allow Logon Locally, Deny Logon through Terminal Services, and Deny Logon Locally. Is there anything there that could cause your issue?

Collapse -


by christianshiflet In reply to not going to reread all t ...

Can you check out and verify that the registry setting on that server is correct for the incoming port on the server (that it hasn't been, for whatever reason, modified)? Presumably if you have external users accessing numerous internal servers with the same WAN IP, there must be some port forwarding happening somewhere.

Collapse -

Everything is correct in the security policies...

by jfuller05 In reply to not going to reread all t ...

I also found the entries to be correct in the registry.

I really appreciate the help.

Collapse -


by christianshiflet In reply to not going to reread all t ...

Is it possible the port is already in use by something else? Try running netstat -o to see all open ports and see if something is locking 3389. I have seen DNS lock a large range of ports. Check out for info on checking the reserved ports and adding exceptions, if need be.

Collapse -

Nothing is using 3389...

by jfuller05 In reply to not going to reread all t ...

netstat -o didn't show anything using 3389.

Collapse -

Everything points to you being able to RDP in

by CG IT In reply to Under server roles, TS is ...

on the server side of things. You've said you've checked everything everybody suggested which pretty much eliminates all the obvious problems of why you can't RDP in.

so all our suggestions end up being that 20 questions game.

The "not so obvious" problems could take up another 50 questions...

Personally, if the server itself will allow RDP sessions, and you can ping the server, there's no firewall settings restricting communications and no security policies restricting RDP sessions, you quess as to what the problem is, is probably as good or better than anyone else's guess.

Collapse -

I realize that, I really appreciate all of the help...

by jfuller05 In reply to Everything points to you ...

there has to be a underlying problem (obviously).

Thanks for all the help and time you put in.

I'll probably just recover from a backup if I can't figure it out soon.

Thanks again.

Collapse -

Everyone, thanks for all of the help you offered me.

by jfuller05 In reply to Remote Desktop connection ...

I appreciate it <b>very</b> much. This server has given me more work since I started here than any computer has ever given me.

I think it's time for wipe-reinstall.

Again, thank you all so much.

Collapse -


by CG IT In reply to Everyone, thanks for all ...

caulk this one up to the "Windows never ceases to Wonder" list.

Collapse -


by jfuller05 In reply to Remote Desktop connection ...

I can remote in to the server using GoToMyPC...

I thought I would post my updates to this crazy problem in case anyone else ever encounters this monster we can share ideas.

I guess since the outside user can access the server with GTMYPC, I can lower the priority of this problem. The server room is not that far away from my office, so it's not like I really need it.
I've been putting duties of this server on to our new one because the server just isn't acting like it used to.
Plus, I like WS2k8 R2 a little bit better. :)

Related Discussions

Related Forums