Try doing a "CWBPING" from the Windows command prompt.
You'll see something like this:
C:\>cwbping SYSNAME
IBM i Access for Windows
Version 7 Release 1 Level 0
Connection Verification Program
(C) Copyright IBM Corporation and Others 1984, 2010. 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 SYSNAME...
E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The IBM i server application (Central Client) is not
started, or
the connection was blocked by a firewall
E - CWBCO1008 - Unable to connect to server application Central Client,
returned
10061
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: 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 IBM i server application (Telnet) is not started, or
the con
nection was blocked by a firewall
E - CWBCO1008 - Unable to connect to server application Telnet, returned
10061
W - CWBCO1015 - Connection verified to system SYSNAME, but there were
warnings
Anything with an E is most likely either not running on your system or
being blocked by a firewall.
====================================================================
These are the ports needed for the various Client Access functions:
PC Function Server Name Port Non-SSL Port SSL
Server Mapper as-svrmap 449 449
License Management as-central 8470 9470
Database Access as-database 8471 9471
Data Queues as-dtaq 8472 9472
Network Drives as-file 8473 9473
Network Printers as-netprt 8474 9474
Remote Command as-rmtcmd 8475 9475
Signon Verification as-signon 8476 9476
Telnet (PC5250 Emulation) telnet 23 992
HTTP Administration as-admi > 2001 2010
POP3 (MAPI) pop3 5010 ---
Management Central as-mgtc > 5555 and 5544 5566
Ultimedia Services as-usf 8480 9480
DRDA DRDA 446 ---
DDM DDM 447 448
IBM AnyNet APPCoverTCPIP 397 (TCP and UDP) ---
NetServer netbios > 137 ---
NetServer CIFS 445 ---
NetServer netbios > 139 ---
Service Tools Server as-sts 3000 ---
RUNRMTCMD REXEC 512 ---
Apologies for the formatting...
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
-----Original Message-----
From: Jerry C. Adams [mailto:midrange@xxxxxxxx]
Sent: Monday, March 05, 2012 2:23 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect
I saw the first two links, too.
There is a firewall (AVG) running, but the system admin gets rather,
shall we say, irked if I even look at his settings, and he ain't
available right now. On the other hand, the remote site (store) could
connect last Friday.
I was able to connect via telnet from a DOS command window.
I ran the History Log. In addition to CWBCO1003, it showed CWBCO1011
(Remote port could not be resolved). It said something about using
iSeries Navigator to check the port, which I did, but I saw nothing in
the 'Connection' tab about a bloody port (still could be the one "good"
eye is going bad).
I guess I'll get with the admin tomorrow (too late in the day to hassle
with
him) about AVG and other possibilities. Though, theoretically, he's
told me that all of the PCs are set-up the same way.
Jerry C. Adams
IBM i Programmer/Analyst
You can never plan the future by the past. -Edmund Burke
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, March 05, 2012 12:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Remote Site Cannot Connect
My first google hit was
http://www-03.ibm.com/systems/i/software/access/linux/guide/cwbcoer.html
I looked at CWBCO1003 and 4 (3 suggests that also). With the reference
code you've given, it suggests that you do what you did: ping, etc.
Googling on both the CWBCO1003 (notice one letter o and two number
zeros?).
and 10013 also shows this
http://www-01.ibm.com/support/docview.wss?uid=nas168a2f7d1eed4f633862579
8a00
5de2c8
possible firewall issue? See also
http://www-01.ibm.com/support/docview.wss?uid=nas1acc12fda96496e4b862566
8f00
7ab75f
Try using telnet from DOS and see if that gets there?
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Jerry C. Adams" <midrange@xxxxxxxx>
To: "Midrange-L" <midrange-l@xxxxxxxxxxxx>,
Date: 03/05/2012 01:42 PM
Subject: Remote Site Cannot Connect
Sent by: midrange-l-bounces@xxxxxxxxxxxx
This is only occurring at one remote location. When they double-click
the
desktop icon (iSeries Access for Windows - PC5250), they get a "PC5250
License Error: CWBCO1003 - Sockets error, function returned 10013 (with
our
IP address)".
I couldn't find anything regarding this function code in the Archives,
Google, or the "Details" box of the error message.
I can take over the site's PC, which I did.
I ran Ping on the remote PC (which, by the by, is running XP Pro at
SP3).
It hit our iSeries box.
I ran cwbping. All services, most notably Telnet, connected fine.
I tried configuring a new session. Same error.
Oddly enough (to me, anyway) the Data Transfer icon works fine.
Uh, I'm stumped.
Jerry C. Adams
IBM i Programmer/Analyst
Toleration is good for all, or it is good for none. -Edmund Burke
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
midrange.com
