NODE-NOT-REACHABLE on ISE

Primary ISE node (Serving Admin and Monitor personas) is showing two of the PSNs as "NODE-NOT-REACHABLE" under Replication Status on Deployment page on GUI. It can ping the PSNs and PSNs are actually registered to the Primary admin/monitor node. How can I fix this?
Thanks,
Kashish

Hi,
I found the issue on ny network and it was due to a different dns record.
Simple way to check is issuing a dns lookup from admin node cli of the problem node. Then repeat from problem node attempting to resolve admin node.
Then if that looks good you can issue the command on both nodes...
Show logging application ise tail,
That output should give you a listing of the nodes in the ise deployment and the ip addresses of each node.
Thanks.
Sent from Cisco Technical Support Android App

Similar Messages

ISE 1.1.3.124 secondary node not reachable after registration

G'day All,
I'm constantly seeing that the sync and replication status for my secondary admin/monitor node in the primary node as node not reachable. The secondary still thinks it is in standalone mode. When I run the ISE diag tool connectivity tests I am able successfully ping the devices from each other using both hostname and ip and the nslookup also works fine between both nodes. Ping and nslookups also work from different networks within the environment. The two nodes are in the same vlan on a 6500 vss pair but on different switches of the pair. I'm new to ISE so any help is greatly appreciated.
Thanks All.
JS
Sent from Cisco Technical Support iPhone App

Hi Saurav,
Thanks for your prompt repsonse...
I have worked through that section of the document. The registration completes successfully, I've got NTP sync on both nodes and the system time on both nodes is identical.
I am only using the self signed certificates, but following the user guide instructions I have imported the secondary's cert into the primary node.
Just as of about 30 minutes ago, I saw an alarm on the Secondary ISE node stating that a Slow or Stuck Replication has been detected...
As I said in the original post, I can ping the fqdn's from each other so it appears that the DNS requirements have been satisfied.
I've changed the admin account password, I am certain that the ISE DB passwords are correct and the same on both nodes and the timezones for both nodes is the same also....
It looks to me that registration is fine, but the first full replication isn't completing successfully
Thanks,
JS

ISE NODE NOT REACHABLE when building distributed deployment

