×
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.
Have you tried applying the latest service level package for iAccess and seeing if that helps?
Regards,
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ashley Dean Myles
Sent: Tuesday, June 7, 2016 9:13 AM
To: midrange-l@xxxxxxxxxxxx
Subject: IBM iAccess Client Solutions - timeout error MSGSOCK007
Greetings!
I have a semi-retired sales executive that I set up with a Lenovo Windows 10
laptop and the latest release of IBM iAccess Client Solutions (5250 terminal
session). She is connecting through a Cisco VPN and had no issues for the
first two weeks it was fast and reliable.
Last week, she got an error from iAccess ³MSGSOCK007 could not connect²
and the only reference to this code was in previous posts to this list
group. Unfortunately, that thread did not have a solution or clue to what
this error code means. Each successive attempt to connect (even with new
sessions with new session names) fails with the same error code. We do not
use SSL and I have no issue connecting via other devices using VPN and
identical session and login information.
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
