RE: Problemette CWBCO1047

I get this when I just tried CWBPING


To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
I - Verifying connection to system  
I - Successfully connected to server application: Central Client
I - Successfully connected to server application: Network File
E - CWBCO1003 - Winsock error, function recv() returned 8405
E - CWBCO1047 - The AS/400 server application (Network Print) disconnected the c
onnection
E - CWBCO1008 - Unable to connect to server application Network Print, returned
8405

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: Telnet
E - CWBCO1003 - Winsock error, function connect() returned 10061
E - CWBCO1049 - The AS/400 server application (Management Central) is not starte
d
E - CWBCO1008 - Unable to connect to server application Management Central, retu
rned 10061

W - CWBCO1015 - Connection verified to system 3.52.104.44, but there were warnin
gs

C:\Documents and Settings\500817021>

I tried to start Management Central from the Ops Navigator on Friday but was 
told that the Administrator had disabled that. 

Steve


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Bryan Dietz
Sent: Monday, July 12, 2004 2:24 PM
To: Midrange Systems Technical Discussion
Subject: Re: Problemette CWBCO1047






I like to use this list to read about the errors:
http://www-1.ibm.com/servers/eserver/iseries/linux/odbc/guide/cwbcoer.htm


CWBCO1047 [Contents]
Cause
The connection was initially established, but was disconnected by the
server or server application before communications were completed.
Recovery
Try the operation again. If the problem persists, have your systems
administrator check the server to verify that TCP/IP and the host servers
are running, and your connection is not restricted by an IP filter. See How
to Start OS/400 Host Socket Servers.
Have your system administrator check the server application job logs and
server subystems. See message CWBCO1003 for the names of the server jobs
and the default names of the subsystems.
This can also result from incorrectly configured routing on the server when
multiple routes to and from the server are possible. The result in this
case is that packets sent to the server are discarded because they are too
large. When this happens, TCP/IP on the PC assumes that the connection has
been ended by the server since it is not responding to the packets sent
from the PC, and reports error 10054 or 8405. Have your systems
administrator analyze the configuration of TCP/IP and associated routing,
as well as the maximum frame size configured for each TCP/IP interface that
may be reachable from the PC, and correct any inconsistencies or problems
with the configuration, then try the operation again.


What happens if the users having problems run this command from the DOS
prompt   CWBPING <insert ip address here>??


----------------------------
Bryan Dietz
Aktion Associates

midrange-l-bounces@xxxxxxxxxxxx wrote on 07/12/2004 06:36:19 AM:

-> Hello All,
->
-> My first post here tho' I have been lurking for a while. I have to
-> "Fess up" that I am not up-to date with the current stuff, I did a
-> lot of this on the S/38 but have spent the intervening years just
-> freelance programming, and so as the adage goes, "use it or lose
-> it" and I have lost it many years ago  :-).
->
-> Anyways up, the reason for this post. I have a problem that
-> recently the AS400 has been rejecting sign on attempts to some
-> users, when I come in I find that there are a number of users on,
-> dumb terminals as well as PC's, but a crowd of rabid users who
-> cannot get on, when I try myself I get a message CWBCO1047. I have
-> no idea why this is happening, there doesn't seem to be a specific
-> number of users that it will allow on nor a specific day. This
-> happened last week and then seemed to cure itself, prior to that it
-> was some weeks ago, now it happened this morning. A re-boot cures
-> the problem, as it showed no signs of curing itself today.
->
-> Help!
->
-> Steve
->

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.