I am trying to build a distributed deployment with the following personas:
2 policy admin nodes
2 monitoring nodes
4 policy service nodes
This was a project that was partially implemented but never in production. It was in a distributed deployment, but half the nodes were no longer working (http errors or devices weren't reachable or could not sync). I decided to start from scratch. All nodes were:
-de-registered
-application was reset to factory defaults on all nodes
-upgraded all 8 nodes to 1.1.4.218 patch 1
-installed all new certs and joined all nodes to the domain
-added to DNS forward and reverse lookup zones
When I make 1 admin node primary and register the other nodes (secondary admin, monitoring, policy services) the nodes successfully register and show up in the deployment window of the primary; however, all the nodes show as NODE NOT REACHABLE. After registration, I've noticed that the registered nodes are still showing as STANDALONE if I access the GUI. I've tried rebooting them manually after registration and they are still unreachable. I have also tried resetting the database user password from the CLI on both admin nodes and the results are always the same.

Originally I had added them all at the same time. I thought that maybe I just wasn't waiting long enough for the sync. I waited an entire day and all the nodes were still unreachable. At this point, I've de-registered all the nodes, rebooted all the nodes, converted the primary back to standalone (the remaining nodes never converted from standalone to distributed even when I rebooted them after registering despite a message that they were successfully registered), converted one node back to primary and tried to register just the secondary admin node giving it plenty of time to sync; this node is still not reachable from the primary.
I've quadruple checked the certificates on all the nodes, these certs were all added on the same day (just last week) and the default self-signed certs were removed.
I had restored from a backup on the primary so I might just rest the config on that node and try joining the other nodes before I restore again.

Clusterware Installation (Nodes not reachable....) 10G R2 on Windows

Hello Guys,
I am struck with this problem for quite a long time... I am installing Oracle Clusterware 10G R2 on windows 2000 operating system.
Well i have setup my public, private and virtual IP correctly, i can ping anyone of them.
During installation when it comes to the screen "Specify Cluster Configuration" i have entered the correct information of IPs on each node BUT when i click next button it says "
The following nodes do not appear to be reachable
rac1-vip
rac2-vip
Please check that nodes in the list are up and reachable
while i can ping rac1-vip.beaconhouse.edu.pk and rac2-vip.beaconhouse.edu.pk from both nodes and also the underlying IPs of these names.
Please help me to come out of this problem as i am struk with it.... cant continue installation while i have checked everything again and again...
Please Help...
Regards,
Imran Baig

This thread has already been answered at the DB General forum here: Re: During RAC Installation (Following Nodes do not appear to be reachable.
~ Madrid

Ise node is not reachable after upgrading 1.2

Hi, I was using beta version of ISE with 1.2.834 code. and now the official release came out so I upgraded it.
after that, the ISE is not communicating with AD, and when I go to download logs, It says node is not reachable even though it is STANDALONE mode.
does anyone know how to work around this ?
should I just delete everything and go from scratch ?

The ISE is not communicating to the AD, So, you have to rejoin the domain. For this purpose please follow the following actions:
Go to Administration > Identity Management > External Identity Stores and select Active Directory from the left-hand pane.
Click Join at the bottom of the configuration page:
Also please check the LDAP port

For server the Node Manager associated with machine is not reachable

Hello all,
I am getting this error, when i start my Managed Server which is in shutdown state
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The configuration details are
i am using weblogic 9.2 MP3 version in windows 2k3 server.
It has a machine vm-bea-dev, a cluster cluster-saa-dev, to which both the managed servers saa-dev-1 and saa-dev-2 are assigned. There are 3 applications deployed onto managed Server 1 and 1 for managed Server 2.
Managed Server 1 is in shutdown state, and when i start the server, it gives the error specified below
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The same for Managed Server 2 too, and this server is in Admin State, i dont know how it went into that state.
Can somebody please help me reslove it.
Thanks in advance

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

UCCX error-remote UCCX node is not reachable

Hi,
I am working in UCCX 9.0,trying to upload new script developed thorugh UCCX script editor ,whenever I click upload script through "script management" tab,giving error as "remote UCCX node is not reachable,it is not recommended to create,modify or delete the files in this state,as it will be inconsistent between nodes",let me know any idea about this error.
Thanks,
Baskar.

Hi,
RTMT is configured and found the following error.
2013-11-11 04:11:39 :INFO: Received request to start the service Cisco Unified CCX Engine
2013-11-11 04:11:39 :INFO: Checking if PID File exists.
2013-11-11 04:11:39 :INFO: process Cisco Unified CCX Engine is not running
2013-11-11 04:11:39 :INFO: Starting process Cisco Unified CCX Engine, Exe=/opt/cisco/uccx/bin/UCCX_Engine, Conf=/opt/cisco/uccx/conf/UCCX_EngineCfg.xml
2013-11-11 04:11:39 :INFO: Cisco Unified CCX Engine initialization complete.... PID 18469 updated in pid file /opt/cisco/uccx/conf/UCCX_Engine.pid
2014-06-05 05:45:46 :INFO: Received request to start the service Cisco Unified CCX Engine
2014-06-05 05:45:46 :INFO: Checking if PID File exists.
2014-06-05 05:45:47 :INFO: PID File exists, pid=18469
2014-06-05 05:45:47 :INFO: process Cisco Unified CCX Engine with PID 18469 might have crashed, PID file still exists
2014-06-05 05:45:47 :INFO: Stale PID entry 18469, removing PID file
2014-06-05 05:45:49 :INFO: Starting process Cisco Unified CCX Engine, Exe=/opt/cisco/uccx/bin/UCCX_Engine, Conf=/opt/cisco/uccx/conf/UCCX_EngineCfg.xml
2014-06-05 05:45:49 :INFO: Cisco Unified CCX Engine initialization complete.... PID 4201 updated in pid file /opt/cisco/uccx/conf/UCCX_Engine.pid
2014-06-05 07:04:03 :INFO: Received request to stop the service Cisco Unified CCX Engine
2014-06-05 07:04:03 :INFO: PID File exists, pid=4201
2014-06-05 07:04:03 :INFO: Stopping the Process Cisco Unified CCX Engine, pid=4201
2014-06-05 07:04:03 :INFO: Stopped the process Cisco Unified CCX Engine
2014-06-05 07:28:29 :INFO: Received request to start the service Cisco Unified CCX Engine
2014-06-05 07:28:29 :INFO: Checking if PID File exists.
2014-06-05 07:28:29 :INFO: process Cisco Unified CCX Engine is not running

Node Manager Not Reachable

Hi Everyone,
I'm very new to WebLogic, so I apologize if this is a dumb question.
I'm trying to install WebLogic as server for OBIEE. My environment is pretty simple. I have two Oracle Red Hat Linux 32-bit physical machines, let's call them WLS_SERVER and OBIEE_SERVER. I installed OBIEE on the OBIEE_SERVER and tested it using the out of the box OC4J container and that worked fine.
Then I installed WebLogic 11g on the WLS_SERVER machine and I ran the config.sh script. I used the configuration GUI to register the two physical machines and an additional server object called BIServer. Out of the box, web logic comes with AdminServer server object. I heard it's a bad practice to deploy applications to the AdminServer, hence why I created the BIServer object. I associated BIServer with the OBIEE_SERVER machine.
I went to start the BIServer and I got the following error:
"For server BIServer, the Node Manager associated with machine OBIEE_SERVER is not reachable."
How do I setup a Node Manager on the OBIEE_SERVER? Do I also need to physical put the WebLogic install file on the OBIEE_SERVER box and also run the installer there? Or there a copy paste thing I do? What am I missing here?
I appreciate the help!
-Joe

I'm trying to install WebLogic as server for OBIEEI have not heard about OBIEE, but if your aim is to use weblogic as a server for hosting this then you definitely need to install weblogic on the physical box where OBIEE will be hosted.
I associated BIServer with the OBIEE_SERVER machine.
I went to start the BIServer and I got the following error:
"For server BIServer, the Node Manager associated with machine OBIEE_SERVER is not reachable."Again not sure what is BIServer but I think you are missing a number of steps here. If you are trying to run BIServer
on weblogic you definitely need to install WLS on this physical machine [OBIEE_SERVER]. You will then need to configure a node manager on OBIEE_SERVER machine to enable it to start remotely from the admin machine.
Link for Node Manager. Since you are in Linux you can try setting up script based node manager.
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/server_start/nodemgr.html#wp1099239

11g node manager reachable but server does not start from admin console

I have a issue with node manager is reachable from admin console and from command prompt it is not connected and could not able to start the managed server.
If i change /config/nodemanager/nm_password.properties plain text and restart it is not reachable in admin console abut can connect from command prompt. I could not able to start the even with this scenario.
i see below error when try to check machine monitor tab.
<Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'dom_11gint' for user 'Ckr10ycOJN' denied".>
Ckr10ycOJN username in config.xml
node manager and managed servers are not root user process.
Please help me if have any suggestions.

Pls. make sure the following points in your environment.
1) Check '*nodemanager.domains*' file in <<WL_HOME>>\commo\nodemanager directory
     a) This file should have the entry for your domain 'dom_11gint'.
     b) Ensure the path referred in the nodemanager.domains file is correct one.
