Topic: PPTP

[Serge Dutremble]

Trying to connect a Windows 98 SE PC to a E-Smith 4.1 server, I get the following message:
"The computer you are dialing does not respond to a network request."

I have 128bit support on DUN on Win98SE
ppp module loaded on E-Smith
ppp-4mppp module loaded on E-Smith
I have 5 PPTP client enabled on E-Smith

The DUN dialog shows the connection is established and it tries to validate username and password.  After 10-15 seconds, I get the error message above.

I searched throught he forums and found no specific problem similar to this one.  It seems that after enabling 128bit encryption, the connection works for others.  Not here.

Any ideas?

Serge.

[Ken Yuinipo]

You have to uninstall 128bit and reinstall it.  Go to add/remove programs.  Trust me, that will work for you (Windows 98)

[Helpme]

Yes, that worked for me when I was having problems.  I already HAD 128bit encryption installed and I installed all the patches from Microsoft.  But I still was getting bumped off.

Once I uninstalled the 128 patch from my computer and went back to Windows Update at MS, I never had a problem connecting via PPTP.  It works super!!!

[Andrew]

Also, just double check that your client on the Win98 side is set up correctly. A good HOWTO on this is located at http://poptop.lineo.com./help.html.

Regards,
Andrew

[buddy]

upgrade to e-smith 4.1.2

[Serge Dutremble]

I tried the suggestion to remove 128 bit encryption and re-install it but it did not work.  I get the same error.

I have been looking around on the pptp server archive mailing list and it seems that the recommendation there is to recompile the PPTP daemon with a patch.

I do not want to go to this extreme as other users of E-Smith 4.1.1 do not seem to have the same problem (I hope).  Also, I would not like to deviate too much from the standard E-Smith distribution and I would like to try something else first.

It seems that the last suggestion is to update to E-Smith 4.1.2.  I have not read that there was a patch for PPTP on this update.  Any thoughts or more information on this?

Also, I have been reluctant to upgrade to Version 4.1.2 as my system is currently working pretty well (except for PPTP) and I have made some small modifications that may not be saved after the update.  I did not find much information about the manual update and what the update actually does.  Does it replace configuration files?  Does it archived the files replaced?  Does it have an UNDO feature?  Does it have a log of what it did?

I may be a little too paranoid about this but I would hate to screw up something that works. (if it aint broke, (or not too broke) don't fix it!).

Can anyone tell me if their upgrade to 4.1.2 went OK or not?

Thanks.

Serge.

[Shad Lords]

I have found one problem with the pptp server on my 4.1.2 server.  It is in the pptpd-restart event/action.  The lines that have the problem are these.

if ( -f "/var/lock/subsys/pptpd" )
{
    esmith::util::backgroundCommand(0, "/etc/rc.d/init.d/pptpd", "stop");
}

It checks to see if there is a lock file and if there is it just stops it.  I guess the init daemon restarts it.  The problem occurs when this script gets called again.  The second time it is called (usually from ip-change in my case) it doesn't find the lock file and the daemon never gets restarted.  

I found this out by doing a: netstat -nlp
This shows all listening daemons with IP addresses and ports.  I found that the pptpd server was still listening on an old ip address that I had before.  If i issued a service pptpd stop, it would restart and then I could connect.  What I have done so far is to just comment out the first of the 4 above and that seems to work for me.  I don't know of a better fix right now.  

Someone might want to look into why the lockfile doesn't get recreated.

-Shad

[Serge Dutremble]

Nothing I tried worked so far.  Even upgrading manually to 4.1.2.

Here is what my /var/log/messages show (I removed the beginning of each line for improved legibility):

pptpd[13488]: CTRL: Client REMOTECLIENTIP control connection finished
pptpd[13488]: CTRL: Exiting now
pptpd[13482]: MGR: Reaped child 13488
pptpd[13495]: MGR: Manager process started
pptpd[13495]: MGR: Couldn't create host socket
pptpd[13497]: MGR: Manager process started
pptpd[13497]: MGR: Couldn't create host socket
pptpd[13499]: MGR: Manager process started
pptpd[13501]: MGR: Launching /usr/sbin/pptpctrl to handle client
pptpd[13501]: CTRL: local address = LOCALSERVERIP
pptpd[13501]: CTRL: remote address = LOCALIPGIVENTOREMOTECLIENT
pptpd[13501]: CTRL: pppd speed = 460800
pptpd[13501]: CTRL: pppd options file = /etc/ppp/options.pptpd
pptpd[13501]: CTRL: Client REMOTECLIENTIP control connection started
pptpd[13501]: CTRL: Received PPTP Control Message (type: 1)
pptpd[13501]: CTRL: Made a START CTRL CONN RPLY packet
pptpd[13501]: CTRL: I wrote 156 bytes to the client.
pptpd[13501]: CTRL: Sent packet to client
pptpd[13501]: CTRL: Received PPTP Control Message (type: 7)
pptpd[13501]: CTRL: 0 min_bps, 0 max_bps, 32 window size
pptpd[13501]: CTRL: Made a OUT CALL RPLY packet
pptpd[13501]: CTRL: Starting call (launching pppd, opening GRE)
pptpd[13501]: CTRL: pty_fd = 5
pptpd[13501]: CTRL: tty_fd = 6
pptpd[13502]: CTRL (PPPD Launcher): Connection speed = 460800
pptpd[13502]: CTRL (PPPD Launcher): local address = LOCALSERVERIP
pptpd[13502]: CTRL (PPPD Launcher): remote address = LOCALIPGIVENTOREMOTECLIENT
pptpd[13501]: CTRL: I wrote 32 bytes to the client.
pptpd[13501]: CTRL: Sent packet to client
pppd[13502]: pppd 2.4.0 started by root, uid 0
pppd[13502]: Using interface ppp0
pppd[13502]: Connect: ppp0 <--> /dev/pts/0
pppd[13502]: LCP: timeout sending Config-Requests
pppd[13502]: Connection terminated.
pppd[13502]: Exit.
pptpd[13501]: Error reading from pppd: Input/output error
pptpd[13501]: CTRL: GRE read or PTY write failed (gre,pty)=(6,5)
pptpd[13501]: CTRL: Client 131.137.113.190 control connection finished
pptpd[13501]: CTRL: Exiting now
pptpd[13499]: MGR: Reaped child 13501

The "LCP: timeout sending Config-Requests" seems to be where the problem lies.

Any ideas?

Serge.

[Bill]

That's what my log looks like too.

[Serge Dutremble]

In follow-up to this (nothing further ever came from it!), I upgraded to SME 5.0 and I still get the same error message.


I have installed, de-installed and re-installed DUN1.4 with 128-bit support a number of times and I do not get anywhere.

Does anyone have any ideas?  Is there a bug in SME 5.0?

Serge

[Sniperg]

Exactly the same thing here ..Someone needs to respond ..Please