Member Avatar for patrick12

First, let me tell you about my network. My computer connects wirelessly to my Linksys WRV200 router which is connected to my Vonage RTP300 which in turn is connected to my Comcast cable modem. So...


Internet -> Vonage RTP300 -> Linksys WRV200 -> Computer

I am unable to connect to my office over my VPN , I hope someone can help me with this issue.

Thanks

  • 5 Contributors
  • 6 Replies
  • 230 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by steosaur(oWn)

Dani AI

Generated

Your topology (Internet → Vonage RTP300 → Linksys WRV200 → PC, from ) makes this a classic NAT/traversal problem rather than a simple client configuration error. and were right to check client settings and account access, but the missing piece most replies haven’t explained is how specific VPN protocols interact badly with a consumer VoIP gateway sitting in front of another router.

Step-by-step checks to run (identify protocol first — PPTP, L2TP/IPsec, or SSL — and get the VPN server IP from your workplace, as suggested). Use basic connectivity tests and a packet capture to see what’s being blocked:

# Windows
ping <vpn-server-ip>
tracert <vpn-server-ip>
telnet <vpn-server-ip> 1723   # tests PPTP TCP 1723 (telnet may not be installed)

# Unix/mac
ping <vpn-server-ip>
traceroute -n <vpn-server-ip>
nc -vz <vpn-server-ip> 1723   # netcat for port checks

Wireshark display filter examples:

udp.port == 500 || udp.port == 4500 || ip.proto == 47 || ip.proto == 50

What to change if tests show the router chain is the blocker: enable VPN passthrough on both boxes, place the Linksys WAN in the Vonage DMZ (or set the Vonage to passthrough/bridge so the Linksys receives the public IP), or forward the needed ports for your VPN type. Note: PPTP requires GRE (IP proto 47) plus TCP/1723 — GRE can’t be NAT-forwarded reliably, so passthrough/DMZ/bridge is usually required. Update router firmware; some versions drop ESP/GRE packets. ’s re-ordering idea is conceptually correct for removing double-NAT, and ’s power-cycle tip is useful — reboot in order: modem → Vonage → Linksys → PC.

If a direct connection to the cable modem lets the VPN connect, the solution is router-side (passthrough/DMZ/bridge or single NAT). If it still fails, the workplace VPN settings or ISP/Vonage firewall are likely responsible and their logs/support will be needed.

Recommended Answers

All 6 Replies

Member Avatar for TheNNS

be specific, why aren't you connecting? what errors are you getting? have you tried even configuring a connection? have you checked proxy settings?

Member Avatar for Serunson

have u actually set up a connection with ur work?
Problems may lie in ur connection to the work servers.

Member Avatar for TheNNS

true, your work might not even have vpn, or you maybe they need to give you an account.

Member Avatar for Serunson

At college, we have a VPN system, which we have to sign up for through their website, ask ur work if they have a VPN connection set up.

Member Avatar for Spriggan

aside from VPN settings, i would connect your vonage router behind your linksys. It may be that your vonage doesn't support IPsec or whatever VPN protocols you're using.

modem--->linksys----->vonage
&
linksys----->Computer

Member Avatar for steosaur(oWn)

don't forget to power cycle. I dunno how Vonage works, but I would plug the router in first let it boot up and then turn on your comp and vonage.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.