I am having some difficulties using RDP on the LAN of the router. I previously had a Linksys E4200 router, and I was able to RDP from my Win7 computer (192.168.1.139) to my Win2k3 server on the LAN (192.168.1.251) with no issues. However, when I replace the E4200 with the WRVS4400N, the connection will only work for a few seconds before giving me the following error:
I am unsure why the new router would be causing this issue. It is not exclusive to RDP connections on the LAN either... I get a similar error when attempting to connect to computers off site. I could see MTU's being an issue if it was over a VPN connection, but there is no VPN involved in this case.
Same problem... cannot do standard RDP to windows clients inside the firewall once a VPN connection is established to the server. Can resolve names via DNS pinging both names and IP addresses fine, can browse internal network, can open server shares by name, no issues there.
Now, I have been using routers of all types and levels for over 20 years with standard VPN port forwarding and windows VPN server connections, small ones, big ones, 5 users, or even 5000 users... and NEVR seen this problem before.
Your tech note that says to "Turn-on Remote Management" on the router is totally dangerous, scary, and irresponsible - NO WAY... any router that requires this to be on just to pass VPN traffic is total garbage folks. Besides, even with this on, and following every ridiculous tech note you have sent me in 12 months, NOTHING MAKES IT WORK.
The perfomance of this router is wonderful as far as speed goes, both on wireless wired segments, but the firewall protocols are garbage compared to the cheapest Linksys routers of the previous generation devices.
And, as if there were any questions as to the idiotic design of this unit, the fact that your manual states that "Remote Managemnt" must be "ON" for the router to even function with VPN is direct evidence of this badly flawed software design.
One may as well advertize to have their system broken into... sheesh - get a clue Cisco. I and the rest of humanity expects more from you. I'll never buy another Cisco product after this, and your lame support of this product.
*** YOU DO NOT NEED TO REPLY, YOU HAVE SAID NOTHING HELPFUL IN 12 MONTHS - I AM TELLING YOU THIS, NOT ASKING YOU. ***
Hi every one!!!When you are configuring a remote VPN connection, there
are some steps that are lost on the path. Here you can see those steps.
A) In your Cisco device: 1. Ensure you don´t have any rule denying the
traffic between the device and the remote...
** Update **These and a number of other issues have been addressed in
SRP520 MR3. Please see https://supportforums.cisco.com/docs/DOC-13853
for details on how to access this code.There have been a number of
reports of the SRP500 becoming unresponsive afte...
STANDARDSOURCECOMMENTSEthernet RJ-45 connector pin number12345678IEEE
802.3afusing data pairsRXDC+RXDC+TXDC-sparespareTXDC-sparespareIndustry
Standard for Embedded POE(used by Cisco Catalyst Switches)IEEE
802.3afusing spare pairs RXRXTXDC+DC+TXDC-DC-Indus...