2) Ensure the following remote server startup parameters are passed properly.
     a) In the Admin Console, Navigate Servers --> <<SERVER_NAME>> -->Configuration --> Server Start
     b) Pass the required Class Path, Arguments, User Name, Password(User name and Password to boot the managed servers)

Uc560 - CUE Webinterface not reachable

Hello,
i have a problem with my UC560. Especially with the CUE Webinterface. After config my UC560 everthings working fine.
But the webinterface of the CUE is not reachable. I can ping the integtr. Service. Engine with IP 10.1.10.1. from my network.
A service-module integr.S.E. status reports -> everything OK. A seesion on CLI also connects and works.
Is there any idea ? help !!!
here some configs :
interface Integrated-Service-Engine0/0
description Interface used to manage integrated application modulecue is initialized with default IMAP group
ip unnumbered Vlan90
ip nat inside
ip virtual-reassembly in
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
interface GigabitEthernet0/1/3
description Interface used to communicate with integrated service module
switchport access vlan 90
no ip address
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
interface Vlan90
description $FW_INSIDE$
ip address 10.1.10.2 255.255.255.252
ip access-group 103 in
ip nat inside
ip virtual-reassembly in
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
ip http path flash:/gui
ip dns server
ip nat inside source list 1 interface GigabitEthernet0/0 overload
ip route 10.1.10.1 255.255.255.255 Vlan90

