Jabber registration issue on CCM 7.1.5

Hi Guys, I'd like to ask your valuable advice on the following:
- we're running CCM 7.1.5(b)SU5
- we installed the following .cop files for Android support (we tried one after the other hoping to get around the problem):
     cmterm-android_8.6.2v17.cop.sgn
     cmterm-android_8.6.2v17b.cop.sgn
     cmterm-android_9.0.1v24.cop.sgn
- we forced the phone (Samsung Galaxy S GTi9000) to install the following Jabber client (found on CCO together with the above device files for which it should be compatible):
     Release 8.6(5) - Optimus-MR3-aligned.apk
Unfortunately we had no luck and the phone gets always the 'timeout/check network config' error.
This is what you see on CCM side:
12/07/2012 10:51:44.332 CCM|SIPStationD(7,100,169,47), BOTTEST, 10.40.251.125:40916, primaryDN=5011, Registration profile error: Error: DB Config, sending registration reject and closing station|<CLID::CCMSG-Cluster><NID::10.40.11.23><CT::0,0,0,0.0><IP::><DEV::><LVL::Error><MASK::0020>
... we followed all the Cisco guidelines to create a suitable device configuration (the same worked like a charm on CCM 8.5).
I'll attach a CCM trace showing the above error (as you may have guesses, the phone name is 'BOTTEST')
Thanks a lot !
- Andrea

I've been having a real fun time trying to get Jabber for Android working as well.  CUCM version 8.6.2 and Jabber 9.0.
The trick was to check the box for 'Use Fully Qualified Domain Name in SIP Requests' in the SIP profile you created for Android phones.
I was connecting to the CUCM, but then it would time out.
Thanks,
Richard

