Dynamic DNS not working in a certain location

[gilesitis]

Hi all,

Does anyone know why the DDNS I setup is not working with RDP in a particular location? I understand this only works outside the network of the computer you're trying to access. It works fine from my home, but it will not work from the network close to the office where the destination computer is located. This network is a separate network from the destination computer with a separate internet connection. The funny thing is I can remote in from there just fine if I use the actual IP in the RDP. Hope this makes sense.

The only thing I can think of is that network is pointing to OpenDNS DNS Servers for content filtering, but not sure if that would cause DDNS not to work.

If anyone has any suggestions I would so greatly appreciate it!

 

[tek9]

I think it's possible to block DDNS domains entirely with OpenDNS. One simple way to check would be to temporarily use Google DNS servers. Note that you might have to change the DNS settings on the router itself if they have a firewall rule in place blocking other DNS servers and such.

 

[gilesitis]

Good idea. I did some reverse engineering by changing my home network's DNS to the OpenDNS servers, and it still lets me connect with the DDNS host name. I am wondering if it's not something else now.

 

[FremontPC]

Yeah, they could have the other network locked down tighter. Did you try pinging the ip of the DDNS service from the network in question?

 

[Moltuae]

In addition to pinging, I would try doing a tracert from the network in question. Might give you some clues as to how/if the route taken reaches the WAN.

 

[nlinecomputers]

What precisely do you mean by "not working"? Does it timeout? 404 error message? What exactly happens when you do this? What are the ISPs involved? Firewalls in place? Hardware? Software?

 

[nlinecomputers]

Also who is providing the DDNS service?

 

[YeOldeStonecat]

Since you say it works via IP address...we can forget about firewall rules 'n such.
So try pinging the DDNS name from that location which cannot resolve....do you get the correct IP in resolution? If not...whatever DNS server/service that location is using, is not updating records for that particular DDNS service that is being used.

 

[nlinecomputers]

I've seen some ISPs block DDNS.

 

[gilesitis]

In addition to pinging, I would try doing a tracert from the network in question. Might give you some clues as to how/if the route taken reaches the WAN.

Thank you. I haven't but I will definitely try that.

 

[gilesitis]

Also who is providing the DDNS service?

DYNU

 

[gilesitis]

What precisely do you mean by "not working"? Does it timeout? 404 error message? What exactly happens when you do this? What are the ISPs involved? Firewalls in place? Hardware? Software?

It says:

Unable to connect to remote PC. Please verify Remote Desktop is enabled, the remote PC is turned on and available on the network, and then try again.

The ISP is Frontier and the computer does have Webroot Internet Security Firewall.

 

[gilesitis]

Since you say it works via IP address...we can forget about firewall rules 'n such.
So try pinging the DDNS name from that location which cannot resolve....do you get the correct IP in resolution? If not...whatever DNS server/service that location is using, is not updating records for that particular DDNS service that is being used.

Thank you. I will try pinging that name to see what happens.

 

[TurricanII]

Also, force the problem computer to use e.g. Google DNS 8.8.8.8 & 8.8.4.4

Assuming the firewall on the network allows outbound DNS to these IP's from your workstation, that might prove DNS blocking on the firewall.