Hello,
I have a similar issue. I know that there are many threads like this but this is the newest I found
I've wiped the preloaded configuration and now using the uc560 like a standard ISR. I've made a lot of tests and changes, using G0/0 and an IP for connecting to the LAN, or g0/1/0 as trunk/access port connecting to the LAN. I've ended up with the configuration I'm attaching. There is no way to have connectivity with the CUE. I've tried with and without VLANs (the file attached is with VLANs). NAT is irrelevant in my case since there is not anything to translate it's all a private routed network. I still cannot ping the ISE inf from inside the uc560 localy or the gateway address from inside the CUE.
This G0/1/3 seems to need some special configuration to be done in order to work. Do you know what is it?
It's also not possible to make the CUE to factory default. No initial setup wizard starts... nothing. No wizard needed for the initial setup like all the other CUE products?
Here is the config:
! interface GigabitEthernet0/0 no ip address duplex auto speed auto h323-gateway voip interface!interface Integrated-Service-Engine0/0 description Loopback interface used to manage integrated application module ip unnumbered Vlan2 service-module ip address 192.168.2.254 255.255.255.0 service-module ip default-gateway 192.168.2.2!interface GigabitEthernet0/1/0 switchport access vlan 2 no ip address!interface GigabitEthernet0/1/1 no ip address!interface GigabitEthernet0/1/2 no ip address!interface GigabitEthernet0/1/3 description Interface used to communicate with integrated service modue switchport access vlan 2 no ip address service-module ip address 192.168.2.254 255.255.255.0 service-module ip default-gateway 192.168.2.2!interface BRI0/1/0 no ip address isdn switch-type basic-net3 isdn point-to-point-setup trunk-group isdn 5!interface BRI0/1/1 no ip address isdn switch-type basic-net3 isdn point-to-point-setup trunk-group isdn 6!interface BRI0/2/0 no ip address isdn switch-type basic-net3 isdn point-to-point-setup! interface BRI0/2/1 no ip address isdn switch-type basic-net3 isdn point-to-point-setup!interface Vlan1 no ip address!interface Vlan2 ip address 192.168.2.2 255.255.255.0!ip forward-protocol ndip http serverno ip http secure-serverip http path flash:/gui!ip route 0.0.0.0 0.0.0.0 192.168.2.1ip route 192.168.2.254 255.255.255.255 Integrated-Service-Engine0/0!!!telephony-service no auto-reg-ephone max-ephones 15 max-dn 15 ip source-address 192.168.2.2 port 2000 secondary 192.168.2.3 rehome 15 time-zone 28 time-format 24 max-conferences 4 gain -6 moh flash:/media/music-on-hold.au multicast moh 239.0.0.1 port 16384 route 192.168.2.2 web admin system name admin password cisco time-webedit transfer-system full-consult create cnf-files version-stamp 7960 Mar 06 2013 15:02:09!
Thanks in advance!

IOS Remote Desktop App resolves hostname but throws Host is not reachable error.

