On 22 Jun 2017, Peter Howkins <rpcemu.howkins@marutan.net> wrote:
> On Wed, Jun 21, 2017 at 04:10:39PM +0000, Tony Moore wrote:
> > I have installed RPCEmu 0.8.15 / RO 6.20 on Windows 7 Pro 64 bit,
> > running on an HP3500 desktop machine. The installation is fine,
> > apart from a lack of networking.
> >
> > I carefully followed the instructions in the RPCEmu Networking
> > Guide, using OpenVPN v2.3.8 to create the TAP driver. Following
> > installation, *ifconfig -a , and *show inet* , return believable
> > results, however *ping shows no connection.
> >
> > From the log, I note that the TAP driver is 32 bit. Could running
> > this on a 64 bit machine lead to the errors?
>
> No, you're using a 64 bit driver on 64 bit windows 'win32' in this
> context is the name of the API we use (which is suitable for both 32
> and 64 bit).
Thank you for the clarification.
> I don't have any specific answer to this error. However one previous
> user who had this error indicated that it was due to not having set up
> the network bridge in windows correctly, recheck that section of the
> instructions.
I'd tried that several times, before posting.
After some time with Google, I found a thread, Another connection
problem', on the RPCEmu mailing list, from a couple of years ago, in
which David Feugey noted the same error messages. The solution then, as
now, was to downgrade OpenVPN to version 2.1.3, which creates Tap-win32
version 9.7.0. This is compatible with Win 7 Pro, whereas at least one
later version seems not to be.
Having changed the TAP driver, the errors have gone, and all is well.
Many thanks for your response.
Tony
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
No comments:
Post a Comment