<div>
I have access rules in place to allow any wan to lan access as well as allow and lan to wan access. &nbsp;If I understand things correctly, this pretty much disables the firewall. &nbsp;I have also created a custom service for RDP port 3389. &nbsp;This is forwarded to the server. &nbsp;Yet when I look at &quot;Open Ports&quot; I do not see port 3389. &nbsp;When I enable &quot;Respond to ping from WAN&quot; I am still unable to ping the public IP of the router or any IP on the subnet behind the router.
</div>


I have access rules in place to allow any wan to lan access as well as allow and lan to wan access.  If I understand things correctly, this pretty much disables the firewall.  I have also created a custom service for RDP port 3389.  This is forwarded to the server.  Yet when I look at "Open Ports" I do not see port 3389.  When I enable "Respond to ping from WAN" I am still unable to ping the public IP of the router or any IP on the subnet behind the router.

<div>
<div class="content wysiwyg-content">
I have two new Cisco RV180 VPN Routers setup. &nbsp;I have successfully establish a gateway VPN between the two, but cannot access the network via remote desktop. &nbsp;Workstations are XP SP3, network is Server 2003 based. &nbsp;I also cannot ping the network via IP or station name.<br />
<br />
What have I missed on the router setup?
</div>
</div>


I have two new Cisco RV180 VPN Routers setup.  I have successfully establish a gateway VPN between the two, but cannot access the network via remote desktop.  Workstations are XP SP3, network is Server 2003 based.  I also cannot ping the network via IP or station name.

What have I missed on the router setup?

Remote Desktop Through Cisco RV180 VPN Tunnel

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

Internet Protocol Security (IPsec) is a protocol suite for secure Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a communication session. IPsec includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session. IPsec can be used in protecting data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-network), or between a security gateway and a host (network-to-host). IPsec is an end-to-end security scheme operating in the Internet Layer of the Internet Protocol Suite.

Internet Protocol Security

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.