Remote Desktop within home network restriced by Internet connection

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #11

    Based on your IP configuration it would appear that your router is giving out a DNS suffix which essentially attaches a domain name at the end of any hostname request:

    For example: DNS Suffix = 'dlink.com' then josh-pc would become 'josh-pc.dlink.com'

    Unless you have a public domain name any domains with .com at the end typically are sent straight to the routers DNS servers that it has (ISPs one) to get resolved. This will then fail because there is no record of OldBoy.dlink.com.

    There are two ways around this that I can think of. Firstly, We can try to find how your machines are receiving a DNS suffix and then remove them to see if that resolves the issue. Or we can create a manual DNS entry if you will on your computers hosts file so that any information sent to the hostname 'OldBoy' won't go to the router but straight to the ip address you specify.

    Please understand that if you chose to add a manual entry then you will need to ensure that the computer 'OldBoy' has a static IP address that will never change otherwise the mapping will not work.

    What option would you like?

    Many Thanks,
    Josh! :)
      My Computer


  2. Posts : 16
    Windows 7 Professional 64 bit and 32 bit
    Thread Starter
       #12

    Thanks Josh,
    I prefer not to use manual. I have checked the machine I am trying to RDC to, and it has the dlink.com suffix as well.

    John
      My Computer


  3. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #13

    In that case, what is the make/model of your router? You are going to have to change a few settings to see if it removes the suffix.

    Just a quick question, have you tried to RDC using the hostname and DNS suffix (dlink.com) to see if it connects? If not then can you tell me the results

    Josh :)
      My Computer


  4. Posts : 16
    Windows 7 Professional 64 bit and 32 bit
    Thread Starter
       #14

    It's a D-Link DSL-2640R firmware v1.22 and Hardware rev B2.
    Tried RDCing hostname.dlink.com but same error.

    Before we go any further, I have been through every menu on the router and there is no mention of dlink.com. As I mentioned in an earlier post, this router was supplied by TalkTalk and I believe that they have modified it.

    John
      My Computer


  5. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #15

    ftp://ftp.dlink.co.uk/dsl_routers_mo..._B1_Manual.pdf

    Please follow the steps to access your DNS settings and ensure that Dynamic DNS is disabled

    Once done, reboot the router and both machines that you wish to connect

    Hopefully this should resolve your issue

    Josh :)
      My Computer


  6. Posts : 16
    Windows 7 Professional 64 bit and 32 bit
    Thread Starter
       #16

    Thanks for this Josh, however DDNS is not enabled on this router. Also note that the manual is for Hardware Rev B1 and the ISP has provided the router with hardware Rev B2 (not mentioned on the D-Link site).
      My Computer


  7. Posts : 3,371
    W10 Pro desktop, W11 laptop, W11 Pro tablet (all 64-bit)
       #17

    Interesting discussion regarding making RDC work and hope you get it solved but if you just want a solution that will work, take a look at the free software: TeamViewer - Free Remote Control, Remote Access & Online Meetings. You won't need to worry about port forwarding or DNS entries and the like.
      My Computer


  8. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #18

    john265 said:
    Thanks for this Josh, however DDNS is not enabled on this router. Also note that the manual is for Hardware Rev B1 and the ISP has provided the router with hardware Rev B2 (not mentioned on the D-Link site).
    I cannot seem to find a manual to your router so I cannot offer any precise steps

    Could you ensure that your Local Domain Name set on the router is blank. Also you can change your DNS servers in the router to the following:

    Primary: 8.8.8.8

    Secondary: 8.8.4.4

    Once done please apply and then test the RDC as well as a ping. My feeling is that your router is forwarding traffic straight to your ISPs DNS servers when it shouldnt't

    Josh :)
      My Computer


  9. Posts : 16
    Windows 7 Professional 64 bit and 32 bit
    Thread Starter
       #19

    Well there is no facility in the router interface to set the domain name. The router DNS section was set to: Obtain DNS server address automatically. I changed it to use the DNS servers that you suggested and RDC worked immediately.

    Ping results below. Note it now uses IPv6 address. The question is, should I leave it like this or will there be repercussions elsewhere?

    Pinging OldBoy [fe80::2839:3779:89f9:ba72%10] with 32 bytes of data:
    Reply from fe80::2839:3779:89f9:ba72%10: time=3ms
    Reply from fe80::2839:3779:89f9:ba72%10: time=1ms
    Reply from fe80::2839:3779:89f9:ba72%10: time=23ms
    Reply from fe80::2839:3779:89f9:ba72%10: time=45ms
    Ping statistics for fe80::2839:3779:89f9:ba72%10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 45ms, Average = 18ms

    [When I look at ipconfig /all it still shows dlink.com as a DNS suffix.]

    Thanks
    John
      My Computer


  10. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #20

    The DNS servers are ones used by Google and offer the same response time as browsing to Googles webpage near enough

    The IPv6 results show the hostname being resolved to the link local address. This is an address used to communicate with local computers rather than using its private address. This is perfectly acceptable and unless you try to ping a hostname not on your LAN you should not have any interference with the DNS suffix.

    It would seem that you suspicion with your ISPs DNS servers may be correct...


    Josh :)
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:01.
Find Us