Hello,
I am trying to use the Remote Desktop app on my iPad running iOS 7.0.2 to connect to a server through our Juniper VPN. When I type the hostname or IP address I get an error that say "Host is not reachable". If I connect through my Mac I have no
problem when on the same VPN. I have looked through all of the setting in Junos Pulse and it is setup to route all traffic through the VPN, and I do not know of anything that would be blocking it on the network end.
Edit: I am connecting to a Windows Server 2008 R2 box with RDP turned on with all types of connections.
Here is the log data for my latest attempt.
[2013-Nov-19 11:23:42] RDP (0): *** Application lauched ***
[2013-Nov-19 11:23:43] RDP (0): Application became foreground application
[2013-Nov-19 11:24:30] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2013-Nov-19 11:24:30] RDP (0): client version: 8.0.24094 on iPad3,4 (iPhone OS 7.0.3)
[2013-Nov-19 11:24:30] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2013-Nov-19 11:24:30] RDP (0): Showing credentials dialog
[2013-Nov-19 11:24:49] RDP (0): Final rdp configuration used: {
    activeUsername = "DOMAIN\\UserName";
    arcTimeout = 1800;
    cacheId = BEBD1725D63BB841;
    configurationVersion = 8;
    console = 0;
    host = "server.mysite.com";
    label = "Server";
    mouseMode = "-1";
    port = 3389;
    soundMode = 1;
    swapMouseButtons = 0;
    type = rdp;
    utilityBar = "-1";
    kCFProxyTypeKey = kCFProxyTypeNone;
[2013-Nov-19 11:24:49] RDP (0): --- BEGIN INTERFACE LIST ---
[2013-Nov-19 11:24:49] RDP (0): lo0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2013-Nov-19 11:24:49] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2013-Nov-19 11:24:49] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2013-Nov-19 11:24:49] RDP (0): en0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): en0 af=30 (AF_INET6) addr=fe80::66:9d3c:3d77:5cce%en0 netmask=ffff:ffff:ffff:ffff::
[2013-Nov-19 11:24:49] RDP (0): en0 af=2 (AF_INET) addr=192.168.114.44 netmask=255.255.252.0
[2013-Nov-19 11:24:49] RDP (0): awdl0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): awdl0 af=30 (AF_INET6) addr=fe80::3c11:d7ff:feb2:7a82%awdl0 netmask=ffff:ffff:ffff:ffff::
[2013-Nov-19 11:24:49] RDP (0): en2 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): utun0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): utun0 af=2 (AF_INET) addr=10.100.01.01 netmask=255.255.255.255
[2013-Nov-19 11:24:49] RDP (0): --- END INTERFACE LIST ---
[2013-Nov-19 11:24:49] RDP (0): Not using any proxy
[2013-Nov-19 11:24:49] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2013-Nov-19 11:24:49] RDP (0): Resolved 'server.mysite.com' to '10.100.01.01' using NameResolveMethod_Unknown(0)
[2013-Nov-19 11:25:09] RDP (0): Exception caught: Exception in file '/Users/build/jenkins/workspace/rc-ios-develop/protocols/RDP/cftcpendpoint.cpp' at line 242
    User Message : Host is not reachable
[2013-Nov-19 11:25:09] RDP (0): Error message: Host is not reachable(phase: 0, type: 0, reason: 0, systemCode: -1, systemMessage: )
[2013-Nov-19 11:25:09] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
[2013-Nov-19 11:25:09] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2013-Nov-19 11:25:09] RDP (0): ------ END ACTIVE CONNECTION ------
Cameron

Hi,
According to the log, your iPad tried to connect the remote server with IP address 10.100.01.01/32. Please check if it is the correct IP address of the server.
Also, please make sure that your iPad can connect to your VPN network successfully and get a valid IP address so that it can remote your internal server.
Thanks.
Jeremy Wu
TechNet Community Support

The system is not reachable, the login data could not be considered

Hello
I'm trying to connect via Hana Studio to a Hana One instance I have configured in AWS, following the guides & videos in the Hana Academy.
When adding the system in Hana studio, I get an error message after inputting the SYSTEM password:
The system is not reachable, the login data could not be considered
I've seen another post in the forum where the user solved the issue by resetting the SYSTEM password to a password without special characters, but mine is already "special character" free.
Are there others who have had difficulties when adding a new system?
Regards
Yann

