Originally Posted by Dutch Master
First, try to establish if there's a physical connection at all. Find out what the IP address of your office machine is, then issue the ping command:
ping -c 5 <insert IP address>
If this returns errors, your physical connection is broken. If the command comes back with a successful ping, the problem is in the configuration of the client. Make sure the client allows enough time to establish a connection, 300 seconds (that's 5 minutes) is the upper limit you can take it to.
Hi Dutch Master
and thanks for replying. I checked by issuing ping an there is reply. Also, I noticed that immediately after trying to log in to the VPN my Debian system gets added the VPN's default route.
I am going to search for information in how to increase the time to establish the connection as you had suggested.
In others things (but a little bit related to the above paragraph), I ran a test to the VPN I want to log in by using Wind0ws. I noticed it delays to get connected to the VPN service. So, increasing the time to establish the connection in Debian might be a good starting point.
Finally, I want to share some findings I gathered when trying to log in to the VPN. Here they goes:
root@thunderbox:/home/thor# tail -f /var/log/messages
Oct 8 08:21:42 thunderbox pppd: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded.
Oct 8 08:21:42 thunderbox kernel: [ 244.066976] PPP generic driver version 2.4.2
Oct 8 08:21:42 thunderbox pppd: pppd 2.4.5 started by root, uid 0
Oct 8 08:21:42 thunderbox pppd: Using interface ppp0
Oct 8 08:21:42 thunderbox pppd: Connect: ppp0 <--> /dev/pts/2
Oct 8 08:21:45 thunderbox pppd: Connection terminated.
Oct 8 08:21:45 thunderbox pppd: Exit.
root@thunderbox:/home/thor# tail -f /var/log/debug
Oct 8 08:21:42 thunderbox modem-manager: (net/ppp0): could not get port's parent device
I think it is specially important this part: modem-manager: (net/ppp0): could not get port's parent device
. This looks strange for me. However, I'd noticed this message appears when I open Virtual Box, look at this:
Oct 8 08:48:38 thunderbox modem-manager: (net/vboxnet0): could not get port's parent device
I don't want to deviate what I am looking to be solved, but I think the output above might be useful, too.
How to regain access to my VPN? Please suggest.