Disable UPnP (I know, kinda defeating the purpose here) and try making your port forwarding rules again, as UPnP can over-ride your own rules. If Windows Home Server requires Port 80, for exmaple to be open, make sure the rule matches TCP Any --> 80 to the host you're forwarding port 80 to. Do the same for the other ports. The router might have a built-in RDP rule, and assuming the port is set to 3389, that built-in rule should do the trick.
Also, I suggest using DHCP Reservations or Static IPs on your network when dealing with port forwarding. This way, the router doesn't have to re-write the rules based on computer name (which doesn't always work right) or should the computer get a different IP, break your rules.
Lastly, make sure the router's Firewall isn't set too high. Anything higher than Low will start to deny port forwarding traffic. Try the router with "No Security" letting NAT act as the firewall instead. That tends to be the most compatible options when hosting servers.
Also, http://canyouseeme.org/ comes in handy. Use this tool once you have the port forwarding rules created, and a server application (for example, the Microsoft Remote Desktop service) running on the ports on the host you're trying to connect to. This tool will tell you if it is able to see something running on the ports you've forwarded, or if things failed.
"Connection Timed Out" usually means a Firewall or NAT has blocked the connection, OR your port forwarding rule is incorrect.
"Connection closed" or another error which returns back almost immediately typically means the port forwarding appears to be working, but there's no server application listening to a port. This could also mean the port forwarding rules are incorrect, if the request was sent to another connected device on your network.
"Success/Open" means your port forwarding should be working properly.