BBOX and VPN Server
Ptit-Fils
Posted messages
12
Status
Member
-
Ptit-Fils Posted messages 12 Status Member -
Ptit-Fils Posted messages 12 Status Member -
Hello,
I'm reaching out to you because I have a problem ...
I have a Bouygues Telecom BBox at home and behind it a Windows VPN server.
Server configuration:
IP: 192.168.1.222/24 (fixed)
IP on a second private network: 192.168.2.10
My Box configuration:
TCP port forwarding 1723 to --> 192.168.1.22 (which is my VPN server).
I'm testing a first connection locally:
- From a client on my LAN (192.168.1.36)
- I connect to the VPN server (192.168.1.222)
- the connection is successful.
I move on to something more difficult:
- From a client on my LAN (192.168.1.36)
- I connect through my box to the VPN server (port forwarded) (theoanne.ddns.net --> 88.... doesn't matter, the resolution is done
- The VPN responds and the connection works through my box using its public address from my home.
Final check:
- From a client outside my LAN (@private 172.16.0.1) (@public: 89.... etc)
- I attempt a connection through my box (theoanne.ddns.net)
- No response from the VPN server.
I tried instead of just leaving the port open to put it in DMZ, nothing works, I even completely disabled the firewall and all other services on the box, I cannot access my VPN which responds correctly.
Does anyone have an idea?
By analyzing the TCP segments:
- When my box does not have the port open:
> Direct response of a RST flag
- When my box has the port open:
> Establishment of a TCP connection (between the box and the remote PC)
> No way to know if the establishment is made with the VPN server or the box itself
> No response upon launching the VPN connection after the TCP connection is established
> Later (much later) a RST flag is sent from the remote PC and the connection fails
Yet the server responds correctly to the second test ... I don't understand ..
I'm reaching out to you because I have a problem ...
I have a Bouygues Telecom BBox at home and behind it a Windows VPN server.
Server configuration:
IP: 192.168.1.222/24 (fixed)
IP on a second private network: 192.168.2.10
My Box configuration:
TCP port forwarding 1723 to --> 192.168.1.22 (which is my VPN server).
I'm testing a first connection locally:
- From a client on my LAN (192.168.1.36)
- I connect to the VPN server (192.168.1.222)
- the connection is successful.
I move on to something more difficult:
- From a client on my LAN (192.168.1.36)
- I connect through my box to the VPN server (port forwarded) (theoanne.ddns.net --> 88.... doesn't matter, the resolution is done
- The VPN responds and the connection works through my box using its public address from my home.
Final check:
- From a client outside my LAN (@private 172.16.0.1) (@public: 89.... etc)
- I attempt a connection through my box (theoanne.ddns.net)
- No response from the VPN server.
I tried instead of just leaving the port open to put it in DMZ, nothing works, I even completely disabled the firewall and all other services on the box, I cannot access my VPN which responds correctly.
Does anyone have an idea?
By analyzing the TCP segments:
- When my box does not have the port open:
> Direct response of a RST flag
- When my box has the port open:
> Establishment of a TCP connection (between the box and the remote PC)
> No way to know if the establishment is made with the VPN server or the box itself
> No response upon launching the VPN connection after the TCP connection is established
> Later (much later) a RST flag is sent from the remote PC and the connection fails
Yet the server responds correctly to the second test ... I don't understand ..
2 answers
-
Hi,
what kind of VPN is it?
--
and ... There you go! -
OK,
PPTP then.
It should work with your server in the DMZ address.
Otherwise, enable VPN passthrough on the box (if it exists).
--
and ... There you go!-
Yes, it should work...
The problem is that I don't have a VPN passthrough option on the box. I would really like to be able to enable something like that, but I can't find anything... I was wondering if we could attack the box via CLI instead of the graphical interface, thinking there might be more options in CLI, but I can't find anything.
This weekend I'll test it behind an Orange box; if the problem disappears, I'll switch operators.
Bouygues Telecom's customer service is unable to respond to my problem and even unable to understand it...- What surprises me is this:
I'm moving on to something more difficult:
- From a client on my LAN (192.168.1.36)
- I'm connecting through my box to the VPN server (redirected port) (theoanne.ddns.net --> 88.... no matter the resolution is done
- The VPN responds and the connection works through my box using its public address from my home.
It shouldn't work in principle.
-
-
