|
Have opened a call with IBM with no resolution. Verified no port problems, connection is via dial up through a RAS into the domain. Client PC is able to Ping the AS400, but unable to telnet either. Question: What in the standard PC software could be causing the winsock error and only on certain machines? Problem: Could not verify a the initial connection through the AS400 Connection manager. Server: AS400E V4R2 Clients: Client Access Software, PC5250 Emulation, V3R2M0 Client Hardware: Various CPUs from P-166 through K6 2/500, 48 Mb RAM min. Sportster 33.6 and C-Net V.90 modems, standard dial-up connections, Standard Client Software: Win95SR2, Win98, Win98SE, Office97Pro, Outlook98SP1, Great Planes Dynamics, Pervasive SQL, MS Proxy Client (All are standard, except 5th system). Dial-Ups All systems dial an 800-number to a bank of 20 modems parallel to the company firewall Sequence of Events: 1st System K6 2/400, 64 Mb, Sportster modem, Win98 Fully operational, experienced no problems verifying connections 2nd System K6 2/500, 64 Mb, C-Net modem, Win98SE Could not verify connection to AS400, error as follows: Wsock32.dll error returned 10060 3rd System K6 2/350, 64 Mb, Sportster modem, Win98SE Could not verify connection to AS400, error as follows: Wsock32.dll error returned 10060 4th System P-233, 64 Mb, C-Net modem, Win95SR2 Could not verify connection to AS400, error as follows: Wsock32.dll error returned 10060 Upgraded to Win98, system was able to verify the AS400 connection. Thinking OS was the problem. 2nd System Formatted hard drive and installed Win98, including standard software Could not verify connection to AS400, error as follows: Wsock32.dll error returned 10060 Didn't work. 5th System P-166, 48 Mb, Sportster modem, Win95SR2 Could not verify connection to AS400, error as follows: Wsock32.dll error returned 10060 Upgraded to Win98, standard software still installed. Could not verify connection to AS400, error as follows: Wsock32.dll error returned 10060 Thinking standard software is causing the connection problem. Formatted hard drive and installed only Win98 and Client Access software. System able to verify connection. Question: What in the standard software could be causing the winsock error and only on certain machines? +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.