AC1750 router doesn't seem to support remote desktop.

In no particular order - Microsoft uses the term "Remote Desktop" both in their Windows 10 literature and in reference to the application foiund in "Windows Accessories > Remote Desktop Connection". if Netgear is not familiar with the term, i would suggest they read up on what > 75% of their residential users are using (ie Windows 10). "Fiddling around" is a polite way of saying that this was not a drop in replacement. My previous network with 6 PC's configured with static IPs set up between 10 - 100, with the DHCP reserved block 101 to 140. The starter app set up through the phone made some assumptions about where the DHCP address block was and it did not match my original scheme. it took some research to figure out how to change it - hence "fiddling around". i can now go to the router at 192.168.1.1 and review my configuration.  it shows 29 devices at locations i expect. it also shows the device name for all the windows 10 devices next to the IP address. most are now assigned by DHCP but the router clearly sees the name of the device for each device regardless of whether it's an assigned static ip or a allocated DHCP.. Now when i try remote desktop, it will connect to 1 device provided i give it the IP address not the name (unlike previously when each device i wanted to connect to was accessible through either the IP address or its name.) no other device connects using remote desktop, regardless of whether i use the device name or the IP address. i would be tempted to say that it's related to the redirect of the DHCP reserved addresses but the one that works is at 192.168.1.134..All devices function normally except for the remote desktop connection. all devices have been rebooted several times and their configuration checked for remote desktop access.