Connection by IP works but not by name

[chance2]

I use local connection only. When I first started using Remote Control, I could connect to a PC by using its name. For some reason, I can no longer connect to PCs by their name; I have to enter their IP addresses in order to connect. Is there any reason why connecting by name would stop working? IP addresses can change, but the name stays the same, so I would prefer to connect by name.

[Administrator]

Which Error message do you get?

[chance2]

Error 10060 ("Host unplugged/disconnected from network OR behind router/firewall/antivirus OR wrong IP address.") Immediately after I got this error message trying to connect by name, I connected by IP address and was successful.

[Administrator]

try to ping the name of your PC

Start - run - write "cmd"
write - ping PCname (the name of PC you want to connect to)

which result do you get?

[chance2]

I was getting an IP address owned by my ISP (Frontier). But now I am getting the correct IP address for my computer. So it seems to go back and forth sporadically.

[Administrator]

Did you try to ping the name of your remote PC?

[chance2]

Yes, if I have a computer "xxx" and type "ping xxx" I get "xxx.ftrdhcpuser.net" as the full name. This name had been resolving to an address owned by Frontier, my ISP, who controls ftrdhcpuser.net. After reading the experiences of another user on dslreports.com, plus a little tweaking on my DSL modem, it seems that the name is again resolving correctly to the local IP address of my computer, which has made connecting by name work again. It is not an issue with the software. Thanks for the response. Pinging my computer by name started me down the path to finding the solution online.

[Administrator]

You may try Account Connection service that does not require any IP address to establish a connection with a remote PC.

[NetcavaKafe]

Marius are you here?

[Administrator]

Please, clarify your request

[Function]

This is how I solved the issue:

It appears the issue had to do with the DhcpDomain registry key. For some reason it was set to my ISP's domain on one computer and my business's domain on another even though both were my home computers. Setting them to blank fixed the issues I was having.

Edit DhcpDomain="" in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\<the interface that corresponds with your current connection>\

[Administrator]

As far as I understand, you had a problem with Direct IP connection?
Why you do not want to use Online Account Connection instead?
In this case you will not have problems with IP-addresses or DNS-names.