Mark Rogers wrote:
> Win95 can dial into my machine great everything works, win3.x using
> Trumpet winsock (any version), dials, gets authenticated, is assigned an
> IP address and then no data gets over the line.
>
> This happens regardless of any ppp settings I've tried or anything else,
> this
Hi,
Ok last time I asked I got people saying it works for me should work
for you.. Well, thanks but it doesn't.
Win95 can dial into my machine great everything works, win3.x using
Trumpet winsock (any version), dials, gets authenticated, is assigned an
IP address and then no data gets over the
I would suggest you check the docs for ppp-2.3.3 very carefully as a lot
of the options changed from 2.2.0f
Graham...
Mark Rogers wrote:
>
> Hi.
>
> I was running pppd 2.2.0f and all was good. Win95, Mac (FreePPP), and
> Win3.1
> (Winsock 2.0b) worked fine. That is they could all dial into my
At 10:35 AM 6/26/98 +1000, someone wrote:
>Hi.
>
> I was running pppd 2.2.0f and all was good. Win95, Mac (FreePPP), and
>Win3.1
>(Winsock 2.0b) worked fine. That is they could all dial into my linux
>machine (on a stallion serial board).
>
>Now I upgrade to 2.3.3 and all I see in Winsock is ppp f
Hi.
I was running pppd 2.2.0f and all was good. Win95, Mac (FreePPP), and
Win3.1
(Winsock 2.0b) worked fine. That is they could all dial into my linux
machine (on a stallion serial board).
Now I upgrade to 2.3.3 and all I see in Winsock is ppp frame check
errors and no connection. Win95 works g
Hi.
I was running 2.2.0f and all was good. Win95, Mac (FreePPP), and Win3.1
(Winsock 2.0b) worked fine.
Now I upgrade to 2.3.3 and all I see in Winsock is ppp frame check
errors and no connection.
Mgetty parses the info fine but PPP dies with messages like:
serial link is not 8-bit clean
or
LC
