> The pending read failure is due to some problem with the "tap" device
> that the service uses to communicate with the driver. What it sounds
> like is happening is that the driver or the OS have misconfigured the
> I/O for the tap device and the asynchronous reads that the service is
> attempting are failing, thus the "hang" until the service attempts
> another read.
> I would try uninstalling the whole thing, including a registry cleanup and
> deleting the cipsrvr.exe and cipdrvr.sys files and the reinstalling.
> You also don't say whether you're running NT4.0 or Win2K.
I'm running Win2K with ADSL (256Kbps). This is the Interface List:
0x1 ........................... MS TCP Loopback interface
0x2 ...00 90 d0 14 eb c4 ...... Alcatel SpeedTouch USB RFC1483 ADSL Miniport
0x3 ...08 00 58 00 00 01 ...... DKW Heavy Industries VPN Adapter.
0x4000005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
If it is a configuration issue, shouldn't the tunnel not work at all? It is
strange that it works fine for a few minutes, and then hangs. I tested
whether it was because of high throughput rates as Jan Olderdissen
mentioned, but even without transferring anything over the tunnel, it stops
working after a few minutes.
Juan Antonio Ruiz Zwollo
> On Thursday 07 March 2002 10:41 am, you wrote:
> > Hi!
> > On one side, I'm using CIPE-Win32-2.0-pre10.
> > On the other side, cipe-1.5.2 on Linux.
> > There are various tunnels going from the Linux box to other Linux boxes.
> > All work fine. But the tunnel to the Win32 box hangs every few minutes.
> > I ran the Win32 CIPE as a console, and found out that each time the
> > transfer hangs, the following output appears:
> > [SIP] failed on pending read attempt
> > It is strange that the transfer just stops and the tunnel no longer
> > but CIPE continues to run. If it would at least stop itself, I could
> > restart it every time the tunnel hangs.
> > What can be done? I already tried setting the Timeout value higher.
> > Kind regards,
> > Juan Antonio Ruiz Zwollo