Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been able to connect to my domain using a PPTP connection from inside my firewall. The connection points to the internal IP address 192.168.0.102 of the Linux box serving the VPN access.
What I was unable to test was a connection out through the firewall (DLink 624) to the firewall's external address, this should be port forwarded to the 192.168.0.102 address of the Linux box. I have not tested that since I found the DLink document quoted above but I would expect that to work.
I thought you were describing attempt to call out from inside the inner network protected by the Linux box. In my case 192.168.1.* addresses. I understand this is not supposed to work.
I have been able to connect to my domain using a PPTP connection from inside my firewall. The connection points to the internal IP address 192.168.0.102 of the Linux box serving the VPN access.
Try a test comment out that line in your chap-secrets file and place a valid username for the domain in the file with a password, try logging on using that usernae and password, the you will at least see if it's an error in your Chap-secrets line or within samba, but it would let you know if the VPN is working appropriately.
I have figured out that it is VPN's authentication process that is giving me trouble. This is my chap-secrets:
Code:
darren.mo pptpd mypassword *
On my Windows machine, I typed in the correct username and password and I allowed only CHAP authentication. This is the log file:
Code:
The remote system is required to authenticate itself
but I couldn't find any suitable secret (password) for it to use to do so.
(None of the available passwords would let it use an IP address.)
So that didn't work...
Next I tried VPN with no authentication at all. I put "noauth" in both /etc/pptpd.conf and /etc/ppp/options.pptpd. It connected perfectly!
Hmmmmm...I wonder if that log message about the IP address is important...
I DID IT!!! All I had to do was put quotes around my password because my password has all sorts of symbols (including the # symbol, which is also a comment).
But now...I have a new question! How do I configure my server so that I can connect from another computer on the network out to moenterprise.no-ip.org instead of 192.168.249.105? It doesn't work because the server thinks that it is looping back because both computers are behind the same router. So...how? Do I edit the /etc/hosts file or something?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.