You shouldn't be posting info
Anyway, the message Windows plays at the end is pretty self-explanatory. That is, the tunnel failed because it couldn't negotiate a security tunnel. Possible issues might be:
* L2TP needs a pre-shared key you were supposed to know. If you didn't set it, it will fail. If you never had it before, then you're probably not on L2TP, however, it's possible such details are lost.
In the security tab, I have:
Type: L2TP (I have that). I have an additional settings button that allows me to tell it not to attempt certificate but a pre-shared key.
Data encryption: Optional (connect even if unsecured). That should probably be on.
Allow these protocols is check and all 3 are allowed, including PAP (unsecured).
Then there's the networking tab where I have MS Client, MS Server and IPv4 (v6 is unbound)
Your issue seems to be that none of the protocols were OK, meaning that
* it's either L2TP and you don't have the pre-shared key (you need to get it)
* it's PPTP (not pppoe!), and most likely it's a firewall or route (it uses additional ports, I think it's 1723 TCP) that blocks it (thus the negotiation)
* it's SSTP (Secure Sockets) and it's also most likely a firewall. It uses port 445 and most firewalls hide that port out of ... well I don't know, they just like that.
If you are 100% sure that you weren't supposed to know a pre-shared key (it's a string password), then it's not L2TP. In which case, my money would be on a firewall interference.
I decided to give it a go.
Internet hinted that that VPN type is PPTP, so I set it at that.
Note that moving it from outo jumped encryption to "required", which is bad.
I moved it to optional and allowed PAP ans MSCHAP (both unencrypted). After the warning, some IP modifications to now allow the remote gateway access (that will dump all my current connections). And there we go, I'm online, I have 192.168.0.1.