Topic: vpn-pptp lost packets

[Isaac]

I'm connecting from my local lan (with e-smith as router) to a remote lan (with e-smith as router and ptpt-server). Setting up the vpn connection to the remote e-mith server works without any problem.

However i've trouble reaching other machines on the remote lan. It often takes 5 minutes before a ping to this machine results in a response without packet loss. After this the connection to pc's on the remote lan may lost intermittantly.

I'm wondering if these problems have something to do with the windows netwerk setup of the remote lan. As far as i can see there are no connection-problems on the remote lan.

I'm connecting with an xp-client via an e-smith gateway on the local lan.

I welcome any suggestion.

Isaac

This is my the situation on the client side (sorry it's in dutch):

C:\Documents and Settings\Administrator>ipconfig/all

Windows IP-configuratie

        Host-naam  . . . . . . . . . . . .: pc11
        Primair DNS-achtervoegsel. . . . .:
        Knooppunttype . . . . . . . . . . : hybride
        IP-routering ingeschakeld. . . . .: nee
        WINS-proxy ingeschakeld . . . . . : nee

Ethernet-adapter LAN-verbinding:

        Verbindingsspec. DNS-achtervoegsel: buronet.nl
        Beschrijving . . . . . . . . . . .:
          Realtek RTL8029(AS) PCI Ethernet Adapter
        Fysiek adres. . . . . . . . . . . : 00-00-B4-97-C9-6F
        DHCP ingeshakeld. . . . . . . . . : ja
        Autom. configuratie ingeschakeld. : ja
        IP-adres. . . . . . . . . . . . . : 192.168.0.101
        Subnetmasker. . . . . . . . . . . : 255.255.255.0
        Standaardgateway. . . . . . . . . : 192.168.0.2
        DHCP-server . . . . . . . . . . . : 192.168.0.2
        DNS-servers . . . . . . . . . . . : 192.168.0.2
        Lease verkregen . . . . . . . . . : donderdag 5 december 2002 11:43:24
        Lease verlopen . . . . . . . . .  : vrijdag 6 december 2002 11:43:24

PPP-adapter remote e-smith-vpn:

        Verbindingsspec. DNS-achtervoegsel:
        Beschrijving . . . . . . . . . . .:
          WAN (PPP/SLIP) Interface
        Fysiek adres. . . . . . . . . . . : 00-53-45-00-00-00
        DHCP ingeschakeld:. . . . . . . . : nee
        IP-adres. . . . . . . . . . . . . : 10.0.0.250
        Subnetmasker. . . . . . . . . . . : 255.255.255.255
        Standaardgateway. . . . . . . . . : 10.0.0.250
        DNS-servers . . . . . . . . . . . : 10.10.1.1
        Primaire WINS-server. . . . . . . : 10.10.1.1

C:\Documents and Settings\Administrator>ping 10.10.0.1

Pingen naar 10.10.0.1 met 32 byte gegevens:

Antwoord van 10.0.0.150: De doelhost is niet bereikbaar.
Antwoord van 10.0.0.150: De doelhost is niet bereikbaar.
Antwoord van 10.0.0.150: De doelhost is niet bereikbaar.
Antwoord van 10.0.0.150: De doelhost is niet bereikbaar.

C:\Documents and Settings\Administrator>tracert 10.10.1.1

Bezig met het traceren van de route naar SPECTRUM [10.10.1.1]
via maximaal 30 hops:

  1    68 ms    62 ms    61 ms  server.remotelan.nl [10.0.0.150]
  2    80 ms    69 ms    79 ms  SPECTRUM [10.10.1.1]

De trace is voltooid.

[guestHH]

hoi,

please post the same config for your local SME server.

[Isaac]

Hallo,

Thanx for your reply; the sme-server is connected to the internet via eth1 to a dutch (mx-stream-alcatel)dsl-modem. This morning the connection seems to be going allright.

Isaac

[root@sme-server /root]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:4B:41:82:72
          inet addr:10.0.0.150  Bcast:10.255.255.255  Mask:255.0.0.0
          EtherTalk Phase 2 addr:65280/243
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:928488 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1006728 errors:0 dropped:0 overruns:0 carrier:0
          collisions:6153 txqueuelen:100
          Interrupt:9 Base address:0x300

eth1      Link encap:Ethernet  HWaddr 00:10:4B:58:99:7B
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:964397 errors:1 dropped:0 overruns:0 frame:1
          TX packets:817976 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1161 txqueuelen:100
          Interrupt:7 Base address:0x220

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          EtherTalk Phase 2 addr:0/0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:5479 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5479 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

[root@sme-server /root]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth1
10.0.0.0        *               255.0.0.0       U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         192.168.0.151   0.0.0.0         UG    0      0        0 eth1

[Bill Talcott]

This doesn't really fix your problem, but it may get around it. What about setting up an IPSec VPN between the two SME servers? On a NATed connection, only one of the PCs can create a PPTP VPN connection to a specified server. With an IPSec VPN, you create a tunnel between the two networks and all PCs on both LANs can communicate...

[isaac van den berg]

Bill Talcott wrote:
> IPSec VPN, you create a tunnel between the two networks and

To be honest I don't know how to do that (yet). Furthermore we will use the pptp-connection for employees working at home.

I think our lost-packets problem is hardware related. I've been asking around and people are complaning about printers sometimes not printing or certain machines being unresponsive.

Isaac

[Bill Talcott]

isaac van den berg wrote:
>
> Bill Talcott wrote:
> > IPSec VPN, you create a tunnel between the two networks and
>
> To be honest I don't know how to do that (yet). Furthermore
> we will use the pptp-connection for employees working at home.

http://myezserver.com/downloads/mitel/contrib/freeswan/ though it seems to be having a problem at the moment. Basically you just install an RPM and supply a few details about the SME at each end.

[Isaac]

Bill Talcott wrote:
>> > > IPSec VPN, you create a tunnel between the two networks and
> >
> > To be honest I don't know how to do that (yet).
>
> http://myezserver.com/downloads/mitel/contrib/freeswan/
> though it seems to be having a problem at the moment.
> Basically you just install an RPM and supply a few details
> about the SME at each end.

Thanx, Bill, I'll try to do a setup.

isaac