PTCL - D-Link VDSL Router doesn't support Cisco VPN Client

[Ratt]

Hello
Please help me out with my VPN connection client.
My company IT installed the official VPN client on my laptop to access the company network from home.
Since my router was upgraded to VDSL it isn't allowing the VPN client to connect.

VPN Client software: Cisco VPN Client version 5.0.07.0290
Connection: PTCL 20 MBPS
Router: D-Link DSL-225

When asked, my IT replied the new PTCL routers do not support the client.
Is that true?
Can anyone help me out?

 

[aura]

type following command in cmd
>ping 8.8.4.4 -l 1400 -f 1492
if you get "Packet needs to be fragmented but DF set."
lower the value after f parameter in increments to like 1470, 1464, 1460 until you get reply
e.g.ping 8.8.4.4 -l 1400 -f 1460


type following command
netsh int ipv4 sh int
e.g. on my pc
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
3 20 1500 connected Local Area Connection
1 50 4294967295 connected Loopback Pseudo-Interface 1
6 10 1500 connected VirtualBox Host-Only Network

note index (idx) number (3 in my case for local area connection)

run following command in cmd with admin rights ( cmd, right click> run as administrator)
netsh int ipv4 set subint "3" mtu=xyz store=active [3 is the index number of interface, should be different on your laptop)
where xyz is value for which you got reply from ping 8.8.4.4 -l 1400 -f 1460 command (1460 in this case)

if you can connect then you need to change last command's store parameter from active to "persistent" so rebooting doesn't reset to default.
P.S. if you do not have any browsing , check dns is working or not the report here

 

[Ratt]

Hi Aura
Thanks for the reply.
Got the below when I tried what you told me.
What to do now?



C:\>ping 8.8.4.4 -l 1400 -f1492

Pinging 8.8.4.4 with 1400 bytes of data:
Request timed out.
Reply from 8.8.4.4: bytes=1400 time=143ms TTL=52
Reply from 8.8.4.4: bytes=1400 time=365ms TTL=52
Reply from 8.8.4.4: bytes=1400 time=86ms TTL=52


Ping statistics for 8.8.4.4:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 365ms, Average = 198ms


C:\>netsh int ipv4 sh int


Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 50 4294967295 connected Loopback Pseudo-Interface 1
26 5 1500 disconnected Ethernet
16 25 1500 connected Wi-Fi
33 50 1500 disconnected Ethernet 2
32 20 1500 disconnected Ethernet 3

 

[aura]

Hi Aura
Thanks for the reply.
Got the below when I tried what you told me.
What to do now?



C:\>ping 8.8.4.4 -l 1400 -f1492

Pinging 8.8.4.4 with 1400 bytes of data:
Request timed out.
Reply from 8.8.4.4: bytes=1400 time=143ms TTL=52
Reply from 8.8.4.4: bytes=1400 time=365ms TTL=52
Reply from 8.8.4.4: bytes=1400 time=86ms TTL=52


Ping statistics for 8.8.4.4:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 365ms, Average = 198ms


C:\>netsh int ipv4 sh int


Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 50 4294967295 connected Loopback Pseudo-Interface 1
26 5 1500 disconnected Ethernet
16 25 1500 connected Wi-Fi
33 50 1500 disconnected Ethernet 2
32 20 1500 disconnected Ethernet 3

netsh int ipv4 set subint "16" mtu=1460 store=active
or

netsh int ipv4 set subint "16" mtu=1400 store=active
though i doubt you'll need mtu of 1400

if it works use store=persistent for permanent change

P.S. i made error in commands i posted it should be "ping 8.8.4.4 -l 1460 -f" you change value of length until you get reply.

 

[Lord Ammar]

Unless the VPN client is to be installed on the router, I don't see what the router has to do with this.