Providing logs will greatly increase your chances of people helping you. Do 'tincd -n VPNname -D -d2' or -d3 or -d4 until you see error messages, do this on both sides.
My common mistake is forgetting to copy the public cert to the other side. -Cobin On Jan 26, 2015 5:53 AM, "Henk van der Meer" <[email protected]> wrote: > Hello, > > > > I have 4 VM’s running in Microsoft Azure. They all should have similar > configurations except from their tinc ip addresses of course. > > They run tinc 1.0.24. I have a 5th machine, my development machine. > > > > I am able to ping all 4 VM’s from my computer when I start tinc from the > commandline (tincd –n innomeer –D –d 2). > > 3 of the computers also work ok when running tinc as a service (tincd –n > innomeer). > > The 4th only works ok from the command line, but doesn’t allow me to ping > it when it is running as a service. > > > > As far as I can tell from the log information my machine and the VM > running tinc as a service do connect, but ping just won’t work. I can’t > tell from the log file what is wrong. > > > > Can somebody tell me where I could look to see what is wrong? > > > > Thank you, > > > > Henk van der Meer > > > > _______________________________________________ > tinc mailing list > [email protected] > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > >
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
