Re: How to tinc windows 2k client to linux server

Tech-Archive recommends: Speed Up your PC by fixing your registry

> You will likely get more help with Linux VPNs and their
> logs by asking a Linux focused list.

I am not sure where the problem is. on server side (linux) or client
side (Windows)

> But you also need to try to be more careful with your
> spelling and wording, as well as very specific about
> your actual problem.
right, sorry for that! And sorry for my horrable english writing, I'll
give my best!

> Generally, when Ping fails the next step is to try TraceRt
> or PathPing.

Thanks for this hint, here ist what pathping says:
C:\>pathping 10.1.1.1
Routenverfolgung zu 10.1.1.1 über maximal 30 Abschnitte
0 soundmachine [10.1.1.2]
1 ...
Berechnung der Statistiken dauert ca. 25 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 soundmachine [10.1.1.2]
100/ 100 =100% |
1 --- 100/ 100 =100% 0/ 100 = 0% soundmachine [0.0.0.0]

But who is 0.0.0.0??

> Many firewall devices/software disallow Ping (i.e., ICMP) EVEN
> when they appear disabled.

I can ping the real internet IPs so I thought that here is no problem.

> You might try something more "application" like, perhaps Telnet or
> NetCat (nc.exe is NOT a built-in Windows program though) with
> a specific and known working service, e.g., a web server from the
> client:
>
> telnet Web.Server.IP.Address 80
>
There is no connection possible with telnet.

Ok, lets sum it up:
The Packages arrive at serverside cause there is the syslog entry.
If my sylsog dosn't lie the server send the ping to my client
pathping colud not realy help -or does it?

Hmm .. I would say: The arrived package from my server is not
recognised by my client an get droped.

To make another test I edited the Key Files to occour an error because
of unmatching keys. Ping my server one more time and yea(!) in my Win
Eventlog I can see now the following:
tinc: Bogus data received from ciserver (83.65.166.XXX port 655).

And in my server syslog I can see:
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Connection from
80.108.85.21 port 6181
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending ID to (null)
(80.108.85.21 port 6181): 0 ciserver 17
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending 14 bytes of
metadata to (null) (80.108.85.21 port 6181)
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Got ID from (null)
(80.108.85.21 port 6181): 0 home 17
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending METAKEY to
home (80.108.85.21 port 6181): 1 94 64 0 0
9B0AC9756F4BEC31D88E8B00C70AE1EB4B20BB2A3CA42C8CFEECA61EB2CE52A46E554E0CA3CF687637E209F65904E97E140D3E9AEAD353168B498C4BB5191BC5C9A53954E2C54D36E24A0D090C9DCBA2D8466FC501B3463B8E52B60561D2FC95C31BF2A8360E690FD70461FB47D32AA6285AE7FFC81DCEDAA96A4D41220F4490
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending 269 bytes of
metadata to home (80.108.85.21 port 6181)
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Got METAKEY from home
(80.108.85.21 port 6181): 1 94 64 0 0
88E689854A6624976FC86381EE70D46EA5053197C2B42D18D524954EAAE2816D62F7603AF9573FE8365B0649C60235C89CC5A974106A0F40DE9C01F4BE85DE3C454A78DFE9CB26185B0899256C27B90024713B5D927D8D6F5A5727BFE18D20E0E741B2778859E9C6B2E4E684F5FA0DA8ED06F3B88268DABB42454AB3C5C927EC
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending CHALLENGE to
home (80.108.85.21 port 6181): 2
EEB38A2E0F0627C6E1D38314113BDBDBFC6676534E910F390FF1C24F09029C49BACF8227194CCA8C362F135AEFFCC5DADD20A7CA36E926A58507FFA922C0508342AA395A22F5460A147B6A65D20EBCE969B894651CE71E8F53D34FB8EBE267723F186095FF7E8E150D634892E5A4F2C3A260DF158134C12DFAD1C77E2C5B4F6B
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending 259 bytes of
metadata to home (80.108.85.21 port 6181)
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Got CHALLENGE from
home (80.108.85.21 port 6181): 2
73AC3A3ECD7E558DEBF25D9E00DDEBA7133A2D203542B1501AD56B7883CFA5E32C899E940453338F257734142FF3EACB522CE8534211C2570DAD622DDA46C87C096921299AA9CC4B4915DDDA9A11F3412399EEE7B6B5887679EC1D5E5C67D3DA6ED0CC840544724E5E8060A1261509DE232BC94AFD6A7B8EAF8512D3F3ED424A
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending CHAL_REPLY to
home (80.108.85.21 port 6181): 3
E06B5E5FFE0F0969852B43AB11846495EB266656
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Sending 43 bytes of
metadata to home (80.108.85.21 port 6181)
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Connection closed by
home (80.108.85.21 port 6181)
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Closing connection
with home (80.108.85.21 port 6181)
Jan 4 16:06:09 localhost tinc.consult-it[4831]: Purging unreachable
nodes

So the Client closed the connection. Do you know more about tinc and
were my mistakes are?

Thx!
Christian Maier

.

Relevant Pages

  • Re: How to tinc windows 2k client to linux server
    ... > a Windows 2K Client over the internet via VPN. ... > But the Ping Packages never arrive my windoze client. ... > happens if I ping from server to client. ... > metadata to home (80.108.85.21 port 6343) ...
    (microsoft.public.win2000.networking)
  • Re: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • RE: cannot connect computer
    ... if I type in the url of the server i get through ok. ... client computer to SBS domain. ... | I am unable to ping the sbs server by ip or name. ...
    (microsoft.public.windows.server.sbs)