Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Remote Desktop not working only for some computers


  • Please log in to reply
10 replies to this topic

#1 remotelylost

remotelylost

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:05:07 AM

Posted 14 April 2016 - 04:55 AM

Hi all, 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 running 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 SS 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.


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!



BC AdBot (Login to Remove)

 


#2 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:07 PM

Posted 14 April 2016 - 11:19 AM

make sure the local firewalls allow remote connections

if you want to ping make sure icmp is allowed in the firewall



#3 Darktune

Darktune

    Very Purple


  • Members
  • 1,139 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Wales
  • Local time:10:07 PM

Posted 14 April 2016 - 06:05 PM

Hello remotelylost,

 

It seems the ping failures between all PC's you have is quite sporadic. Check the DNS settings on each PC and make sure they're all pointing to the same DNS server. To check your DNS open up elevated command prompt and enter the following command;

ipconfig /all

The line you are looking for is "DNS Servers"

Kind regards,

 

Darktune


It's very hard to imagine all the crazy things that things really are like. 

Electrons act like waves.. no they don't exactly, they act like particles.. no they don't exactly.

Words and ideas can change the world.


#4 remotelylost

remotelylost
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:05:07 AM

Posted 14 April 2016 - 09:01 PM

Hello remotelylost,

 

It seems the ping failures between all PC's you have is quite sporadic. Check the DNS settings on each PC and make sure they're all pointing to the same DNS server. To check your DNS open up elevated command prompt and enter the following command;

ipconfig /all

The line you are looking for is "DNS Servers"

Kind regards,

 

Darktune

 

I've checked, and the DNS Servers between D, 1, and S are the same. 2 has a different DNS server, while 3 is currently being used so I'm unable to access it. In any case, my focus is getting S to RDC to D.

For S, the DNS Server line is listed under "Wireless LAN adapter Wireless Network Connection", while D and 1 has it listed under "Ethernet adapter Local Area Connection".

 

Is there any significance to this? It appears that both S and D are pointing to the same server, but somehow they can neither ping nor connect to one another remotely. 

 

 

Btw, is there a difference in launching cmd prompt with UAC and without? Would the result for the ipconfig command ever differ between the two cases?

 

 

make sure the local firewalls allow remote connections

if you want to ping make sure icmp is allowed in the firewall

 

Okay, I've googled and read up a little on icmp. Would this be a good guide to enabling icmp? --> http://www.hammer-software.com/icmpgphowto.shtml

 

Also, in this situation which icmp type needs to be allowed? Are 0, 3, 8 and 11 sufficient?

 

It seems that allowing icmp allows for a computer to be 'visible' by others, so that incoming pings can be received. What I don't understand however is that D is currently able to be ping-ed by 1,2&3, even without these icmp configurations. Why is that the case?



#5 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:07 PM

Posted 14 April 2016 - 11:45 PM

what firewall software are you using?

 

icmp is used by ping and tracert.  Because you can ping doesn't mean its really visible.  It just means something is answering [printer, pc, tablet, refrigerator ...]. Being on a local network this isn't of concern.  It is when you wan port responds to ping can you have troubles.

 

your link deals with group policy in a domain.  not your situation.

no public dns server knows your host names or their ip addresses.  public dns servers don't do that but private ones do.  Since you are in a peer to peer network you have no local dns server and you are pointed to either the gateway or a public dns server.  local name resolution is done by broadcasts and then cached locally.  no worries there.

 

Everyone on the network should be getting the same dns settings.  Since they are not it would infer someone has set static entries on 2

 

post a ipconfig /all from both D and S.  If D can be pinged by 1,2,3 but not S either D's firewall is set to block S or S is configure to not allow D.  Again it comes down to what program can block access and that is down to firewalls.


Edited by Wand3r3r, 14 April 2016 - 11:46 PM.


#6 remotelylost

remotelylost
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:05:07 AM

Posted 15 April 2016 - 05:01 AM

what firewall software are you using?

 

Again it comes down to what program can block access and that is down to firewalls.

 

To my knowledge, the only firewall running is Windows Firewall, for both and D.  How should I enable access between S and D?



#7 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:07 PM

Posted 15 April 2016 - 08:36 AM

Google "how to enable windows firewall exception for remote desktop" for the steps.

 

Still looking for those ipconfig /all



#8 remotelylost

remotelylost
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:05:07 AM

Posted 17 April 2016 - 09:57 PM

Firewall for D has been enabled for "Domain" and "Home/Work (Private)". Even after enabling it for "Public" S is still unable to remotely connect.

 

 

ipconfig for D:
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : ComputerD
   Primary Dns Suffix  . . . . . . . : abc.xyz.my
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : abc.xyz.my
 
