Remote Desktop only working for some computers but not others

remotelylost · Apr 13, 2016

I've been having some issues with Remote Desktop Connections, and I can't seem to find an answer after googling and looking through previous threads. Hoping to hear everyone's thoughts on what I may be missing out on.

Situation

There are 5 computers within my work place -
(all on Windows 7, SP 1)

Desktop (D), connected via LAN cable
Spare laptop (S), connected to wifi
Laptop 1,2,3 (1,2,3), connected via LAN cable and wifi

I hope to remotely control the desktop unit D from the Spare unit S, but when I try to I encounter the standard error: "Remote Desktop can't connect to the remote computer for one of these reasons". I am able to remotely connect to D using Laptops 1-3, but unfortunately these 3 laptops are often used for other reasons so I would still need to use S most of the time.

Between Laptops 1-3 and S, S seems to be able to remotely connect to laptop 3, but the same error appears for laptops 1 and 2.

Connecting from D to the other units, the standard error appears in each scenario. I find this strange but it's not important; I do not have to remotely control the laptops from my desktop.

To summarize,
S RDC to D = doesn't work. <-- what I hope to fix
1,2,3 RDC to D = works
S RDC to 1,2 = doesn't work
S RDC to 3 = works.
D RDC to 1,2,3,S = doesn't work

When I try to ping the various units, this was what I observed.

S ping to D : timed out
1,2,3 ping to D: 0% lost
S ping to 1: 0% lost
S ping to 2: timed out
S ping to 3: 0% lost

In the other direction,
D ping to 1,3: 0% lost
D ping to 2: timed out
D ping to S: timed out

Hope the information is relevant. Would appreciate advice on how I may get S to remotely connect with D, or an explanation on why it may not be possible to accomplish what I hope to do.

Thanks in advance!

basroil · Apr 13, 2016

Sounds like a router/switch configuration issue where the subnetworks formed are all screwed up

Solandri · Apr 14, 2016

remotelylost :

Are you sure there isn't a second DHCP server on the network? That's the only explanation I can think of for contradictory results like this (able to ping one way but not the other - ping by its very nature requires bi-directional communication).

It could be as simple as someone at work wanting wifi in their room, so they buy a wifi router and plug its LAN port into your existing network. That gives your network two DHCP servers and an IP address conflict for the gateway, and can cause asymmetrical connection problems like this.

remotelylost · Apr 14, 2016

basroil :

Okay, what would you recommend I do to determine where it's screwed up, and how can I go about fixing it then?

basroil · Apr 14, 2016

remotelylost :

Easiest way, swap computer locations and see if it works. That is of course if you don't know how to manage IP routing (not too difficult)

remotelylost · Apr 14, 2016

Solandri :

Ah, I'm afraid I'm not well versed in servers and networks. I think I understand your point, though. For laptops 1-3 they are both plugged into a LAN cable and connected to the wifi, so it may be causing what you're suggesting.

Are there any solutions to this, then? My thinking is that since S is able to ping to 2, and 2 is able to ping to D, technically S should also be able to ping to D? I'm working with the assumption that "ping" = "RDC", haha.

basroil · Apr 14, 2016

remotelylost :

Not quite. Assume each computer is a person on a hill that can see all those below but only a little uphill unless the person uphill calls them. In this case, your D is the one on the bottom and S and 2 are further up top both next to each other. D can't see anyone, but S and 2 can see each other and D.

remotelylost · Apr 14, 2016

basroil :

Alright, I will give that a go then. Thanks for the suggestion!

remotelylost · Apr 14, 2016

basroil :

Thanks for the analogy. Would it be correct to say then that computer 1 needs to be able to 'see' computer 2 in order to connect to it remotely then? IOW, if S can ping to D, it should be able to RDC to it (once RDC settings have been configured properly and all). Is this correct?

basroil · Apr 14, 2016

remotelylost :

Yes, but it's only part of the equation. You need to make sure that the necessary ports are open

remotelylost · Apr 15, 2016

basroil :

I see. What are these necessary ports then, and how can I make sure that they're open? I've just read that icmp can sometimes be an issue when it comes to remote desktop connections, is this related to the ports?

basroil · Apr 15, 2016

remotelylost :

for RDP you need 3389 on TCP

remotelylost · Apr 17, 2016

basroil :

Thanks for your help so far. I've checked; the port 3389 is open. I've tried opening the Public ones as well, but RDP still doesn't work even with those open.

Since laptops 1,2,3 can connect to D with no problem, could it be that it's only S that is being denied access, for some reason? Is this possible?

basroil · Apr 17, 2016

remotelylost :

Certainly possible, either from firewalls or network routing issues. In your case it sounds like a network routing issue, so you should actually map out your network with pen and paper and see where packets have to flow from and too, as well as possible subnetworks you are accidentally making

remotelylost · Apr 18, 2016

basroil :

I see then. Do you have any advice on how one may learn how to troubleshoot network routing problems?

Search

Remote Desktop only working for some computers but not others

remotelylost

Commendable

basroil

Glorious

Solandri

Illustrious

remotelylost

Commendable

basroil

Glorious

remotelylost

Commendable

basroil

Glorious

remotelylost

Commendable

remotelylost

Commendable

basroil

Glorious

remotelylost

Commendable

basroil

Glorious

remotelylost

Commendable

basroil

Glorious

remotelylost

Commendable

TRENDING THREADS

Latest posts

Moderators online

Share this page