Windows 10: Windows Remote Assistance generating with IP address I need it to with a host name

Hello, I have a situation where when using remote assistance I need the "*.msrcIncident" file to be generated with the hostname that needs assistance and not the IP address. Is this possible via GPO or another option? It is creating a very serious issue in our environment.

:)

 

Unable to remote into PC using host/PC name, but can using dynamic IP

Hello Everyone,

I've been spending some time trying to figure this out and can't seem to find the problem that's affecting me. Here's what I've tried so far.

• Changing PC name to something with only lower cases
• Looked at "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent\OldName" in registry to see if I can connect using the old PC name
• Ensured network adapter is set to find addresses automatically. DNS is set to find address automatically etc.
• Looked at host file, but didn't make any edits. I figured this is for static IPs, not for someone with a dynamic IP with a 24 hour lease

I'm able to remote into my PC using the IP address, but the problem is, I'm running a dynamic IP set up for my home PC and I don't want to run a static IP. The reason why I want to remote into my PC on my home network is because I have a PC and a Macbook Pro. My Mac is for light work and menial tasks; school work, reports, documents and such, portability stuff, etc. and my PC is for gaming heavy tasks, video rendering, etc. I'm also beginning to study for my MCSA and will be running Server 2016, and SQL2016 on a VM on my gaming PC or partition it out so it's a full time server. Or just buy a dedicated server of some sort. I don't know yet.

I can easily use a third party solution, such as TeamViewer, or Chrome Remote Desktop, but I don't like the fact it keeps things running on my screen at the same time. Meaning, I like it when my home PC is not showing what I'm doing remotely.

When I use ipconfig /all in command prompt it says "connection-specific DNS suffix" is blank. I don't know if that's the problem or not.

Any assistance would be great.

 

Remote Desktop vs. Internet Remote Desktop (Internet and LAN)

Remote Desktop works in exactly the same way over the Internet as over an internal network. However, when working over the Internet, you must take some extra steps in order to establish a connection:

• The client must know the host's external IP address.
• You must create a tunnel for port 3389 on the host's router.
• The host must have a fixed internal IP address.
• The host's router must direct port 3389 packets to the host's internal IP address.
• The hosts's firewall must allow port 3389 packets.

BTW, "Host" is the machine that is being taken over, often a PC at the work place.

"Client" is your own machine, often the PC at your home.

 

Windows 7 Home Premium Remote Administration

Setting up an RDP connection is not exactly trivial. In broad terms, here is what you need:

• Either a static external IP address for the RDP host, or a domain name that resolves to the current dynamic address.
• A tunnel through the router at the RDP host site.
• A fixed internal IP address for the RDP host.
• Remote Desktop must be enabled on the RDP host.
• The RDP host's firewall must accept incoming RDP packets.

If you lack the experience then you need to ask a computer-savvy friend to help you, either in person at the remote end or by granting him remote access to the RDP host.