Ethernet adapter Local Area Connection:
 
   Connection-specific DNS Suffix  . : abc.xyz.my
   Description . . . . . . . . . . . : Intel® 82567LM-3 Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-57-C2-RE-73-55
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b0f2:eecb:31:f461%10(Preferred) 
   IPv4 Address. . . . . . . . . . . : 182.13.136.99(Preferred) 
   Subnet Mask . . . . . . . . . . . : 232.232.233.0
   Lease Obtained. . . . . . . . . . : Monday, 18 April, 2016 7:56:32 AM
   Lease Expires . . . . . . . . . . : Monday, 18 April, 2016 12:26:33 PM
   Default Gateway . . . . . . . . . : 182.13.136.1
   DHCP Server . . . . . . . . . . . : 182.13.136.1
   DHCPv6 IAID . . . . . . . . . . . : 234098472
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-4B-74-19-20-00-24-E6-FD-49-22
   DNS Servers . . . . . . . . . . . : 257.252.0.132
                                       257.252.0.134
   Primary WINS Server . . . . . . . : 257.252.4.5
   Secondary WINS Server . . . . . . : 257.252.4.25
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Tunnel adapter isatap.abc.xyz.my:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : abc.xyz.my
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
 
 
ipconfig for S
 
Windows IP Configuration

 

   Host Name . . . . . . . . . . . . : ComputerS

   Primary Dns Suffix  . . . . . . . : abc.xyz.my

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

   DNS Suffix Search List. . . . . . : abc.xyz.my

 

Wireless LAN adapter Wireless Network Connection 2:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : 

   Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter

   Physical Address. . . . . . . . . : 27-6Q-7G-99-C8-7F

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

 

Wireless LAN adapter Wireless Network Connection:

 

   Connection-specific DNS Suffix  . : abc.xyz.my

   Description . . . . . . . . . . . : Intel® Centrino® Advanced-N 6205

   Physical Address. . . . . . . . . : 27-6Q-7G-99-C8-7E

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::16f2:635c:1a16:c67e%15(Preferred) 

   IPv4 Address. . . . . . . . . . . : 182.13.145.47(Preferred) 

   Subnet Mask . . . . . . . . . . . : 232.232.231.0

   Lease Obtained. . . . . . . . . . : Monday, 18 April, 2016 8:23:08 AM

   Lease Expires . . . . . . . . . . : Monday, 18 April, 2016 10:52:43 AM

   Default Gateway . . . . . . . . . : 182.25.144.1

   DHCP Server . . . . . . . . . . . : 1.1.1.1

   DHCPv6 IAID . . . . . . . . . . . : 374467727

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-E2-CF-CE-88-51-FB-CC-90-F5

   DNS Servers . . . . . . . . . . . : 257.252.0.132

                                       257.252.0.134

   Primary WINS Server . . . . . . . : 257.252.4.5

   Secondary WINS Server . . . . . . : 257.252.4.25

   NetBIOS over Tcpip. . . . . . . . : Enabled

 

Ethernet adapter Local Area Connection 2:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : 

   Description . . . . . . . . . . . : Bluetooth Personal Area Network

   Physical Address. . . . . . . . . : G2-19-6R-E9-64-84

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

 

Ethernet adapter Local Area Connection:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : abc.xyz.my

   Description . . . . . . . . . . . : Intel® 82579LM Gigabit Network Connection

   Physical Address. . . . . . . . . : 22-84-RG-DD-30-R6

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

 

Tunnel adapter isatap.stf.nus.edu.sg:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : 

   Description . . . . . . . . . . . : Microsoft ISATAP Adapter

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

 

Tunnel adapter isatap.{A321514B-127C-425F-BBE9-5D2CA99AA266}:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : 

   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

 

Tunnel adapter isatap.{0BE9CDFA-DD88-4171-96FA-3168C8061542}:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : 

   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

 

Tunnel adapter Teredo Tunneling Pseudo-Interface:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : 

   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

 

 

I'm unsure about the security risks of posting the full ipconfig for my computers, so i've changed some digits. Those which were originally the same, however, have been kept the same.



#9 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:07 PM

Posted 18 April 2016 - 09:30 AM

There is no risk to posting ipconfigs.

 

Frist thing that is obvious is the subnet masks are invalid. There is no 232.232.231/233.0 subnet masks

Without proper subnet masks I can't tell if the two networks can talk to each other

 

D is using 182.13.136.1 for dhcp but S is using 1.1.1.1 which means they are connecting to different dhcp servers

D has 182.13.136.1 for gateway whereas S has 182.25.144.1 for gateway which means they have different gateways AND your network has multiple gateways.

D is at 182.13.136.99 whereas S is at 182.13.145.47.  Notice the 3rd octet is different?  They are in different networks which means without a router or correct mask of [255.255.224.0] these ips cant talk to each other.

 

Last but not least these are public ips when they should be private.  So either your company is using 8000+ public ips which is doubtful or you are improperly using public ip privately which is a problem in itself.


Edited by Wand3r3r, 18 April 2016 - 09:31 AM.


#10 remotelylost

remotelylost
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:05:07 AM

Posted 18 April 2016 - 10:18 PM

Thank you so much for the break down of information. I think the issue is as you mentioned, the computers belonging to different networks. My guess is that the wifi connects to a different network to the lan cable.

 

They are in different networks which means without a router or correct mask of [255.255.224.0] these ips cant talk to each other.

 

 

The subnet masks for is 255.255.254.0. I cannot access for now but it differs by one digit, as in the example above. IIRC it should be 255.255.256.0

 

I'll see if it's possible to change the subnet mask, hopefully this will work once that is done. 

 

Thanks very much once again!



#11 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:02:07 PM

Posted 19 April 2016 - 10:04 AM

There is no such subnet mask as 255.255.256.0

You would need all talking on 255.255.224.0 subnet mask to not have to use a router.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users