Can't RDP to one server from only one computer

I have a computer that can access all servers on the network through RDP with the exception of one terminal server... let's name this server 'TS1'.  I am able to access TS1 through other means, ie: pings and shared folders.

While logged directly into TS1 and initiating an RDP session to the computer in question (but not logging the current user off), the computer is then able to RDP into TS1.  I'm starting to think the problem might be at the switch as the server is not logging any events on the failure.

Very disturbing...
itechbizAsked:
Who is Participating?
 
itechbizConnect With a Mentor Author Commented:
Almost forgot about the posting... well, interestingly enough, replacing the computer did not fix the issue as it began happening on other machines (not the new one though).

It seems that one of our engineers who has long since gone had put an internal reflexive rule concerning terminal services... and everyone was getting bounced around.  Never became a problem though until this.
0
 
KechkaCommented:
You normally can RDP to TS1 from any other computer from your network?
0
 
itechbizAuthor Commented:
That is correct.  Every machine on the network can RDP into TS1 with the exception of this one computer.
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
coredatarecoveryCommented:
This may be a permissions issue in your firewall.

Can this computer ping the server in question, just not rdp into it?
0
 
itechbizAuthor Commented:
I don't think it would be the firewall as they are all on the same subnet.  The computer can communicate with TS1 in every manner I have tested with the exception of RDP.

Again, though, let me restate that this computer can effectively use RDP to connect to any other server besides TS1.  TS1 is also licensed for 20 more users than are on the network currently.
0
 
coredatarecoveryCommented:
Software firewalls on the server or the client end are the most common cause of rdp not working on the same physical network.

(Was a stab in the dark)

can you assign a different physical address to the client computer and try again?

What happens when you rdp to the IP Address of TS1?

(remove the name resolution from the equation?)
0
 
itechbizAuthor Commented:
No software firewalls are being ran on either the terminal server or the client computers.  The computer is on DHCP and we have performed renews since the problem.  Also, the problem persists if you attempt to remote into TS1 using netbios name, fqdn, or IP address.

Maddening.....
0
 
coredatarecoveryCommented:
That's pretty crazy. I will ask a friend of mine who knows more than I do about the RDP protocol.

0
 
johnb6767Commented:
Whats the exact error you get, or where exactly does it fail... Do you get a login, or a failure?
0
 
itechbizAuthor Commented:
"This computer can't connect to the remote computer. Remote Desktop cannot find the remote computer.  Type the computer name or IP address again, and then try connecting." bla bla...

Yet I am connecting with the IP address and I can ping it.  It can only be found if an RDP session is initiated in the other direction.

0
 
itechbizAuthor Commented:
Points updated
0
 
coredatarecoveryCommented:
you can only ping if there is an rdp to the desktop unit in place?
0
 
itechbizAuthor Commented:
We are able to communicate with TS1 in any manner at any time with the exception of RDP... we can only RDP into the server though if an RDP session is initiated from the server to the computer.
0
 
johnb6767Commented:
start>run>cmd

telnet ts1 3389 (or your custom port if applicable)

Whast the result?
0
 
itechbizAuthor Commented:
Unable to test that today... I'll let everyone interested know in the morning
0
 
itechbizAuthor Commented:
Telnet into the server failed... also this morning the messages is simply that it is unable to connect and if trying again fails call ... well ... me
0
 
johnb6767Commented:
So something is blocking 3389 FROM this PC? Forgive me if this was stated already...

Can THIS machine RDP into others?
0
 
coredatarecoveryCommented:
port 3389 is blocked until a session is opened from the server to the client computer, then you can open the terminal server window fine.

(That's my understanding of the situation)

That would lead me to believe it's an issue with the server, not the client box.

The author said previously that there were no firewalls involved on either computer.

(I'm still thinking about what might cause this, I'll chip in if I come up with anything good.)
0
 
itechbizAuthor Commented:
Replaced the computer today... went for the easy solution, thanks for all your help though.
0
 
johnb6767Commented:
Slacker!!!!

Just kidding really.... Im glad you got it resolved at least....
0
 
johnb6767Commented:
Good find, thanks for the update.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.