MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

RE: Sockets Error 10065



fixed

Any chance the VPN network is using the same IP addressing scheme as your
local network? Your local routers might be getting confused?

Rich

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry
C. Adams
Sent: Monday, June 09, 2014 3:17 PM
To: 'Midrange Systems Technical Discussion'
Subject: Sockets Error 10065

I'm trying to connect to a remote site (well, not THAT remote; just 25 miles
away but I don't want to go there) via a VPN connection.



I'm making the connect through the VPN, but when I try to use System i
Client Access to connect to the System i, I get an error: "Sockets Error
returned 10065". The Help text for the error is: "No route to the system
was found. Check your TCP/IP address and configuration. There may also be a
network problem."



I'm not a network pro, but I read this to mean that the System i is either
not on the network (it's IP address may have been changed) or it is
comatose. Any other possibility?



Jerry C. Adams

You couldn't handle me even if I gave out instructions.

IBM i Programmer/Analyst






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact