VPN tunnel ws. Remote Desktop (Terminal client)

Hello group,

I've set up a linux routing-server with pptp-client. Routing is
enabled. Default route points to our firewall.

The connection to the VPN network is established. FTP and VNC are
working without problems.

My problem is very curious: I connect via my Remote Desktop/Terminal
client. I get a connection (the screen turns black) but I get no login
dialouge. After a while an error accures: "Connection failed. Check
network properties" (or something like that). If I connect again and
then start another instance of the client and also connect it, the
second instance works well.
After that I tried to connect only one client. This worked also great
with the instance, that got the prior connection.
Then I closed all clients and startet a new one. I got no connection.

I tried the same procedure from two computers. Both Windows XP prof.
SP2. They work identicly.

In /var/log/messages there are some lines like this:
Aug 25 20:08:31 vpngate pptp[21695]: anon
log[decaps_greptp_gre.c:404]: buffering packet 5429 (expecting 5426,
lost or reordered)

But they are not written while connecting the client.

In /var/log/firewall there are some entries, that packets were accepted
(high log level), but no messages of dropped packets.

Anyone has got an idea?

Thanks in advice!

Christian Kusenbach
Germany

In comp.os.linux.networking (E-Mail Removed):
> Hello group,

> I've set up a linux routing-server with pptp-client. Routing is
> enabled. Default route points to our firewall.

> The connection to the VPN network is established. FTP and VNC are
> working without problems.

> My problem is very curious: I connect via my Remote Desktop/Terminal
> client. I get a connection (the screen turns black) but I get no login
> dialouge. After a while an error accures: "Connection failed. Check

Why would you need all the bloatware? Ssh allows anything + more.

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 395: Redundant ACLs.

Michael Heiming <michael+(E-Mail Removed)> wrote in news:j691u2-
(E-Mail Removed):

> In comp.os.linux.networking (E-Mail Removed):
>> Hello group,
>
>> I've set up a linux routing-server with pptp-client. Routing is
>> enabled. Default route points to our firewall.
>
>> The connection to the VPN network is established. FTP and VNC are
>> working without problems.
>
>> My problem is very curious: I connect via my Remote Desktop/Terminal
>> client. I get a connection (the screen turns black) but I get no login
>> dialouge. After a while an error accures: "Connection failed. Check
>
> Why would you need all the bloatware? Ssh allows anything + more.
>

I didn't know you can encap ip and route over SSH?

I like Open VPN myself.

http://openvpn.net/

Klazmon




> [..]
>

In comp.os.linux.networking Llanzlan Klazmon <(E-Mail Removed)>:
> Michael Heiming <michael+(E-Mail Removed)> wrote in news:j691u2-
> (E-Mail Removed):

>> In comp.os.linux.networking (E-Mail Removed):
>>> Hello group,
>>
>>> I've set up a linux routing-server with pptp-client. Routing is
>>> enabled. Default route points to our firewall.
>>
>>> The connection to the VPN network is established. FTP and VNC are
>>> working without problems.
>>
>>> My problem is very curious: I connect via my Remote Desktop/Terminal
>>> client. I get a connection (the screen turns black) but I get no login
>>> dialouge. After a while an error accures: "Connection failed. Check
>>
>> Why would you need all the bloatware? Ssh allows anything + more.
>>

> I didn't know you can encap ip and route over SSH?

Don't think you can, the remark was about all those doze remote
admin tools. Seems over 90% of all OP seem to surround doze, I
don't use and have no problems at all. Even if it's easy enough
tunneling rdesktop through ssh. ;-)

> I like Open VPN myself.

> http://openvpn.net/

Looks good!

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 355: Boredom in the Kernel.

Michael Heiming wrote:

>> I didn't know you can encap ip and route over SSH?
>
> Don't think you can, the remark was about all those doze remote
> admin tools. Seems over 90% of all OP seem to surround doze, I
> don't use and have no problems at all. Even if it's easy enough
> tunneling rdesktop through ssh. ;-)

Actually, you can built a VPN through SSH. There was even an article about
it, in Linux Journal, a couple of years ago. However, it's not a good idea
as you're then running TCP over TCP, which can cause performance issues.
OpenVPN uses UDP (though if necessary, it can also use TCP) , which has the
same performance characteristics as Ethernet or other "best effort"
protocol.

In comp.os.linux.networking James Knott <(E-Mail Removed)>:
> Michael Heiming wrote:

>>> I didn't know you can encap ip and route over SSH?
>>
>> Don't think you can, the remark was about all those doze remote
>> admin tools. Seems over 90% of all OP seem to surround doze, I
>> don't use and have no problems at all. Even if it's easy enough
>> tunneling rdesktop through ssh. ;-)

> Actually, you can built a VPN through SSH. There was even an article about
> it, in Linux Journal, a couple of years ago. However, it's not a good idea
> as you're then running TCP over TCP, which can cause performance issues.
> OpenVPN uses UDP (though if necessary, it can also use TCP) , which has the
> same performance characteristics as Ethernet or other "best effort"
> protocol.

Actually, there's even a howto available:

http://en.tldp.org/HOWTO/VPN-HOWTO/


--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 120: we just switched to FDDI.