Hi Swapan,
Thank you for your attention and message.
I downloaded the SAP HANA Studio from "Get your own SAP HANA, developer edition on Amazon Web Services (http://scn.sap.com/docs/DOC-28294)", specifically at SAP HANA Studio, developer edition and SAP HANA Client, developer edition, for Windows XP 32-bit. Is this HANA One? How to know the version of HANA server? How to make my Internet or firewall allow me to go out to the JDBC port? I am just learning to deal with these computer-science issues.
Regards,
Beiwei
Date: Wed, 4 Sep 2013 20:52:41 -0700
From: [email protected]
To: [email protected]
Subject: Re: - The system is not reachable, the login data could not be considered
                                                                                SAP HANA
    The system is not reachable, the login data could not be considered
    created by Swapan Saha in SAP HANA One Platform on AWS - View the full discussion
Hi Beiwei,
I suppose you are using HANA One (which you can only launch today from AWS Marketplace and HANA costs 99 cents/hr). If it is HANA One, which version of HANA One you are using? Please make sure you are using the same version of HANA Studio with HANA Server? Instance number in HANA One is 00.
If you HANA One, by default, it will open all the necessary ports. Please make sure you are Internet or your firewall allow you to go out to the JDBC port. If not, you cannot connect your studio behind your firewall with HANA server in the cloud.
Thanks,
Swapan
     Reply to this message by replying to this email -or- go to the message on SAP HANA
     Start a new discussion in SAP HANA One Platform on AWS by email or at SAP HANA

Officejet Pro X476dw MFP not reachable

Hi,
out of the blue my Officejet Pro X476dw MFP turned 'not reachable' from my MacBook. Device is still connected to my Wifi network, no changes there since last use. I can print ok from my iPhone. I turned the device off and on again - no success. I turned the MacBook off and on again - same. I reconfiguered Wifi connection at device - same. I deleted printer from MacBook and tried to re-add but installation program couldn't find device. I tried to connect manually using IP address that was shown on device - 'device not reachable'.
I am running out of ideas, appreciate any help!
Thank you!
Maik.

@weirdharrell
‎Thank you for using HP Support Forum. I have brought your issue to the appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post ( serial numbers and case details).
If you are unfamiliar with the Forum's private messaging please click here to learn more.
Thank you,
Omar
I Work for HP

Photosmart C4385 "Device Not Reachable"

I know this has been addressed in other threads, but none of the solutions have worked for me and my configuration is a little different. So here goes:
I'm running OS 10.6 Snow Leopard with my C4385. My computer is connected to a wireless network via an extender. I don't know anything about the router other than it's probably a Cisco since that's in the network name. The router and extender are both in my landlord's house, so I don't have access to them to reboot, check settings, or anything. Until this morning my printer was associated with the main network, which worked fine, but the signal is very weak and I would rather have it associated with the extender network. I went through the HP Setup Assistant and now all I get is the "Device Not Reachable" error message, whether I use the extender or main network.
I printed a Network Configuration Page and typed the printer's IP into my browser, and it shows up just fine, saying it's connected to the main network. Print & Fax under System Preferences disagrees and I can't print at all anymore (except with the USB cable). The only thing I changed recently is switching to a manual IP address for my laptop since I had lots of connectivity issues with automatic IPs, but after that everything worked until this morning when I ran Setup Assistant.
Sorry for writing a novel. I wish I had more information about the hardware but my landlord's not very helpful with these sorts of things. Any advice would be great! I've tried scrubbing software and reinstalling it and resetting the printing system, with no luck.

I see a couple of potential problems, here.
First, adding the printer by IP is dicey. If the router changes the printer's IP (actually WHEN it does, because eventually it will), then your Mac may lose track of it. Plus, adding by IP usually only enables printing, not scanning.
Second, HP printers don't seem to play well with wifi extenders. Is there a way to move your printer so that it is connected to the main router, not the extender?
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

