[pptp-server] Select() errors --- client or server???

Wed Jun 28 10:12:52 CDT 2000

|-----Original Message-----
|From: pptp-server-admin at lists.schulte.org
|[mailto:pptp-server-admin at lists.schulte.org]On Behalf Of Brian Aust
|Sent: Wednesday, June 28, 2000 10:48 AM
|To: pptp-server at lists.schulte.org
|Subject: [pptp-server] Select() errors --- client or server???
|
|
|Rumour around here seems to have it that "CTRL:  select() error" messages
|appearing in the /var/log/messages file are generally a result of a fubar'd
|Windoze client setup, as opposed to anything wrong on the poptop server.
|Here's a sample set:
|

I can verify this as in my case it was a foobar'd Windows client...

|Jun 28 01:21:30 bnyatalie pptpd[20208]: CTRL: Client 24.162.230.175 control
|connection started
|Jun 28 01:21:30 bnyatalie pptpd[20208]: CTRL: Starting call
|(launching pppd,
|opening GRE)
|Jun 28 01:21:30 bnyatalie kernel: CSLIP: code copyright 1989 Regents of the
|University of California
|Jun 28 01:21:30 bnyatalie kernel: PPP: version 2.3.7 (demand dialling)
|Jun 28 01:21:30 bnyatalie kernel: PPP line discipline registered.
|Jun 28 01:21:30 bnyatalie kernel: registered device ppp0
|Jun 28 01:21:30 bnyatalie pppd[20209]: pppd 2.3.8 started by root, uid 0
|Jun 28 01:21:30 bnyatalie pppd[20209]: Using interface ppp0
|Jun 28 01:21:30 bnyatalie pppd[20209]: Connect: ppp0 <--> /dev/pts/2
|Jun 28 01:21:59 bnyatalie pptpd[20208]: CTRL: Error with select(), quitting
|Jun 28 01:21:59 bnyatalie pptpd[20208]: CTRL: Client 24.162.230.175 control
|connection finished
|Jun 28 01:21:59 bnyatalie pppd[20209]: Modem hangup
|Jun 28 01:21:59 bnyatalie pppd[20209]: Connection terminated.
|Jun 28 01:21:59 bnyatalie pppd[20209]: Exit.
|
|I've tried numerous server configurations, always on stock RedHat6.2 box,
|with poptop 1.0.0, along with ppp of either 2.3.8 or 2.3.11.
|

Yeap exactly what I saw!

|The Windoze client is always W98 SE.  I have done EVERYTHING imaginable on
|this W98 client -- uninstall DUN, reinstall DUN, install msdun128.exe
|128-bit DUN upgrade.....   then even so far as to remove all dialup and
|ethernet adapters, so there's nothing in the Network control panel, then
|reinstalling everything.
|

I hope you didn't download the patch from Microsoft's web site. For Win98SE
the patch completely screws up Windows as it was written for WIN95 & 98 not
98SE!

For 98SE you merely use the included VPN configuration.

|SOMETIMES the connection works and i can get in and browse the LAN -- but
|only about 10-15% of the time.  Most usually the W98 client hangs on the
|"Verifying Username....." screen.
|
|
|Sooo......    a few questions:
|
|1.  Has anyone determined what causes these select() errors?
|
|2.  Those of you who have a consistently working VPN --- what Windoze
|clients are you using?  NT?  98 (1E or 2E)?, 2000?   Any other patches
|besides the DUN128-bit upgrade?
|

Nope, however I've upgraded from the Windows 98SE update page...

Also you HAVE to have VPN Adapter #2 installed by the Windows Setup
Add/Remove programs if you are using PPP on another device... I.E. Dialup to
an ISP.

If you've applied the downloadable EXE patch from Microsoft, start
re-installing Win98SE, because it's very difficult to undo the damage.

|3.  For NT's DUN, I don't see any way possible to select "Microsoft VPN
|adapter", especially since it doesn't seem possible to save DUN
|profiles for
|each server.... even after installing PPTP.  Can PoPToP be used with NT DUN
|clients?
|

Dunno on this one.

1.0.0-1 is working fine for me, FINALLY.

As for browsing, it seems that windows "registers" the domain the system is
first initiated to when the networking components are installed.

If you install VPN after say another adapter card, or after having connected
to another domain, you will -NOT- be able to see the remote shares (I've
tested this).

Your clients must be members of the same domain when windows is first
installed or Networking is setup...

The original domain is then added to the dialup VPN settings (search the
registry) for each adapter.

If you've already set up another domain or workgroup, you'll need to
uninstall all networking components, edit the registry VPN entries, then
re-add in all networking components, making the machine a member of the
remote domain.

Then browsing works (at least for me).

Something is wrong with this, NORMALLY windows can detect other domains on
the same lan segment. It seems that once you install VPN and establish a
connection Windows does not "see" the remote LAN as being on the same
segment as the local one...

(I haven't tried setting the remote and local to the same subnet though).

In all cases however, specifying the complete UNC does work.

-JMS

|Any and all help is greatly appreciated guys,
|
|Cheers,
|Brian
|