If the problem isn't with your router's PPPoE configuration, then work with your company's VPN support staff to...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
monitor traffic from your VPN client to isolate the problem. For example, incoming IKE but not IPsec can be an indication that your provider blocks protocol (not port) 50. Incoming-but-errored IPsec packets can indicate a fragmentation or NAT problem. Returned IPsec packets that never reach your VPN client can indicate a NAT-ing device that does not supporting VPN pass-through. Comparing traffic logs at both ends (VPN server and VPN client) and traffic counters on your router can help you spot the device or "hop" where packet drops occur.
Related Q&A from Lisa Phifer
The enterprise mobility management market for wearable devices is in its infancy, but IT can still use existing EMM tools to manage wearables.continue reading
Wireless expert Lisa A. Phifer explains to what extent WEP cracking remains a worrisome issue. It all depends on your company's WLAN security policy.continue reading
Wireless expert Lisa A. Phifer explains why you shouldn't stop using 802.1X authentication methods for enterprise WLAN access control.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.