pc5250 license error cwbco1003 - sockets error, function returned 10013

jambear
jambear used Ask the Experts™
on
I have a remote user who no longer can connect to our as400. He connected fine yesterday. Everyone else at his location can connect with no problem. He is running vista home premium. When he goes to connect he gets the error message:

pc5250 license error
cwbco1003 - sockets error, function returned 10013

I recreated the connection through the navigator and recreated the session and i get the same issue. When i restart the PC it prompts for the password which made me think it worked. But after i put the password in, i get the same error. I have attached a screenshot of the error. Any help would be greatly appreciated.

Thank you!
Untitled.jpg
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
First obvious step is to run the "Verify connection" process. You might simply run CWBPING from a Windows command line to see if any obvious areas of trouble are exposed.

CWBCO1003 refers to connection problems. I'd wonder about Windows firewall or address resolution from that specific PC, as long as others had no problem.


Tom

Author

Commented:
Thanks for the response. I will give this a try on Monday. I tried the "Verify Conneciton" process from the program itself and it was successful. The windows firewall is off also. I run the command that you suggested from a command prompt on Monday. Thanks again for the response!
You can find details about CWBPING in the User's Guide, which is normally installed as part of iSeries Access and made available through the Start-> Programs menu. CWBPING is essentially what "Verify connection" does.

However, the command has parm options that might be helpful. You can review those options in the User's Guide or simply run CWBPING with no parms to get a basic list of the parms that can be set. One parm that might be useful for [/user:userid]. That can let you specify the specific user that has trouble on that PC. Best would be reading the User's Guide page.

Because everything can be specified as parms, you can sometimes find a value that works for CWBPING but not for "Verify connection". That can mean that something is wrong with how the 'connection' has been defined on that PC -- it works when given manually, but not when pulled from the configuration.

Tom
OWASP: Forgery and Phishing

Learn the techniques to avoid forgery and phishing attacks and the types of attacks an application or network may face.

Gary PattersonVP Technology / Senior Consultant
Commented:
Well, the classic question is "What changed?".

Start with the workstation and work outward to the local network, then the WAN, then the corporate network.  New software?  Automatic OS updates?  Client Access service pack?  AV program updated?  Router, firewall or VPN changes?  New wireless access point installed?  New workstations installed at the remote location.  

If you can identify what changed, you're usually well on the road to diagnosing your problem.

WinSock return code 10013 indicates a "permission denied" error when trying to access a socket.  

This sounds to me like a firewall issue.  In addition to making sure Windows Firewall is disabled, check to make sure that there is no other personal firewall software (McAfee, Norton, etc.) running on the machine that might be getting in the way.  

Sudden communications funkiness can also be a sign of malware infection.  I like to pull the drive and drop it into an external drive  enclosure and scan it from an up-to-date known-clean system using the AV  program of your choice, plus Spybot Search&Destroy.  This helps if the system has a rootkit installed or other malware that can cloak itself from AV one it is up and running.

Of course, verify your host address, and your network settings and make sure they match the other workstations at this location.  

Sometimes this can be a hardware firewall or VPN endpoint setup issue, too.  One way to test that is to steal the IP address of a working system temporarily and see if changing the problem workstation's address fixes the problem.  Remember to power off the workstation that you steal the address from, or disconnect it from the network.

How are workstations addressed at this location?  If they are addressed manually (or if there is a problem such as a rogue DHCP server on the network, you can see these sorts of problems with a duplicate MAC address or duplicate IP address.

Check the event log on the problem PC - if there is a local program that is interfering, it might be polite enough to expose itself by logging a message.  Or not - but it can't hurt to look.

One other quick thought:  is it possible that this user is configured to use an SSL connection, but SSL isn't configured on the host (or configured to use a non-SSL connection when only SSL is open)?

Run a regular PING, TRACERT, plus the CWBPING command that Tom suggests with the /ALL option.  Post the results back here if you need more help.

CWBPING 192.168.132.10 /all (specify username and password if required, and also use the /SSL:1 to test SSL connections if needed).

If all else fails, you might want to try removing and re-installing Client Access on this machine, making sure that you "Run As Administrator" when you launch the setup program, and disable any AV or firewall software during the install and initial testing.  Also make sure that you've applied the latest MS Vista OS patches and Client Access Service Pack for your version.

- Gary Patterson


Author

Commented:
Thanks for all of your suggestions. Here's what I got back from the cwbping:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Bob>CWBPING 192.168.132.10 /all

IBM iSeries Access for Windows
Version 5  Release 4  Level 0
Connection Verification Program
(C) Copyright IBM Corporation and Others 1984, 2005.  All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
  restricted by GSA ADP Schedule Contract with IBM Corp.
Licensed Materials - Property of IBM

To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
I - Verifying connection to system 192.168.132.10...
I - Successfully connected to server application: Central Client
I - Successfully connected to server application: Network File
I - Successfully connected to server application: Network Print
I - Successfully connected to server application: Data Access
I - Successfully connected to server application: ODBC
I - Successfully connected to server application: Data Queues
I - Successfully connected to server application: Remote Command
I - Successfully connected to server application: Security
I - Successfully connected to server application: DDM
E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The iSeries server application (MAPI) is not started
E - CWBCO1008 - Unable to connect to server application MAPI, returned 10061

E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application USF, returned 8407

I - Successfully connected to server application: Web Administration
I - Successfully connected to server application: Telnet
I - Successfully connected to server application: Management Central
I - Successfully connected to server application: Service Tools
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Operations Console, retu
rned 8407

E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Linux Console, returned
8407

E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The iSeries server application (XDA) is not started
E - CWBCO1008 - Unable to connect to server application XDA, returned 10061

W - CWBCO1015 - Connection verified to system 192.168.132.10, but there were war
nings


C:\Users\Bob>

Author

Commented:
By the way, i did start the iseries access for windows remote command service. still got the same error.

thanks again

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial