×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
