Port Forwarding On Linksys RV016
Port forwarding was working on this Linksys RV016. The previous sys admin set it up so I could access the IT workstation using the routers public IP address and an assigned port, using RDP.
It looks like this on the router, "setup", "Port Range Forwarding":
IT-RDP[TCP/4200~4200]->192.168.100.46
It worked fine, I could access it from anywhere on the Internet. The IT workstation died, so I put another workstation on that IP address (192.168.100.46), but it does not work.
I can RDP from the LAN, but not from the Internet.
Any ideas?
Computers & Internet - Linksys - RV016 Router
Answers & Comments
My first thoughts were whether the old PC had XPSP3 or not and if the new PC is different than the old one with respect to XPSP3.
Secondly, this too could affect the profile in your router. The station ID. That is the computer name in addition to the ip address behind the router.
When you want to add a new PC as a replacement station on the network, not only does the IP address need to match , but the computer name needs to match as well.
I'd check those two things, most importantly the XPSP3 which had raked havoc on systems.
Regards,
Worldvet
Make sure that the new workstation can access the internet and its also setup with the correct static IP and DNS which is the one setup to use the the RDP port that was forwardde on the router. because if you just change the workstation and its not set with the same settings like the old one it wont be working...
Hope that helps..........
Hi sir.. u will get more details about this.. forums.linksys.com/linksys/board/message?board.id=Wired_Routers&thread.id=18777 thank u sir. have a nice day..
Common misconceptions:
1. The remote computer MUST be able to install the Active-X Remote Desktop Client that is provided by the Remote Desktop Web Connection (AKA TSWEB).
2. It does not work like GoToMyPc, which works over standard SSL. Remote Desktop works over port 3389 (by default)
3. The purpose of TSWEB is to provide both an Active-X Remote Desktop Client and the proper configuration information to connect to a Terminal Server or Remote Desktop Host.
4. The IIS Server hosting TSWeb does NOT connect to or contact the Terminal Server in any way, shape or form. It's only job is to provide the Active-X Remote Desktop Client and the proper configuration information. The TSWEB can be on the public Internet, DMZ or private network, i.e. makes no difference where it's located.
So to recap:
Remote client connects to the IIS Server -> IIS Server provides Active-X Remote Desktop Client and the proper configuration information to the client computer (if the client isn't already installed) -> Client uses the connection information in the TSWEB to connect to the defined Terminal Server or Remote Desktop Host over port 3389, or whatever port is defined in the TSWEB Configuration.
If the firewall is configured properly, one should be able to connect to the Terminal Server with the built-in Remote Desktop Client. If this doesn't work, neither will the Active-X Remote Desktop Client provided by the TSWEB.
Using an SSL Connection for the TSWEB is pointless, as it offers no added security.
http://www.sessioncomputing.com/security.htm
http://www.sessioncomputing.com/how-to.htm
Would need to mach the settings on the server to the old server, something must be a little off. Services on the right ports? Forwarded the right ports?
Think you need to double check everything that they are set correctly, new server firewall blocking?
-check ip
-check ports
-check firewall
the issue is clearly between the server and the router / firewall. I suppose you could even try DMZ if the workstation has protection.
No change needed on the RV016 - same IP & Port
Check settings on the NEW Workstation (Remote Access grants / Ports assignment)
And your Computer as it is still looking for the old workstation (RDP is more on the computer's identity not the IP address).
I think it would be wie to check that the server is set to allow access from the internet. many routers now have a built in firewall to ensure hack attempts cannot access. I think it may be that its set to allow RDP connections from lan but not from the internet.
It's a rather lenghty explanation so please go to this site and follow the instructions...
http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/
Robert
Please rate this solution ... thanks