Cisco VPN acccess via a DLINK DI-614+ router

[turtle16]

Hi,

I connect to my work network via Cisco VPN Client v4.8, My home network runs on a DI-614+ wireless router with a seperate ethernet modem connected to the router.

The problem that I have is that when i am connected to the router directly using a network cable then i can vpn in no problem, however when i connect over wireless the vpn client fails to connect.

I have checked the protocols on the network connections and they are the same with the exception that the wireless has an additional transport protocol.

Does anyone have any idea how i vpn in over wireless?

thanks

 

[John Lewis]

There is nothing special about wireless that should prevent a connection. Any time you are behind a NAT router (such as your D-Link), special steps may be required to allow the connection to be maintained. The particulars will vary from router to router (especially different manufacturers).

From D-Link Knowledge Base (their KB is in html frames, so it is not possible to link to it):

Cisco VPN
Upgrade your router to the latest firmware. You can download firmware at

http://support.dlink.com/downloads.

Disable all Firewall Software (ZoneAlarm, Windows XP Firewall, etc.).

Configuring PC running VPN Client Software:

Step 1 Disable all Firewall Software (ZoneAlarm, Windows XP Firewall, etc.).

Step 2 Change IP Address to be outside of the routers DHCP Pool (i.e. 192.168.0.99). By default the DHCP pool is 192.168.0.100 - 192.168.0.199.

Step 3 Configure Cisco VPN Client - Connection Properties.

Step 4 Check Enable Transparent Tunneling.

Step 5 Allow IPSec over UDP ( NAT/PAT).

Configuring Router using the Web-based configuration:

Step 1 Open the Web Configuration Page by entering 192.168.0.1 into your web browser. Enter username (admin) and your password (blank by default).

Step 2 Check the Status tab and make sure that firmware is at least v2.03g. If not, upgrade firmware before proceeding.

Step 3 Click on the Miscellaneous button on the Tools tab. Enable both PPTP and IPSec.

Step 4 Click Apply.

Step 5 Click on the Virtual Servers button on the Advanced tab.

Step 6 Enable IPSec from the list and configure as follows:

Private IP: IP Address of the PC running Cisco VPN Client
Protocol: UDP
Private Port: 500
Public Port: 500
Schedule: Always.

Step 7 Click Apply and then Continue.

Step 8 Enable PPTP from the list and configure as follows:

Private IP: IP Address of the PC running Cisco VPN Client
Protocol: TCP
Private Port: 1723
Public Port: 1723
Schedule: Always.

Step 9 Click Apply and then Continue.

 

[turtle16]

Thanks for your response with this however i still cannot connect over wireless. If i connect my laptop directly to the router via an ethernet cable then the vpn is fine however if i connect over wireless the vpn will not establish. I have tried the vpn through a different wireless router and it connected ok so it does seem to be specific to my router, any one got any ideas?

 

[mtbrain200]

I have the same problem with a Dlink DI-624S that has the same issue. I have been on the phone 5 different times with thier tech support and even spoke with thier "senior" tech support which transfered me back to thier initial support number. I'm really getting frustrated with D-Link.

 

[mladd]

Not sure if this was ever resolved but same problem here.

What I notice is that the Cisco VPN client does connect, but I am not able to connect to my E-mail server, telnet to a box, or even connect to a network drive. It seems that I am not getting an IP (I'll verify this tonight).

When I plug in directly to the router it all works fine. My VPN worked fine using Windows XP VPN, until they switched to the Cisco client recently.

I saw the posts earlier, and I may have to try a few different things listed earlier, to see if that helps. I'll let you know if any of them work.

-Mike

 

[mtbrain200]

I still have the issue and D-Link tech support has been working on it since the end of November. If you look at their support page it tells you that you need to upgrade the firmware to a newer version, yet there is not a newer version of the firmware only the shipping version.

I finally received a reply from their Product Specialist that states: "we tested this device,and we were unsuccessful in opening ports 1723 TCP or 500 UDP,I reported this to our group lead,who will foward this to Product Management."

Good luck Mike! If you do find something, please share it with the rest of us.

Ritchie