I am trying to use Remote Desktop on my computer, as a host. Whenever I try to connect via the IP address I get an error "Remote desktop can't connect to the remote computer for one of these reasons:" and then it gives the following reasons "Remote access to the server is not enabled; the remote computer is turned off; the remote computer is not available on the network." I can connect just fine when I use the name of the computer, but it will not work when I use the IP address. I tried accessing my router and adding in Remote Desktop on a certain port, 3389. This has not helped. I have been told that the problem probably lies in my firewall settings, but I cannot get it working still. I have Norton Security Suite. I went into the firewall settings and under the Traffic Rules tab I added an exception. I set it as allowing the connection to go in and out, to use TCP, I added the port 3389 as both local and remote, and told it to create a history log. I also tried it as TCP & UDP. Any advice/suggestions?
You say it connects fine when you use the "computer name".
You must be connecting from inside your home network. If thats the case you need to use the internal IP address of the computer, not the internet address.
When I am on the same network, then the computer name works fine and the Public IP Address fails. When I am on a different network the IP fails and obviously I can't use the computer name. The goal is to use Remote Desktop from another network so I am trying to figure out what is blocking it.
You can't test the internet connection from inside your network because there is no way to have your connection go "out" your router and do a U turn to come back in.
The easiest way is to get someone to help you, someone outside the network with a computer and a telephone.
I'm personally not very familiar with remote desktop because I need to be able to also transfer files but I assume the setup is the same as with all other remote administrator tools.
I always thought remote desktop used UDP but I see some articles say TCP. If you want to play it safe start with both but I'm still pretty sure that windows terminal services uses UDP.
The server should have a fixed IP address so the internal (LAN) IP never changes.
Your router should be configured to forward port 3389 to the server system in both protocols.
The firewall rule you made on the server system should be both protocols.
Move that rule to the top of the list (to give it priority over any existing rule that could block it).
Right click on the norton icon next to the clock and "disable smart firewall", choose 15 minutes.
Have your assistant try to connect, if you cannot connect at this point it is a configuration problem
If you connected, re-enable the firewall and try again. If it doesn't connect at this point, look in the history under firewall to see if it got blocked for some reason.
If your able to connect, reboot the server system and make sure it still works and you should be fine.