similar to: Problem starting connection.

Displaying 20 results from an estimated 1000 matches similar to: "Problem starting connection."

2015 Oct 20
3
Problem starting connection - build tinc VM
Hello, I have send the message below this message before. I guess nobody is familiar with my problem. So the next step is "use the source". The thing is I'm a windows developer. I have tried to build tinc before, a few years ago. And I know the linux developers think it is easy. And it always is, once you know what to do. But I got so many errors last time, I just gave up. I
2015 Jan 26
0
Windows service tincd behaves different from command line tincd
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" <hvdmeer at timeservice.nl> wrote: > Hello, > > > > I have 4
2015 Oct 20
1
Problem fixed, still like to build tinc
On Tue, 20 Oct 2015 11:08:35 +0200 Henk van der Meer <henk at innomeer.nl> wrote: > Hello, > > With regards to my previous message and to help others. > Using the source I tracked the problem down to a call to getaddrinfo > that failed. > After a lot of trying I found out that somehow my host file got > notepad++ macintosh file endings. Never even knew it existed.
2015 Jan 26
2
Windows service tincd behaves different from command line tincd
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
2004 Nov 04
0
Warning: Unacceptable file attachment detected
[ ENGLISH ] Our virus detector has just been triggered by a message you sent:- To: screensavers@pagina.nl Subject: Re: Hi Date: Thu Nov 4 09:38:54 2004 One or more of the attachments are on the list of unacceptable attachments for this site and will not have been delivered. Consider renaming the files or putting them into a "zip" file to avoid this constraint. The virus
2017 Dec 30
2
Having problems connecting
Parke, Thank you for your suggestion, but I am already using those subnet settings. And how could they be wrong if the two peers start communicating at some point without changing the settings? Henk -----Oorspronkelijk bericht----- Van: tinc [mailto:tinc-bounces at tinc-vpn.org] Namens Parke Verzonden: vrijdag 22 december 2017 23:20 Aan: tinc at tinc-vpn.org Onderwerp: Re: Having problems
2018 Jan 02
1
Having problems connecting
One of the nodes is running without a firewall. The other is on a public Azure server and can't run without firewall. It is running without firewall on its own (10.23.23.1) network card. How could the firewall do this when it starts running after some time without changing anything to the firewall? Henk -----Oorspronkelijk bericht----- Van: tinc [mailto:tinc-bounces at tinc-vpn.org] Namens
2015 Oct 20
1
Problem fixed, still like to build tinc
On Tue, Oct 20, 2015 at 11:08:35AM +0200, Henk van der Meer wrote: > Using the source I tracked the problem down to a call to getaddrinfo > that failed. After a lot of trying I found out that somehow my host > file got notepad++ macintosh file endings. Never even knew it existed. Oh, maybe I'll have to add proper handling of Macintosh file endings to tinc then... > Anyhow
2019 Aug 30
0
Upgrade Samba 4
Hi, Now, my functional level is 2008_R2. samba-tool domain level show Domain and forest function level for domain 'DC=empres,DC=com,DC=br' Forest function level: (Windows) 2008 R2 Domain function level: (Windows) 2008 R2 Lowest function level of a DC: (Windows) 2008 R2 Everything looks fine, the replication, the consistency between the DCs, however I have checked this information in
2016 Sep 26
3
Receiving packet failed: (10054) (2nd post)
Thank you for your response. Yes, I know something changed, hence the smiley. I have looked at the code (I was able to build it under the new windows bash). It turns out that the error was on a udp receive, not a tcp connection. Didn't know you would get this error. Anyhow near the location of the error there was a remark about IPv6. I hadn't looked at that yet. So I turned IPv6 off at
2016 Sep 26
0
Receiving packet failed: (10054) (2nd post)
On Mon, 26 Sep 2016 07:46:36 +0000 Henk <henk at innomeer.nl> wrote: > > Hello, > > I have a problem connecting to one of my computers using tinc 1.0.x > on Windows. It used to work, now it suddenly stopped (and nothing > changed :) ) When something worked for a long time but now it's not, then there was a change. It's time to determine where! > > We
2016 Sep 27
0
Receiving packet failed: (10054) (2nd post)
On Mon, 26 Sep 2016 20:40:47 +0000 Henk <henk at innomeer.nl> wrote: > Thank you for your response. > Yes, I know something changed, hence the smiley. > > I have looked at the code (I was able to build it under the new > windows bash). It turns out that the error was on a udp receive, not > a tcp connection. Didn't know you would get this error. > > Anyhow near
2017 Dec 22
0
Having problems connecting
On Fri, Dec 22, 2017 at 5:17 AM, Henk <henk at innomeer.nl> wrote: > I am having problems connecting two computers over the vpn. > Form the debug messages it looks like the two computers are connected via tcp on port 655. > > But when I try to ping the other computer I get the message: > > Cannot route packet from TrackServer (MYSELF): unknown IPv4 destination address
2017 Dec 31
0
Having problems connecting
On Sat, Dec 30, 2017 at 10:59 AM, Henk <henk at innomeer.nl> wrote: > Thank you for your suggestion, but I am already using those subnet settings. > And how could they be wrong if the two peers start communicating at some point without changing the settings? I believe there is a difference, with Tinc, between nodes connecting to each other, and nodes deciding to route VPN traffic to
2018 Sep 09
2
Autoreply ( Autoreply (Re: getting invites to rtp ports ??))
Bedankt voor uw bericht. Online4You is sinds 1 augustus niet meer operationeel. Per e-mail hebben wij u geinformeerd over de omstandigheden en uw opties. Helaas kunnen wij u niet meer helpen, uw mail wordt niet doorgestuurd en/of beantwoord. Indien uw abonnement is overgenomen door KovoKs, kijk dan voor contactgegevens op https://www.kovoks.nl/. Dank voor uw vertrouwen de afgelopen jaren! Met
2015 Aug 06
0
2nd DC, internal DNS: dns_tkey_negotiategss: TKEY is unacceptable - SOLVED
On 06/08/15 09:08, Roel van Meer wrote: > L.P.H. van Belle writes: > >> is the time in sync on your servers ? > > Yes it is. > > I managed to make it work by specifying the primary DC as nameserver > in /etc/resolv.conf of the secondary DC. As soon as I do that, > samba_dnsupdate works on the secondary. When I change it back to use > the local Samba as resolver,
2006 Apr 10
0
P3Scan support
Hello, I want to ask if CentOS will support P3Scan (http://p3scan.sourceforge.net/) as RPM delivered with the distribution? For explanation: P3Scan is an transparent mailproxy. It uses ClamAV and SpamAssassin to distinguish between Spam- Virus- and normal Mail. Its more usefull to get an update via the repos instead of compiling it by myself. I hope you understand my englisch. ;) Greets Jens
2003 Apr 16
0
Scheepjeswolharmonie Veenendaal
2015 Aug 06
0
2nd DC, internal DNS: dns_tkey_negotiategss: TKEY is unacceptable
is the time in sync on your servers ? >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at lists.samba.org] Namens Roel van Meer >Verzonden: donderdag 6 augustus 2015 9:28 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] 2nd DC, internal DNS: >dns_tkey_negotiategss: TKEY is unacceptable > >L.P.H. van Belle writes: > >> check the rights
2003 Mar 20
0
Misschien leuk voor u
- Deze mail is doorgezonden omdat iemand dacht dat u wellicht interesse zou kunnen hebben. Mocht u na het lezen van deze mail geen interesse hebben dan kunt u de boodschap verwijderen, u ontvangt geen verdere berichten meer tenzij u daar uitdrukkelijk om verzoekt. Computervrienden De club computervrienden gaat zich lanceren in mei 2002. Voordat deze datum wordt bereikt willen wij het volgende