So you said it started working once you restarted your laptop? Did you reboot before? I am asking since I wonder if your registry settings were only applied after the reboot? And yes VPN should be your choice, definitely. Sorry I am curious, just another question. How would I accomplish what you said so that only those specific IP addresses can access my desktop? If I recall correctly from the few networking classes i've had I could also add a scope to the current firewall settings I have and just block out all IP addresses on port 3456 except the ones I need to connect from, but I am not sure if this is the best way to do this.
#MICROSOFT REMOTE DESKTOP ERROR CODE 0X104 PC#
Yeah I indeed only need to connect to my PC from some specific locations like work, my gf's house. If on the other hand you need to be able to remote in from various random locations, such as coffee shops, restaurants, hotels, etc, a VPN is definitely the better approach. If you are planning to connect to your home computer from a few specific locations, such as your office or a relative's house, then you will probably be fine just using your router's firewall rules to limit access to those specific IP addresses. It will only block the simplest automatic scans, so instead of being attacked every 10 seconds, you may only be attacked every ten minutes. Volume of invalid login attempts that show up in your logs, but it's not Using an alternate port for RDP is an effective way to reduce the A lot of people at my workplace and the place I study at use RDP over the internet without a problem. I don't think it's such a bad idea as long as I take correct precautions, like having a different port to the default one, restrict user accounts, accounts lockout policy. I have added my user to the users through system properties. I have Network Level Authentication enabled as an RDP requirement on the desktop. I made a inbound rule for both TCP/UDP on 3456 Port Forwarding is setup for TCP/UDP on 3456 for 192.168.178.21 Have you given yourself access through system properties?īTW, have I mentioned that opening up RDP to the Internet isn't a great idea anyway? If your dekstop's firewall is active, check that for udp/tcp, tooĭo you have Network Level Authentication enabled as an RDP requirement on the Desktop? Please check to see if port forwarding on the router for 3456 is set up for TCP, UDP or both. Text C:\Users\me>netstat -a | find ":3389" Once I am home in two hours I will confirm again if it does work from within my network. It's DESKTOP-JN4LCD5 (Never bothered to set up a name, I should though), My lan address is indeed 192.168.178.21.
So, are you testing from within your network so we can eliminate the router? If it is as above then the netstat result shows that the laptop has at least started communicating with the desktop.
If your desktop's name is media-match and its LAN address isĪnd you have been trying to connect to it from
And sorry for the confusion, the netstat output was on my desktop. I altered the following register key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber I don't have to option to do port translation on my router sadly. I am indeed trying to access my desktop from *OUTSIDE* of my home network. Please confirm which registry key you altered.Īnd, of course, please confirm that you are trying to connect to your desktop computer using the RDP client and entering the address DesktopNameOrIP:3456īTW, it is not clear to me if the netstat output you have shown is at the Desktop or the Laptop. If you don't have that option either, then changing the registry is your only option.
Again, no configuration changes would be necessary at the desktop. If you don't want to set up a VPN server, you might be able to achieve what you want very simply, depending on what make and model of router you have, You might be able to do port translation in conjunction with port forwarding so that the router is listening on 3389 and forwarding those requests to that other desktop while, at the same time, listening on 3456 and forwarding those requests to your desktop, still on 3389. That way you could connect to the VPN and then connect to the Desktop with no configuration changes at the desktop being necessary. If external access is required, I would strongly recommend setting up a VPN server on your network (possibly on the router) so that you can securely connect to the network and NOT expose RDP ports to the Internet. If not, and you're trying to access your desktop computer from *within* your network via RDP, there is no need to change the port. Just to be clear, you are trying to access your Desktop computer from *outside* your network via RDP using your laptop.
0 kommentar(er)
