Well a bit more reading on my part indicates that vpn on Windows 10 professional is only a client, not a server so does not let me hook to a Windows 10 Professional workstation. There appears to be a work around I think its adding a point to point protocol
https://www.howtogeek.com/135996/how-to-create-a-vpn-server-on-your-windows-computer-without-installing-any-software/
Yup - it's a desktop not a server, so unlikely to be able to run as a VPN server by default
PPTP is as old as the hills, and totally cracked years ago. Yes SME has it, but I could never, ever recommend it. Don't touch with a barge pole. Anyone giving you that advice needs taking round the back of the shed and shooting. OpenVPN/Ipsec are far superior.
but I assume thats why you went with what you did? However I am just wanting to be able to remote in like one would with Teamviewer. Are you using your method from a portable or are you restricted to permanent location for what would be the client.
From experience. Note I have no Windows AT ALL, but that is besides the point. You want to be able to connect to a desktop behind a router.
Answer.
1. Use SME in server/gateway and add VPN server software.
2. Use a VPN to the router.
You can set up individual certificates and connect from anywhere with any device, assuming you aren't in a hotel that port blocks VPNs or you have a device that can't do VPN....
I'm not to sure why suicidal, I assume "remote login with network authentication" is encrypted which would restrict it to password strength like ssh?
Because it is a really sought after port to by hackers. If they get access then they have control of your workstation, and your network. If the port is exposed they'll hammer it day and night with dictionary attacks (and you'll then be asking how to stop them). You have no other protection.
Besides, if Windows has a bug to which allows them access, they'll know well before you.
Thoughts?
Assuming you aren't going to put SME in server/gateway, use your router as a VPN server if it is possible, or bin it and get a decent one that can (you still haven't mentioned what you have got)
Use proper certificates and not passwords. Way more secure.
Don't make life easy for the bad boys.
Note - I have a number of small networks linked permanently by ipsec using certificates. If I am on the local networks, I can remote desktop to anywhere on the linked local networks. They have static IPs at the VPN endpoints, so you can't just get in from anywhere , just the allowed IPs.
I also have a couple of places that I use OpenVPN so I can access from varying clients, again using certificates.
None of it is rocket science (though certs are a bit of pain when you start, and I'm still no guru on them !) but it is pretty secure.