This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I'm trying to setup Remote Desktop capabilities for the Plant Manager so when he's on the road, he can access the server. For the life of me, I can't get any access to my server from outside our network no matter what client I'm using or where.
I've disabled all rules for incoming traffic on the router, but still can't ping it. I'm thinking if I can't ping it, then why would I be able to connect to it.... I could be wrong in my thinking.
Anyway, I can ping the Cable Modem [Charter Comm] static IP that it has, but not the router that is hung off of it.
Can anyone shed some light as to what setting I should look over within the routers config?
TIA
Of course, I could always consider a 3rd party solution like Logmein, Go to my pc, etc....
I found the problem. It was the actual Firewall on the server. Took me a while to figure out if it was the DOMAIN, PUBLIC, or PRIVATE firewall setttings.
One other note. I took a PC and hung it off the Cable Modem from Charter, assigned it a static IP from a 5 pack that we have. I drove to our sister plant, pulled up Remote Desktop, and put that IP addy in. I connected and logged into the PC. So now I know it's a setting somehwere within the router, but not sure where to look.
Kindly try to configure an Inbound rule on the FVS336Gv3 to open port 3389 (RDP port) pointing to the LAN IP address of the server. Afterwards, double-check if port 3389 is really opened on the FVS336Gv3 by using an online port scanner here.
Kindly read pages 231-233 of the FVS336Gv3 reference manual here about adding an IPv4 LAN WAN Inbound Rule.
I found the problem. It was the actual Firewall on the server. Took me a while to figure out if it was the DOMAIN, PUBLIC, or PRIVATE firewall setttings.
Thanks for the update. I glad to know that you figured out what the problem is. I believe you are now able to remotely access the server. 🙂
If ever your concern has been resolved, I encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The NETGEAR Community looks forward to hearing from you and being a helpful resource in the future!