CUE Website not reachable

Hello,
we've configured a UC560 with Cisco Standards. So the CUE has the IP-adress 10.1.10.1 (Gateway .2).
The CUE successfully answer a ping ! The CCA CUE diagnostics ended successful.
I also can connect to CUE through CLI of the UC560.
BUT : The Webinterface of the CUE does not answer. The webiste ist not reachable.
Here the http config of the UC560 :
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
ip http path flash:/GUI
telephony-service
video
fxo hook-flash
max-ephones 138
max-dn 600
ip source-address 10.1.1.1 port 2000
auto assign 1 to 1 type bri
calling-number initiator
service phone videoCapability 1
service phone ehookenable 1
service dnis overlay
service dnis dir-lookup
service dss
timeouts interdigit 5
system message Cisco Small Business
url services
http://10.1.10.1/voiceview/common/login.do
url authentication
http://10.1.10.1/voiceview/authentication/authenticate.do
cnf-file location flash:
cnf-file perphone
user-locale U4 load CME-locale-de_DE-German-8.1.2.2.tar
network-locale U4
load 7941 SCCP41.9-1-1SR1S
load 7941GE SCCP41.9-1-1SR1S
load 7961 SCCP41.9-1-1SR1S
load 7961GE SCCP41.9-1-1SR1S
load 521G-524G cp524g-8-1-17
time-zone 23
time-format 24
date-format dd-mm-yy
dialplan-pattern 1 5909.. extension-length 2
keepalive 30 auxiliary 4
voicemail 39
max-conferences 8 gain -6
call-forward pattern .T
call-forward system redirecting-expanded
moh flash:/media/music-on-hold.au
multicast moh 239.10.16.16 port 2000
web admin system name cisco secret 5 $1$xdzm$dQ00q0.IUYeRDA4lTuNIl1
dn-webedit
time-webedit
transfer-system full-consult dss
transfer-pattern .T
transfer-pattern 0.T
transfer-pattern 6.. blind
secondary-dialtone 0
and the telephony part :
telephony-service
video
fxo hook-flash
max-ephones 138
max-dn 600
ip source-address 10.1.1.1 port 2000
auto assign 1 to 1 type bri
calling-number initiator
service phone videoCapability 1
service phone ehookenable 1
service dnis overlay
service dnis dir-lookup
service dss
timeouts interdigit 5
system message Cisco Small Business
url services http://10.1.10.1/voiceview/common/login.do
url authentication http://10.1.10.1/voiceview/authentication/authenticate.do
cnf-file location flash:
cnf-file perphone
user-locale U4 load CME-locale-de_DE-German-8.1.2.2.tar
network-locale U4
load 7941 SCCP41.9-1-1SR1S
load 7941GE SCCP41.9-1-1SR1S
load 7961 SCCP41.9-1-1SR1S
load 7961GE SCCP41.9-1-1SR1S
load 521G-524G cp524g-8-1-17
time-zone 23
time-format 24
date-format dd-mm-yy
dialplan-pattern 1 5909.. extension-length 2
keepalive 30 auxiliary 4
voicemail 39
max-conferences 8 gain -6
call-forward pattern .T
call-forward system redirecting-expanded
moh flash:/media/music-on-hold.au
multicast moh 239.10.16.16 port 2000
web admin system name cisco secret 5 $1$xdzm$dQ00q0.IUYeRDA4lTuNIl1
dn-webedit
time-webedit
transfer-system full-consult dss
transfer-pattern .T
transfer-pattern 0.T
transfer-pattern 6.. blind
secondary-dialtone 0
Can the problem be based on corrupt http CUE files or the wrong version ? Which files are required ?
May the Firewall ACLs block this traffic ? But ping works !
Please help !
Greets
Huck

That usually happens when your PC is using a default gatway that doesn't know about CUE address subnet.
So you have to fix your routing.

NODE-NOT-REACHABLE on ISE

Similar Messages

Maybe you are looking for