Similar Messages

  • Jabber for Windows Registration Issue

    I have been facing issue with J4W registration and display error "no connection to server". Following is the version detail:-
    Version CUCM and IM&P---> (10.5.2)
    On-Premises login
    During analysis, i found 2 things in logs:-
    1). Unable to download jabber-config.xml file (Download of TFTP File failed for server ) //// all the other xml files are succesfully downloaded which may indicate that there is an absence of jabber-config.xml file.
    2). While signing into presence "OnLoginError: (data=0) LERR_JABBER_UNREACHABLE <16>: "
    [rc\cert\common\BaseCertVerifier.cpp(250)] [csf.cert.] [cert::BaseCertVerifier::checkIdentity] - About to verify the Subject Alt Name.
    [ls\src\cert\common\CertVerifier.cpp(154)] [csf.cert] [cert::CertVerifier::checkIdentifier] - Verifying identity '162.20.10.30'       
    [rc\cert\utils\AltNameParserImpl.cpp(349)] [csf.cert.utils] [cert::AltNameParserImpl::verify] - Looking for match with 162.20.10.30   
    [rc\cert\utils\AltNameParserImpl.cpp(400)] [csf.cert.utils] [cert::AltNameParserImpl::verify] - No Match Found    
    I tried to change the IP address to FQDN under System---> Server, but after that the connection is lost between CUCM and IM&P.
    Attached is the log file and snapshot of IM&P.
    - See more at: https://supportforums.cisco.com/discussion/12490406/jabber-windows-registration-issue#sthash.E2wXb4iJ.dpuf

    Nishant,
    Sorry for the late reply. You may well have resolved this  by now, if you have can I suggest that you update the post with the resolution so others may benefit.
    Looking at the logs, I can see that Jabber is trying to login to the IMP server below, but its returning server unreachable error.
    Signing into Presence Server. Server: 162.20.10.30, login mode: ON_PREM, result: 0
    [IMPStackCap::Login::OnLoginError] - ****************************************************************
    [IMPStackCap::Login::OnLoginError] - OnLoginError: (data=0) LERR_JABBER_UNREACHABLE <16>:
    [IMPStackCap::Login::OnLoginError] - ****************************************************************
    We will need to look at the IMP logs to know what is going on. Let me know if you still need help with this.

  • Regarding passport registration issues, I need to have a letter from you including both the old and new imei numbers. Could you please send me an email mentioning that I have changed the phones with the given imei numbers?

    Regarding passport registration issues, I need to have a letter from you including both the old and new imei numbers. Could you please send me an email mentioning that I have changed the phones with the given imei numbers?

    You're not addressing Apple here. This is a user-to-user technical support forum. If you want to contact Apple, use the Contact Us link at the bottom right of every page for information on how to do so.
    Best of luck.

  • Jabber voicemail issue

    When we click on the voicemail icon within Jabber, we get "You are not signed in to your voicemail account. Go to the phone accounts tab..."
    When I go to File>Options>phone accounts and and enter my AD credentials for username and password, it says the username or password is not correct.
    Am I entering the correct info for the username and password? Everything is sync'd with LDAP.
    Thank you.

    This may not be your case, but I had this same exact issue last week and it was because the Server Admin had changed the password to the account we used as the CN in our LDAP authentication. Once I updated the password in CUC, the problem was resolved. So, doesn't hurt to ensure the credentials are still good.

  • EBS Registration issue

    Hi All,
    We have done the sso registration successfully , but sso login functionality is not working as expected.
    Please provide some inputs to fix this issue.
    Environment
    We are on 11gR2 database for both OID and EBS 11.5.10.2.
    OID version 11g on web logic server.
    SSO server version is 10.1.4.3
    In the front end it is showing the below error while login using the SSO URL.
    "The Single Sign-On server registration is invalid. Please contact the System Administrator. "
    When we run the below query in the backend (EBS R11 DB) it suppose to get the records without any error or it is suppose to show just “no rows selected”, but I got the “ORA-29275” error in the backend
    Query: select FROM FND_USER_PREFERENCES WHERE USER_NAME = '#INTERNAL'*
    and I ran the FND Log Query, found these messages..."END with errors for getSSOVerion"
    Query--> select * from fnd_log_messages where module like '%fnd.sso.FNDSSOLoginRedirect%' order by timestamp desc;
    out put:
    MODULE,LOG_LEVEL,MESSAGE_TEXT,SESSION_ID,USER_ID,TIMESTAMP,LOG_SEQUENCE,ENCODED,NODE,NODE_IP_ADDRESS,PROCESS_ID,JVM_ID,THREAD_ID,AUDSID,DB_INSTANCE,TRANSACTION_CONTEXT_ID
    fnd.sso.FNDSSOLoginRedirect,6,END with errors for getSSOVerion,-1,-1,7/7/2011 5:39:36 PM,16151017,N,agsos186,155.108.22.210,5161,8230:16210,Thread[Thread-17669,10,main],46984138,1,3762242
    I have run the below mentioned steps to register the sso with EBS R11.
    Registration Steps
    txkrun.pl -script=SetSSOReg -registersso=Yes
    txkrun.pl -script=SetSSOReg -registeroid=Yes -provtmp=$FND_TOP/admin/template/ProvBiDiNoCreation.tmp (Here basically I don’t want provision/create the users by default in EBS or OID). Even I tried default option its not working ( by default it provision /create in both places EBS and OID)
    LOG
    Oxxx(APPS2)$txkrun.pl -script=SetSSOReg -registersso=Yes
    Enter the host name where Oracle iAS Infrastructure database is installed ? xxxxxxxxx2.com
    Enter the Oracle iAS Infrastructure database port number ? 1510
    Enter the Oracle iAS Infrastructure database SID ? xxx2eee
    Enter Oracle E-Business apps database user password ? xxxxxxx
    Enter Oracle iAS Infrastructure database ORASSO schema password ? xxxxxx
    Enter Oracle E-Business SYSTEM database user password ? xxxxxxx
    Enter E-Business Suite existing SSOSDK schema password or choose a password to use with the new SSOSDK schema if the schema does not exist ? ssosdk
    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS
    *** Log File = /aifsd03/ifs/applmgr/xxxxcomn/rgf/xxxxxxxx_agsosxxx/sso/txkSetSSOReg_Fri_Jul_1_13_52_00_2011.log
    Program : /aifsd03/ifs/applmgr/Oxxx/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Fri Jul 1 13:52:18 2011
    *** Log File = /aifsd03/ifs/applmgr/xxxxxxxppl/rgf/xxxxxxxppl_agsos/sso/txkSetSSOReg_Fri_Jul_1_13_52_00_2011.log
    ######################## WARNING ########################################
    This application works with SSOSDK version 9.0.2 or higher. If lower version
    (3.0.9) of SSOSDK was installed in your system and you have a registered
    partner application, this process will remove the 3.0.9 version of the SSOSDK
    schema and install the 9.0.2 version.
    ######################## WARNING ########################################
    Beginning input parameter validation for SSO registration.
    Beginning loading SSO SDK into database if necessary.
    Loading of SSO SDK into database completed successfully.
    Input parameter validation for SSO registration completed.
    BEGIN SSO REGISTRATION:
    Beginning to register partner application.
    Partner application has been registered successfully.
    Single Sign-On partner application registered successfully.
    End of /aifsd03/ifs/applmgr/xxxxxxxppl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered
    Oxxx(APPS2)$txkrun.pl -script=SetSSOReg -registeroid=Yes-provtmp=$FND_TOP/admin/template/ProvBiDiNoCreation.tmp
    Enter the host name where Oracle iAS Infrastructure database is installed ? XXXXXXXXXXXXX2.com
    Enter the LDAP Port on Oracle Internet Directory server ? 3010
    Enter Oracle E-Business apps database user password ? XXXXX
    Enter the Oracle Internet Directory Administrator (orcladmin) Bind password ? XXXXX
    Enter the instance password that you would like to register this application instance with ? XXXXXX
    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS
    *** Log File = /aifsd03/ifs/applmgr/xxxxxxx0comn/rgf/xxxxxxxxx_agsosxxx/sso/txkSetSSOReg_Fri_Jul_1_13_58_14_2011.log
    Program : /aifsd03/ifs/applmgr/xxxxxxxppl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Fri Jul 1 13:59:50 2011
    *** Log File = /aifsd03/ifs/applmgr/xxxxxxxppl/rgf/xxxxxxxppl_agsosxxx/sso/txkSetSSOReg_Fri_Jul_1_13_58_14_2011.log
    Beginning input parameter validation for OID registration.
    Input parameters validation for OID registration completed.
    BEGIN OID REGISTRATION:
    Beginning to register Application and Service containers if necessary.
    Application and Service containers were found and thus not created.
    Beginning to register application in Oracle Internet Directory.
    Registration of application in Oracle Internet Directory completed successfully.
    Beginning to register instance password in Oracle Internet Directory.
    Registration of instance password in Oracle Internet Directory completed successfully.
    Beginning to test application registration in Oracle Internet Directory.
    Testing of application registration in Oracle Internet Directory completed successfully.
    Beginning to register provisioning profile in Oracle Internet Directory.
    Registration of provisioning profile in Oracle Internet Directory completed successfully.
    Application is now registered successfully with provisioning in Oracle Internet Directory.
    End of /aifsd03/ifs/applmgr/xxxxxxxppl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered
    Edited by: reddy1198 on Jul 8, 2011 2:36 PM

    Please see if (The Single Sign-On server registration is invalid [ID 434752.1]) helps.
    Thanks,
    Hussein

  • Jabber Video Issue on Mac

    I am running Jabber Video 4.6 (17194) and OS X 10.9.4.  When I installed the Jabber software, it would not recognize the built-in camera or my Tandburg HD Camera.  I have a meeting with a Client on Wednesday and this is the way that they are requesting that we communicate.  I need to figure out what is the issue.  
    I can get both cameras to work with Face Time.  I also have the following collboration tools loaded that do not have an issue with the cameras:
    Lync for Mac 2011 v14.0.9 (140606)
    Cisco Jabber v9.6.0 (173114)
    Assistance would be most welcome.
    Mike

    Hi Mike,
    It is a known issue. It is a Bug in version 4.6.
    You need to upgrade to version 4.7 or higher, just be aware that the user will be prompted to downgrade when signing in because Cisco is currently only provisioning version 4.6.3. The user should decline that :-)
    http://software.cisco.com/download/release.html?mdfid=283613653&softwareid=280886992&release=4.8.6.18185&relind=AVAILABLE&rellifecycle=&reltype=latest
    Thomas

  • Jabber login issue&uploading pic

    I am facing issue on logging jabber into iphone
    Status always shows verify
    what could be the problem can any body suggest me?
    How to set a photo in jabber client?

    I  was able to make this work, and it was a huge PITA.  You have to modify the XML files that Jabber uses for its configuration.  You then have to have a web server that holds all your images.  Jabber downloads them from the web server.

  • Jabber audio issue

    Ok so I'm a new iMac user and until I got it, I always used the Google Talk since it has the option of talking through a mic with the people who are on my buddy list. Since I was unable to download Google Talk to my iMac, I registered my google email account to the iChat which I guess now logs me through Jabber when I'm talking to my friends who are still on Google Talk. The problem I'm having is while I'm on Jabber and iMac, they're using Windows and Google Talk so I'm not having any luck connecting via Audio Chat with them. I select their name on the Jabber list and attempt to click on "Invite to Audio Chat", that option is grayed out and I'm unable to connect with them via mic. I double checked all the options on my iChat about the audio connection and everything seams right. Am I doing something wrong?

    My Understanding is that iChat can Video and Audio only chat to another iChat users with a Jabber ID (including a Google one)
    The issue is then that this uses the protocols for a A/V chat.
    These are the same as the AIM Buddy List uses and not the one Jabber or in fact Google uses on their applications on a PC.
    Therefore you will not e able to Audio chat to a PC user via the Jabber Buddy list in iChat.
    9:38 PM Monday; April 28, 2008

  • Jabber login issue

    Hi 
    I have recently deploy expressway edge 8.1.1 with cucm 9.1.2 and cups 9.1.1.However,when I  try to login via internet using jabber 9.7.2,it return error "username or password wrong".From the log in expressway-core,I can see the log below
    (192.168.121.32 is the ip add of my cucm ,username is zhangzr)
    2014-06-19T22:08:08+08:00 EXPC edgeconfigprovisioning UTCTime="2014-06-19 14:08:08,603" Module="network.http.edgeconfigprovisioning" Level="DEBUG" Action="Received" Request-url="https://192.168.121.32:8443/cucm-uds/clusterUser?username=zhangzr" 
    HTTPMSG:
    |HTTP/1.1 200 OK
     Date: Thu, 19 Jun 2014 14:08:08 GMT
     X-Frame-Options: SAMEORIGIN
     Content-Type: application/xml
     Server: 
     <?xml version="1.0" encoding="UTF-8" standalone="yes"?><clusterUser uri="https://192.168.121.32:8443/cucm-uds/clusterUser?username=zhangzr" version="9.1.2"><result version="9.1.2" uri="https://192.168.121.32:8443/cucm-uds/user/zhangzr" found="true"/><homeCluster>192.168.121.32</homeCluster></clusterUser>
     |
    2014-06-19T22:08:08+08:00 EXPC edgeconfigprovisioning UTCTime="2014-06-19 14:08:08,604" Module="network.http.edgeconfigprovisioning" Level="DEBUG" Action="Send" Url="https://192.168.121.32:8443/cucm-uds/user/zhangzr/devices" 
    HTTPMSG:
    |GET //192.168.121.32:8443/cucm-uds/user/zhangzr/devices HTTP/1.1
     Authorization: <CONCEALED>
     |
    2014-06-19T22:08:08+08:00 EXPC ssh: Event="sshd" Module="openssh" Level="INFO"  Detail="Allocated port 34882 for remote forward to localhost:8443" UTCTime="2014-06-19 14:08:08"
    2014-06-19T22:08:08+08:00 EXPC ssh: Event="sshd" Module="openssh" Level="INFO"  Detail="RSA+cert host key for IP address '192.168.121.31' not in list of known hosts." UTCTime="2014-06-19 14:08:08"
    2014-06-19T22:08:08+08:00 EXPC ssh: Event="sshd" Module="openssh" Level="INFO"  Detail="Authenticated to expe.gdhwater.com ([192.168.121.31]:2222)." UTCTime="2014-06-19 14:08:08"
    2014-06-19T22:08:08+08:00 EXPC edgeconfigprovisioning UTCTime="2014-06-19 14:08:08,872" Module="network.http.edgeconfigprovisioning" Level="DEBUG" Action="Received" Request-url="https://192.168.121.32:8443/cucm-uds/user/zhangzr/devices" 
    HTTPMSG:
    |HTTP/1.1 403 Forbidden
     Set-Cookie: JSESSIONIDSSO=A2FB5364EB77D11136697ABAC436EE78; Path=/; Secure; HttpOnly
     Set-Cookie: JSESSIONID=588E4DCBE1165A82680BFF3BDD6A865B; Path=/cucm-uds/; Secure; HttpOnly
     Expires: Thu, 01 Jan 1970 07:00:00 CST
     Server: 
     Cache-Control: private
     Date: Thu, 19 Jun 2014 14:08:08 GMT
     Content-Type: text/html;charset=utf-8
     <!-- custom Cisco error page --><html>    <head>        <title>            Cisco System - Error report        </title>        <style type="text/css">            a {                color: #316984;                text-decoration: none;            }            a:hover {                color: #316984;                text-decoration: underline;            }            a:visted {                color: #316984;                text-decoration: none;            }            body {                background-attachment: fixed;                background-color: #ffffff;                background-repeat: no-repeat;                color: #316984;                font-family: arial,helvetica,sans-serif;            }            #content {                border: 1px solid #d6d7d6;                font-size: 93.5%;                margin: 0px 10% 30px 10%;            }            #content-header {                background-color: #eeeeee;                b
    order-bottom: 1px solid #666666;                color: #666666;                font-size: 124.5%;                padding: 5px 15px 5px 15px;            }            #copyright {                font-size: 75%;                margin: 0px 10% 0px 10%;                padding: 3px 0px 0px 0px;                text-align: right;            }            img {                display: block;                margin: 0px 0px 20px 0px;            }            #logo {                margin: 30px 10% 0px 10%;            }            p {                padding: 5px 15px 5px 15px;            }            pre {                padding: 5px 15px 5px 30px;            }        </style>    </head>    <body>        <div id="logo">            <img src="/ciscologo.gif" alt="Cisco Systems, Inc." />        </div>        <div id="content">            <div id="content-header">HTTP Status 403 - Access to the requested resource has been denied            </div>            <p>                <b>                    type:               </b> Status report            </p>            <p>                <b>message:               </b> Access to the requested resource has been denied            </p>            <p>                <b>description:               </b> Access to the specified resource has been forbidden.            </p>        </div>    </body></html>
     |2014-06-19T22:08:08+08:00 EXPC edgeconfigprovisioning: Level="INFO" Detail="Failed to authenticate user against server" Username="zhangzr" Server="('https', '192.168.121.32', 8443)" Reason="<twisted.python.failure.Failure <type 'exceptions.Exception'>>" UTCTime="2014-06-19 14:08:08,874"
    2014-06-19T22:08:08+08:00 EXPC edgeconfigprovisioning: Level="INFO" Detail="All attempts to authenticate user failed" Username="zhangzr" UTCTime="2014-06-19 14:08:08,875"
    Anyone can see what is the problem from the log? Should we upload  a jabber-config.xml for remote-access  to cucm so that we can authenticate ?Or is there any other reason causing such problem?

    Hi,
    I have exactly the same issue running exactly the same CUCM and CUPS versions.
    I am running Expressway 8.2 and Jabber Client 9.7.4.
    My log files show the same as yours, but I don't see any incorrect username or password statements.
    Internally the clients work fine, externally they seem to parse both Expressway servers and returning the cups and cucm internally addresses in the log files. And then the clients responds with "Cannot communicate with the server". Logging stops.
    Anyone got any pointers?

  • Jabber Softphone issue

    I'm hoping someone can help me here.
    I am deploying Jabber to our 1000+ user org and there are a handful of users that have the need for Jabber softphones. I am able to setup the CSF devices just fine and the users don't have any errors when they choose to control their computer for control.
    The issue is when the user is connected via VPN (AnyConnect), the calls placed to them do not go to their jabber client. It only rings their deskphone.  They can place calls (internal and external) just fine, but cannot receive them.
    Ideas?

    So, Jabber doesn't even ring??
    Or do you have 1-way/no audio??
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • Portal Self registration issue

    Hi guys,
    I had activated Portal self registration with companies feature. what i did is ,  i assigned one role (ess portal role in which all my ess screens are covered) to authenticated group and  every_user_core_role to anonymous group and did necessary configuration in configtool . The problem i am facing is that my self registered users are able to see my portal role without any approval (via approve/ deny in user administration) which i want to show them after approval . PLs guide what might me the issue.
    Regards,
    Shwetang Saxena.

    Hello Soni!
    Please review and follow the steps mentioned here:
    Companies and Self-Registration with Approval (SAP Library - User Management of the Application Server Java)
    https://cw.sdn.sap.com/cw/docs/DOC-110636
    Hope this helps,
    Edison

  • Registration issues....  Solaris 10 - 06/06

    Having issues registering my V440 running Solaris 10 06/06. I have posted the error below and them some system information below that. any help is appreciated.
    sysax /: /usr/sbin/sconadm register -a -r /usr/lib/breg/data/RegistrationProfile.properties
    sconadm is running
    Authenticating user ...
    Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
    at $Proxy1.getInstanceName(Unknown Source)
    at com.sun.scn.client.SCNClientSession.login(SCNClientSession.java:371)
    at com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter.loginAccount(ClientLoginCacaoAdapter.java:209)
    at com.sun.cns.basicreg.BasicRegCLI.authenticateUser(BasicRegCLI.java:1079)
    at com.sun.cns.basicreg.BasicRegCLI.run(BasicRegCLI.java:669)
    at com.sun.cns.basicreg.BasicRegCLI.main(BasicRegCLI.java:562)
    Caused by: javax.management.InstanceNotFoundException: com.sun.scn:name=SCNBaseServiceFactory,assetSubProfile=Factory,host=sysax.consolidated.com,assetProfile=Factory,scnType=ServiceFactory,Vendor=Sun Microsystems Inc
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getClassLoaderFor(DefaultMBeanServerInterceptor.java:1349)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.getClassLoaderFor(JmxMBeanServer.java:1300)
    at com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.getClassLoaderFor(DefaultMBeanServerInterceptor.java:285)
    at com.sun.cacao.agent.DispatchInterceptor.getClassLoaderFor(DispatchInterceptor.java:474)
    at com.sun.cacao.agent.auth.impl.AccessControlInterceptor.getClassLoaderFor(AccessControlInterceptor.java:427)
    at com.sun.jdmk.JdmkMBeanServerImpl.getClassLoaderFor(JdmkMBeanServerImpl.java:1130)
    at com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.getClassLoaderFor(InstrumDefaultForwarder.java:153)
    at javax.management.remote.rmi.RMIConnectionImpl$4.run(RMIConnectionImpl.java:1306)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.management.remote.rmi.RMIConnectionImpl.getClassLoaderFor(RMIConnectionImpl.java:1303)
    at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:766)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
    at sun.rmi.transport.Transport$1.run(Transport.java:153)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
    at java.lang.Thread.run(Thread.java:595)
    at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
    at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
    at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
    at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source)
    at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:969)
    at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
    ... 6 more
    sysax /: cat /etc/release
    Solaris 10 6/06 s10s_u2wos_09a SPARC
    Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 09 June 2006
    sysax /: cat /var/sadm/system/admin/CLUSTER
    CLUSTER=SUNWCall
    sysax /: java -version
    java version "1.5.0_06"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
    Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
    sysax /: smpatch get
    patchpro.backout.directory - ""
    patchpro.baseline.directory - /var/sadm/spool
    patchpro.download.directory - /var/sadm/spool
    patchpro.install.types - rebootafter:reconfigafter:standard
    patchpro.patch.source - https://getupdates1.sun.com/
    patchpro.patchset - current
    patchpro.proxy.host - ""
    patchpro.proxy.passwd **** ****
    patchpro.proxy.port - 8080
    patchpro.proxy.user - ""
    sysax /: cat /usr/lib/breg/data/RegistrationProfile.properties
    # CLI registration profile template version 1.0
    # ******** WARNING ********
    # This profile contains sensitive data: passwords and subscription
    # keys. You should take care in how you handle it, ensuring that it
    # is always adequately protected (mode 400 or 600, owned by root)
    # and not stored on insecure file systems like those exported through
    # standard NFS.
    # Sun Online account information. A new account can be created by visiting
    # http://updates.sun.com
    userName=**************
    password=***********
    # Name (label) of this machine as you would like it to appear on the Sun Connection
    # portal. If left blank hostname will be used
    hostName=devdbs01
    # Service Plan / contract number with Sun. For more information on this topic
    # please visit http://www.sun.com/service/warrantiescontracts/ . NOTE - a
    # subscription key is required to use the Sun Connection Portal.
    subscriptionKey=***************
    # Allow this host to be managed by the Sun Connection Portal. If set to true,
    # a subscription key is required.
    portalEnabled=true
    # HTTPS proxy information needed to connect to Sun for registration and patch
    # updates.
    proxyHostName=
    proxyPort=
    proxyUserName=
    proxyPassword=

    The error message I received was from the Sun Update Connection GUI. Once the patches I attempted to apply failed.
    sysax /tmp: ./suc.sh.2
    $USER:
    $LOGNAME: root
    Sat Feb 24 13:37:07 CST 2007
    sysax
    smpatch get:
    patchpro.backout.directory - ""
    patchpro.baseline.directory - /var/sadm/spool
    patchpro.download.directory - /var/sadm/spool
    patchpro.install.types - rebootafter:reconfigafter:standard
    patchpro.patch.source - https://getupdates1.sun.com/
    patchpro.patchset - current
    patchpro.proxy.host - ""
    patchpro.proxy.passwd **** ****
    patchpro.proxy.port - 8080
    patchpro.proxy.user - ""
    smpatch analyze:
    119252-15 SunOS 5.10: System Administration Applications Patch
    119081-25 SunOS 5.10: CD-ROM Install Boot Image Patch
    124630-03 SunOS 5.10: System Administration Applications, Network and Core Libraries Patch
    124188-02 SunOS 5.10: Trusted Solaris Attributes Patch
    119315-07 SunOS 5.10: Solaris Management Applications Patch
    121308-08 SunOS 5.10: Solaris Management Console Patch
    119313-10 SunOS 5.10: WBEM Patch
    119534-10 SunOS 5.10: Flash Archive Patch
    119254-34 SunOS 5.10: Install and Patch Utilities Patch
    119963-08 SunOS 5.10: Shared library patch for C++
    120753-03 SunOS 5.10: Microtasking libraries (libmtsk) patch
    123494-03 X11 6.6.2: fontconfig patch
    119812-02 X11 6.6.2: Freetype patch
    125014-02 SunOS 5.10: IP filter patch
    120780-03 SunOS 5.10: ixgb patch
    119764-05 SunOS 5.10 : ipmitool patch
    124258-01 SunOS 5.10: ufs and nfs driver patch
    124252-01 SunOS 5.10: nfssrv patch
    120812-15 OpenGL 1.5: OpenGL Patch for Solaris
    123839-04 SunOS 5.10: Fault Manager Patch
    124204-04 SunOS 5.10: zfs patch
    122911-02 SunOS 5.10: Apache 1.3 Patch
    120543-08 SunOS 5.10: Apache 2 Patch
    117463-04 SunOS 5.10: passwdutil Patch
    118890-03 SunOS 5.10: llib-lc patch
    125024-01 SunOS 5.10: basic audit reporting tool patch
    123908-01 SunOS 5.10: ar patch
    120887-06 SunOS 5.10: cdrw patch
    119580-05 SunOS 5.10: libcpc Patch
    124244-01 SunOS 5.10: /usr/bin/rm patch
    119685-10 SunOS 5.10: svc.startd patch
    124997-01 SunOS 5.10: /usr/bin/tip patch
    121081-06 SunOS 5.10: Connected Customer Agents 1.1.0
    120845-04 SunOS 5.10: auditd patch
    124235-01 SunOS 5.10: libpam.so.1 patch
    120050-05 SunOS 5.10: usermod patch
    122525-03 SunOS 5.10: Sun Fire V445 patch
    124614-01 SunOS 5.10: sconadm proxy: UnknownHostException
    120986-10 SunOS 5.10: mkfs and newfs patch
    125040-01 SunOS 5.10: /usr/lib/inet/in.mpathd patch
    122517-03 SunOS 5.10: Sun Fire V215/V245 platmod patch
    125035-01 SunOS 5.10: libinetsvc.so.1 patch
    123334-04 SunOS 5.10: e1000g_transition patch
    122660-07 SunOS 5.10: zones patch
    119998-02 SunOS 5.10: arp, ip, ipsecah drivers patch
    125026-01 SunOS 5.10: message queue patch
    118371-08 SunOS 5.10: elfsign Patch
    123328-01 SunOS 5.10: expr patch
    123520-01 SunOS 5.10: basename & dirname patch
    123915-01 SunOS 5.10: libcfgadm.so.1 patch
    125018-02 SunOS 5.10: scsi_vhci driver patch
    123912-02 SunOS 5.10: ppriv patch
    118367-04 SunOS 5.10: csh Patch
    125016-01 SunOS 5.10: audit and init patch
    119824-02 SunOS 5.10: prstat patch
    123910-01 SunOS 5.10: platform_sun4v.xml patch
    122255-04 SunOS 5.10: etc/flash/precreation/caplib patch
    123319-01 SunOS 5.10: sysacct patch
    118557-07 SunOS 5.10: platform/sun4u/kernel/drv/sparcv9/su patch
    123271-01 SunOS 5.10: iwscn patch
    124922-02 SunOS 5.10: ld.so.1 patch
    123301-01 SunOS 5.10: i2c_svc patch
    124325-01 SunOS 5.10: rcm modules patch
    121561-04 SunOS 5.10: keymap patch
    124918-02 SunOS 5.10: devfsadm, devlinks, drvconfig patch
    122032-04 SunOS 5.10: Update timezones patch
    124916-03 SunOS 5.10: sd, ssd drivers patch
    121002-03 SunOS 5.10: pax patch
    123252-01 SunOS 5.10: platform/SUNW,Netra-T2000 patch
    122412-01 SunOS 5.10: ipseckey patch
    122408-01 SunOS 5.10: libmtmalloc patch
    120473-02 SunOS 5.10: nss_compat patch
    124254-02 SunOS 5.10: sockfs patch
    124250-03 SunOS 5.10: rpcmod patch
    122752-04 SunOS 5.10: FMA snmp patch
    124999-01 SunOS 5.10: mc-us3 driver patch
    125319-01 SunOS 5.10: rmc_comm patch
    125028-02 SunOS 5.10: pcipsy patch
    118879-02 SunOS 5.10: dhcp daemon patch
    118815-05 SunOS 5.10: awk nawk patch
    121286-04 SunOS 5.10: libfru.so.1 and libfrureg.so.1 patch
    122363-02 SunOS 5.10: fru_container.conf and libfruaccess.so.1 patch
    119974-07 SunOS 5.10: fp plug-in for cfgadm
    120222-15 SunOS 5.10: Emulex-Sun LightPulse Fibre Channel Adapter driver
    119130-33 SunOS 5.10: Sun Fibre Channel Device Drivers
    120182-05 SunOS 5.10: Sun Fibre Channel Host Bus Adapter Library
    120346-06 SunOS 5.10: Common Fibre Channel HBA API Library
    124943-01 SunOS 5.10: SunFreeware gzip man pages patch
    122675-01 SunOS 5.10 : SunFreeware samba man pages patch
    123809-01 SunOS 5.10: rpcsec_gss patch
    121239-02 SunOS 5.10: libgss patch
    120719-02 SunOS 5.10 : SunFreeware gzip patch
    118925-05 SunOS 5.10: unistd header file patch
    124208-01 SunOS 5.10: Trusted Extensions header files patch
    124280-01 SunOS 5.10: libkdb.so.1 patch
    120469-05 SunOS 5.10: kerberos patch
    121006-02 SunOS 5.10: libkadm5 and kadmind patch
    124991-01 SunOS 5.10: llc2 driver patch
    124286-01 SunOS 5.10: chkey core dump
    123186-02 SunOS 5.10: NIS yp utilities patch
    124987-01 SunOS 5.10: ldap_cachemgr patch
    119470-10 SunOS 5.10: Sun Enterprise Network Array firmware and utilities
    122404-01 SunOS 5.10: xntpd patch
    124990-01 SunOS 5.10: Sun-Blade-100 libprtdiag_psr.so.1 patch
    121944-02 SunOS 5.10: libpsvcpolicy and libpsvcpolicy_psr patch
    122537-02 SunOS 5.10: libpiclenvmon.so.1 patch
    123590-02 SunOS 5.10: PostgresSQL patch
    120629-05 SunOS 5.10: libpool patch
    124993-01 SunOS 5.10: in.ndpd patch
    125011-01 SunOS 5.10: sendmail patch
    125022-01 SunOS 5.10: usr/sbin/sar patch
    122376-01 SunOS 5.10: prex patch
    120068-03 SunOS 5.10: in.telnetd patch
    124995-01 SunOS 5.10: ehci driver patch
    121010-05 SunOS 5.10: rpc.metad patch
    124256-01 SunOS 5.10: md_mirror patch
    125075-01 SunOS 5.10: svc-volfs patch
    125073-01 SunOS 5.10: vold patch
    119555-04 SunOS 5.10: Software to support QLogic Ultra3 SCSI host bus adapters
    119090-22 SunOS 5.10: Sun iSCSI Device Driver and Utilities
    120272-06 SunOS 5.10: SMA patch
    124463-02 SunOS sparc : cacao 2.0 patch 02
    119213-11 NSS_NSPR_JSS 3.11.4: NSPR 4.6.4 / NSS 3.11.4 / JSS 4.2.4
    118666-11 J2SE 5.0: update 11 patch (5.0u11)
    118667-11 J2SE 5.0: update 11 patch (5.0u11), 64bit
    122119-05 SunOS 5.10: Patch for Arabic Fonts
    119703-08 SunOS 5.10: Patch for localeadm issues
    123003-02 SunOS 5.10: dependency issue with SUNWopenssl-include
    123630-01 SunOS 5.10: HTTP proxy settings patch
    123005-05 SunOS 5.10: Basic Registration Update
    123011-01 SunOS 5.10: BR desktop icon patch
    119648-03 SunOS 5.10: vlan driver patch
    118777-08 SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver patch
    121118-11 SunOS 5.10: Sun Update Connection System Client 1.0.9
    118712-13 SunOS 5.10: Sun XVR-100 Graphics Accelerator Patch
    120410-17 SunOS 5.10: Internet/Intranet Input Method Framework patch
    121734-05 SunOS 5.10: patch to support addition of new UTF-8 locales
    119810-03 SunOS 5.10: International Components for Unicode Patch
    120099-07 APOC 1.2: Sun Java(tm) Desktop System Configuration Shared Libraries
    119546-07 APOC 1.2: APOC Configuration Agent Patch
    124393-02 CDE 1.6: Dtlogin smf patch
    123611-02 X11 6.6.2: Trusted Extensions patch
    119280-10 CDE 1.6: Runtime library patch for Solaris 10
    119278-12 CDE 1.6: dtlogin patch
    124405-01 CDE1.6: sdtfprop patch
    124403-01 CDE1.6: dtstyle patch
    124401-01 CDE1.6: dtpad patch
    124399-01 CDE1.6: dtfile patch
    125279-01 CDE1.6: dtsession patch
    121977-02 CDE 1.6: dtlogin resources patch
    124397-02 CDE1.6: libDtWidget patch
    124395-01 CDE1.6: dtaction patch
    119117-29 Evolution 1.4.6 patch
    123938-01 GNOME 2.6.0: GNU Transport Layer Security Library Patch
    119418-03 GNOME 2.6.0: Gnome On-screen Keyboard Patch
    119414-13 GNOME 2.6.0: Gnome Accessibility Libraries Patch
    119598-08 GNOME 2.6.0: Gnome Screen Reader and Magnifier Patch
    120454-02 GNOME 2.6.0: Gnome Apoc GConf Adapter Patch
    120460-10 GNOME 2.6.0: Gnome libs Patch
    120284-04 GNOME 2.6.0: GNOME CORBA ORB and component framework
    122212-17 GNOME 2.6.0: GNOME Desktop Patch
    119410-05 GNOME 2.6.0: Gnome Applets Patch
    119540-05 GNOME 2.6.0: Gnome Dtlogin configuration Patch
    119548-07 GNOME 2.6.0: Gnome Multi-protocol instant messaging client Patch
    123162-02 GNOME 2.6.0: Gnome Java Run Time Patch
    120739-03 GNOME 2.6.0: GNOME PDF Viewer based on Xpdf
    119368-05 GNOME 2.6.0: Printing Technology Patch
    121606-02 GNOME 2.6.0: Python patch
    120288-03 GNOME 2.6.0: Gnome terminal Patch
    119906-08 Gnome 2.6.0: Virtual File System Framework patch
    119538-10 GNOME 2.6.0: Window Manager Patch
    119115-23 Mozilla 1.7 patch
    122958-02 GNOME 2.6.0: RealPlayer media application
    119903-02 OpenWindows 3.7.3: Xview Patch
    119059-21 X11 6.6.2: Xsun patch
    125045-01 X11 6.6.2: Xft patch
    124457-01 X11 6.6.2: xdm patch
    showrev -p
    119788-07
    120335-04
    121081-05
    121118-06
    121118-08
    121118-10
    121453-02
    122231-01
    java -version:
    java version "1.5.0_06"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
    Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
    /etc/release:
    Solaris 10 6/06 s10s_u2wos_09a SPARC
    Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 09 June 2006
    /var/sadm/system/admin/CLUSTER:
    CLUSTER=SUNWCall
    /usr/lib/cc-ccr/bin/ccr -g cns.assetid:
    1917645754
    patchsvr setup -l
    Patch source URL: https://getupdates1.sun.com/
    Cache location: /var/sadm/spool/patchsvr
    sysax /tmp: ps -ef | grep cc
    root 2006 2003 0 Feb 22 ? 0:17 /usr/lib/cc-cfw/platform/transport/bin/cctransport
    root 2022 2017 0 Feb 22 ? 0:01 /usr/lib/cc-cfw/platform/fwagent/bin/ccfwagent
    root 2003 1 0 Feb 22 ? 0:00 /bin/sh /usr/lib/cc-cfw/framework/lib/watchdog /usr/lib/cc-cfw/platform/transpo
    root 2013 2010 0 Feb 22 ? 0:01 /usr/lib/cc-cfw/platform/ccragent/bin/ccccragent
    root 2010 1 0 Feb 22 ? 0:00 /bin/sh /usr/lib/cc-cfw/framework/lib/watchdog /usr/lib/cc-cfw/platform/ccragen
    root 2017 1 0 Feb 22 ? 0:00 /bin/sh /usr/lib/cc-cfw/framework/lib/watchdog /usr/lib/cc-cfw/platform/fwagent
    noaccess 1898 1 0 Feb 22 ? 1:02 /usr/jdk/instances/jdk1.5.0/bin/java -server -XX:+BackgroundCompilation -Djava.
    root 8884 5284 0 13:39:27 console 0:00 grep cc
    sysax /tmp:

  • Retail Execution Application Device Registration Issues

    Hello Community,
    I am having issues registering the Retail Execution application with a user in CRM.
    I am testing with an iOS device where I downloaded the application from the app store and an Android device where I got the APK from the SAP marketplace.
    The guide I am following is the Administrator's Guide SAP Retail Execution 3.2.0.
    There are a few issues i've come across which I think might be contributing to my devices not enrolling.
    I've completed the setup of the environment till the point in the documentation for Data Change Notification where I need to create an RFC connection to the SMP server.
    I entered the IP address for the SUP server with the port as 80. Is port 80 correct?
    The username ive setup as supAdmin@Admin with the password.
    When I test the connection I get a : Status HTTP Response 404 error.
    Another issue I have is that in the documentation under the section enrolling a device using the Relay Server, all the fields are referring to SMP username, SMP Farm ID, SMP Activation code and so on. The connection details I have used in other apps are as follows:
    Server : <ip of relay server>
    Farm : Relay server Farm ID
    Username : jcommerford@crm           (CRM login ID @ security configuration - crm is my HTTPAuthentication security configuration I created in SUP)
    password :
    Port : 80 (relay server port)
    URL suffix : leave blank
    Domain : The new domain I created in SUP and where the Rex MBO is deployed.
    So it isnt making sense as to what details need to go into here.
    Lastly...
    What is the absolute minimum setup of the CRM system and SUP to register a user through the relay server?
    I would like to comment that I havnt performed the initial download of Master Data using DCN but didnt think this was needed to enrol a device. Other than that the guide was followed and configuration done according to it.
    Let me know if anymore information is needed as I am very stressed to get this issue sorted out.
    Thank you
    Jared

    Hello Jared
    Has the registration worked without the Relay server setup? I would suggest you try that first.
    I am assuming you already set the SM59 destinations for CRM to SMP and trusted RFC to corresponding ECC (but this is not necessarily the issue, because the registration is failing).
    Please confirm that the RFC Destination is set as follows (use the supAdmin user on the Logon & Security page)
    Check the security provider on SMP (your's may be different but I am using the following for POC and it works)
    Could you please confirm if the REX package was deployed correctly on the SMP server by selecting the connection pools for both CRM and ECC for corresponding MBO's
    Please post a log of the SMP server once you switch to direct registration to SMP (without relay server)
    Thanks
    Raza.

  • Zenworks 7 Linux Management Device Registration Issue

    All,
    Below is a detailed description of a resistration issue using Zenworks
    Linux Management 7.
    Hardware Configuration:
    1- DSL Modem (Westell Model 2200)
    1- DI 614+ 2.4 GHz Broadband Wireless Router (includes 4-5 ethernet
    ports) with a IP address of 192.168.0.1
    1- PC Server running Redhat SUSE Linux Enterprise Server 9 (has a static
    IP address of 192.168.0.103). This machine is running the Zenworks 7
    Linux Management Software and is able to sucessfully launch the Zenworks
    7 Control Panel.
    1- Redhat Linux Enterprise Server 3 on a completely different network
    with a static IP address (207.44.142.56). This machine is running the
    Zenworks Linux Management Agent install using the ./zlm-install -a
    command.
    Network Configuration:
    The broadband DSL modem is connected directly to the WAN ethernet port on
    the wireless router
    The primary PC server running Redhat SUSE Linux Enterprise Server 9 has a
    direct connection to one of the ethernet ports on the wireless broadboard
    router with a private static IP address of 192.168.0.103 and has a public
    IP of 70.22.107.168.
    The DSL modem is has a direct connection to the telephone line.
    The Redhat Linux Enterprise Server 3 is on a completely different network
    with a IP of 207.44.142.56.
    No firewalls are configured on the primary server and the wireless router
    Port Forwarders are configured on the broadband wireless router as
    follows:
    zlm1
    192.168.0.103
    TCP 80/80
    always
    zlm2
    192.168.0.103
    TCP 443/443
    always
    zlm3
    192.168.0.103
    TCP 524/524
    always
    zlm4
    192.168.0.103
    TCP 1299/1299
    always
    zlm5
    192.168.0.103
    TCP 2544/2544
    always
    zlm6
    192.168.0.103
    TCP 5506/5506
    always
    zlm7
    192.168.0.103
    TCP 10389/10389
    always
    zlm8
    192.168.0.103
    TCP 10636/10636
    always
    Goal:
    To successfully register the Redhat Linux Enterprise 3 server (i.e. the
    managed device with IP 207.44.142.56) with the primary server
    (192.168.0.103 SUSE Redhat Enterprise Server 9 machine) so it can be
    viewed and managed from the Zenworks 7 Control panel.
    Nature of Problem:
    When attempting to register the managed device (207.44.142.56) with the
    primary server (192.168.0.103) which resides inside of my Wireless Local
    Area Network (WLAN) via the following command, it appears to fail. I'm
    unable to view or configure this managed device inside of the Zenworks 7
    Linux Management Control Panel. The following are 2 manual approaches
    that I take to register the managed device and the results for each.
    Register using private IP approach:
    /opt/novell/zenworks/bin/rug sa https://192.168.0.103
    Results: ERROR: Could not add 'https://192.168.0.103': Download failed:
    (https://192.168.0.103/zenworks-registration/service.xml) Error:
    ConnectFailure
    Register using public IP approach:
    /opt/novell/zenworks/bin/rug sa https://70.22.107.168
    Results: ERROR: Could not add 'https://70.22.107.168': Download failed:
    (https://70.22.107.168/zenworks-registration/service.xml) Error:
    ConnectFailure
    Regards,
    Darrick Addison
    Sr. Software Engineer/Consultant
    ASC Technologies, LLC
    Ph: 443.257.9116
    Fax: 410.360.5570
    E-mail: [email protected]
    Web: www.asctllc.com

    On Tue, 08 Nov 2005 02:37:16 GMT, [email protected] wrote:
    > Below is a detailed description of a resistration issue using Zenworks
    > Linux Management 7.
    duplicate question - can I gently mention a point? Whilst we naturally
    understand that you may need information/help in a hurry, asking the
    same question in multiple forums dilutes the answers you get, and makes
    more work for those of us who have to read them; it would help if you
    could avoid this in future.
    Many thanks
    (c) Shaun Pond, stolen without permission ;-)
    Marcus Breiden
    Please change -- to - to mail me.
    The content of this mail is my private and personal opinion.
    http://www.edu-magic.net

  • Zenworks Linux Management Device Registration Issue

    All,
    Below is a detailed description of a resistration issue using Zenworks
    Linux Management 7.
    Hardware Configuration:
    1- DSL Modem (Westell Model 2200)
    1- DI 614+ 2.4 GHz Broadband Wireless Router (includes 4-5 ethernet
    ports) with a IP address of 192.168.0.1
    1- PC Server running Redhat SUSE Linux Enterprise Server 9 (has a static
    IP address of 192.168.0.103). This machine is running the Zenworks 7
    Linux Management Software and is able to sucessfully launch the Zenworks
    7 Control Panel.
    1- Redhat Linux Enterprise Server 3 on a completely different network
    with a static IP address (207.44.142.56). This machine is running the
    Zenworks Linux Management Agent install using the ./zlm-install -a
    command.
    Network Configuration:
    The broadband DSL modem is connected directly to the WAN ethernet port on
    the wireless router
    The primary PC server running Redhat SUSE Linux Enterprise Server 9 has a
    direct connection to one of the ethernet ports on the wireless broadboard
    router with a private static IP address of 192.168.0.103 and has a public
    IP of 70.22.107.168.
    The DSL modem is has a direct connection to the telephone line.
    The Redhat Linux Enterprise Server 3 is on a completely different network
    with a IP of 207.44.142.56.
    No firewalls are configured on the primary server and the wireless router
    Port Forwarders are configured on the broadband wireless router as
    follows:
    zlm1
    192.168.0.103
    TCP 80/80
    always
    zlm2
    192.168.0.103
    TCP 443/443
    always
    zlm3
    192.168.0.103
    TCP 524/524
    always
    zlm4
    192.168.0.103
    TCP 1299/1299
    always
    zlm5
    192.168.0.103
    TCP 2544/2544
    always
    zlm6
    192.168.0.103
    TCP 5506/5506
    always
    zlm7
    192.168.0.103
    TCP 10389/10389
    always
    zlm8
    192.168.0.103
    TCP 10636/10636
    always
    Goal:
    To successfully register the Redhat Linux Enterprise 3 server (i.e. the
    managed device with IP 207.44.142.56) with the primary server
    (192.168.0.103 SUSE Redhat Enterprise Server 9 machine) so it can be
    viewed and managed from the Zenworks 7 Control panel.
    Nature of Problem:
    When attempting to register the managed device (207.44.142.56) with the
    primary server (192.168.0.103) which resides inside of my Wireless Local
    Area Network (WLAN) via the following command, it appears to fail. I'm
    unable to view or configure this managed device inside of the Zenworks 7
    Linux Management Control Panel. The following are 2 manual approaches
    that I take to register the managed device and the results for each.
    Register using private IP approach:
    /opt/novell/zenworks/bin/rug sa https://192.168.0.103
    Results: ERROR: Could not add 'https://192.168.0.103': Download failed:
    (https://192.168.0.103/zenworks-registration/service.xml) Error:
    ConnectFailure
    Register using public IP approach:
    /opt/novell/zenworks/bin/rug sa https://70.22.107.168
    Results: ERROR: Could not add 'https://70.22.107.168': Download failed:
    (https://70.22.107.168/zenworks-registration/service.xml) Error:
    ConnectFailure
    Regards,
    Darrick Addison
    Sr. Software Engineer/Consultant
    ASC Technologies, LLC
    Ph: 443.257.9116
    Fax: 410.360.5570
    E-mail: [email protected]
    Web: www.asctllc.com

    On Tue, 08 Nov 2005 02:40:58 GMT, [email protected] wrote:
    > Below is a detailed description of a resistration issue using Zenworks
    > Linux Management 7.
    duplicate question - can I gently mention a point? Whilst we naturally
    understand that you may need information/help in a hurry, asking the
    same question in multiple forums dilutes the answers you get, and makes
    more work for those of us who have to read them; it would help if you
    could avoid this in future.
    Many thanks
    (c) Shaun Pond, stolen without permission ;-)
    Marcus Breiden
    Please change -- to - to mail me.
    The content of this mail is my private and personal opinion.
    http://www.edu-magic.net

Maybe you are looking for