Yes, you are correct. I had mistyped a route and was trying to add
192.168.40.0/2 instead of 192.168.40.0/24.
Thanks for your help. I think I had looked at that long enough that I
would have never found the problem.
Jay
Michael Bretterklieber wrote:
Hi,
it looks everything is ok, until your
Hi,
it looks everything is ok, until your routes were added. Could you try
this without these routes?
On Mon, 29 Mar 2004, Jay Hall wrote:
> Mar 29 06:37:37 ST_CHARLES mpd: [vpn] IPCP: Up event
> Mar 29 06:37:37 ST_CHARLES mpd: [vpn] IPCP: state change Starting -->
> Req-Sent
> Mar 29 06:37:37 ST
Here is a copy of the log file for the client.
Mar 29 06:35:40 ST_CHARLES mpd: mpd: process 81252 terminated
Mar 29 06:37:37 ST_CHARLES mpd: mpd: pid 81306, version 3.17
([EMAIL PROTECTED] 10:34 26-Mar-2004)
Mar 29 06:37:37 ST_CHARLES mpd: [vpn] ppp node is "mpd81306-vpn"
Mar 29 06:37:37 ST_CHARL
Hi,
On Sun, 28 Mar 2004, Jay Hall wrote:
> OK, I think I have an MTU negotiation problem. The server side sets an
> MTU of 1458 and the client side sets an MTU of 1456. Occassionally, the
> MTUs on the client and the server will be the same and then the
> connection comes up and runs like a cham
possible that this is a hardware issue?
Thanks for your help.
Jay
Date: Sat, 27 Mar 2004 08:08:34 -0600
From: Jay Hall <[EMAIL PROTECTED]>
Subject: PPTP mtu
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii; format=flowed
I am using mpd to
I am using mpd to establish a DSL connection and, once that connection
is established, I am brining up a PPTP connection. However, I am having
problems keeping the PPTP connection up.
In the logs on the remote machine, I am seeing the following error message:
Mar 27 00:22:52 ST_CHARLES mpd:
