PXE DHCP ICMP:Destination Unreachable Message

Hi
I have a question regarding PXE and DHCP. Is it possible to ping a machine, which is in PXE boot with a DHCP address and able to access my SCCM server? Unfortunately i cannot ping the machine and in network traffic i see:
12913 17:00:17 01.04.2015 759.8323064 SRV-SCCMDP-501 <00> 172.16.10.66 ICMP ICMP:Destination Unreachable Message, Port Unreachable, 172.16.8.38:69 {IPv4:228}
No firewall between the machines and is the same subnet.
Thank you in Advance

Hi Torsten
Thank you for your reply. I'm in hardware pxe, so no firewall is active.
Here is the network traffic:
1525597 11:55:38 02.04.2015 68880.5266514  172.16.10.25 SRV-SCCMDP-501 TFTP TFTP: Read Request - File: SMSBoot\x64\wdsnbp.com, Transfer Mode: octet tsize: 0 {UDP:1483, IPv4:1477}
1525598 11:55:38 02.04.2015 68880.5266948  SRV-SCCMDP-501 172.16.10.25 ICMP ICMP:Destination Unreachable Message, Port Unreachable, 172.16.8.38:69 {IPv4:1477}
1525701 11:55:44 02.04.2015 68886.5143787  172.16.10.25 SRV-SCCMDP-501 TFTP TFTP: Read Request - File: SMSBoot\x64\wdsnbp.com, Transfer Mode: octet tsize: 0 {UDP:1488, IPv4:1477}
1525702 11:55:44 02.04.2015 68886.5144115  SRV-SCCMDP-501 172.16.10.25 ICMP ICMP:Destination Unreachable Message, Port Unreachable, 172.16.8.38:69 {IPv4:1477}
I'm lost....

Similar Messages

Can ACE 4710 send ICMP-dest-unreachable?

Dear Community!
We have previously configured an ACE context for implementing redundant corporate DNS service and now testing a transparent ACE context and HA configuration.One virtual-IP is configured for UDP/53, listening for DNS requests. Behind the VIP, there are 3 DNS server. The next step of our testing process, we have shut down all real-server instance behind the virtual-IP while inspecting DNS clients behaviour. Besides the DNS clients requesting the virtual-IP DNS service need ICMP-destination-unreachable packet to switchover the secondary DNS server.
Can ACE 4710 send ICMP-dest-unreachable?
Thanks in advance!
Regards,
Belabacsi
from Hungary

Unfortunately the 4710 does not send icmp unreachable when a vserver is down.
If you have backup dns service, you can configure it on ace itself.
Gilles.

Ping return a lot of "ICMP Port Unreachable from gateway"

hi all,
continues getting many "ICMP Port unreachable" messages while i ping a host that is within same subnet. both servers are running solaris 10 U6. is there any wrong configuration of IPMP ?
PING rac-dbs-a2: 1024 data bytes
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=0. time=0.830 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=1. time=0.608 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=2. time=0.547 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=3. time=0.611 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=4. time=0.543 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=5. time=0.616 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=6. time=0.663 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=7. time=0.596 ms
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=8. time=0.672 ms ICMP Port Unreachable from gateway rac-dbs-a2 (10.1.3.27) for udp from rac-dbs-c2 (10.1.3.36) to rac-dbs-a2 (10.1.3.27) port
37833
1032 bytes from rac-dbs-a2 (10.1.3.27): icmp_seq=9. time=0.582 ms
----rac-dbs-a2 PING Statistics----
10 packets transmitted, 10 packets received, 0% packet loss round-trip (ms) min/avg/max/stddev = 0.543/0.6268/0.830/0.0828
ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 192.168.1.27 netmask ffffff00 broadcast 192.168.1.255
groupname internal-multipath
bge0:1:
flags=201040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,CoS> mtu 1500 index 2
inet 192.168.1.37 netmask ffffff00 broadcast 192.168.1.255
bge1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 3
inet 172.22.100.27 netmask ffffff00 broadcast 172.22.100.255
groupname smtm-multipath
bge2: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 4
inet 10.1.4.27 netmask ffffff00 broadcast 10.1.4.255
groupname crf-multipath
bge2:1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 4
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
bge3: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 5
inet 10.1.3.27 netmask ffffff00 broadcast 10.1.3.255
groupname rac-multipath
bge3:1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 5
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
ce0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 6
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
groupname internal-multipath
ce1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 7
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
groupname smtm-multipath
ce2:
flags=249000842<BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,INACTIVE,CoS
mtu 0 index 8inet 0.0.0.0 netmask 0
groupname crf-multipath
ce3:
flags=249000842<BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,INACTIVE,CoS
mtu 0 index 9inet 0.0.0.0 netmask 0
groupname rac-multipath
Edited by: hello78 on May 11, 2009 9:02 PM

This isn't a Java question. Try the Solaris forum.

VPN "Destination Unreachable"

Trying to use VPN in Lion (to connect to a Lion Server I configured in another building), when I try to connect, it fails. Viewing console messages on the server shows my requests never arrived. So I used Wireshark to do a packet capture of en0 (my wifi is off). I think I have discovered the problem, but I don't know the solution. The packet capture shows the following error about 30 times in a row each time i try to enable VPN:
Source: 10.0.1.4
Destination: 10.0.1.1
Protocol: ICMP
Info: Destination unreachable (port unreachable)
10.0.1.4 is my Mac and 10.0.1.1 is my AEBS. Why would attempting to initiate VPN cause this error?

Ok, so your "in another building" reference was intended to indicate this is a remote connection, across the internet, and definitely across an insecure connection, and not (as I'd erroneously interpreted it) in a campus network at a somewhat larger school or business site. The "in another building" can be a reference to a different IP subnet within a larger organization's internal network.
All of which means you're not going to be using an IP router to bridge to an outer and trusted network; you'll want a gateway device, and you're probably also stuck with the morass that is NAT. And parts of what I've referenced earlier will be wrong for your requirements.
I'd guess that there's an IP routing configuration issue here. A bad subnet, or a bad gateway address, would be my initial suspicion.
As a first test, switch your iMac to the wireless connection, and see if that works. Get it using the same path as your iPad.
Unless you have a public static IP address, you'll (unfortunately) need NAT here (somewhere). But the question is whether your "modem" is actually a gateway device. Iis your Airport getting a private-block address from that modem device?
If you're getting a private-block address from the modem, then the modem has implemented NAT, or your ISP has implemented NAT gateway somewhere outside of your modem. For instance, AT&T Uverse implements a private NAT address on the "outside" of your local modem configuration, and this then leads to very specific (and somewhat weird) private network set-up requirements for that ISP.
What features does the modem have, and what access into its configuration are you permitted by your ISP?
If your modem is providing gateway features (some do), and particularly if it is providing DHCP and NAT services, then I'd switch the Airport to bridged mode (AP mode), and let the modem deal with NAT and DHCP for your network.
If your modem is providing DHCP and NAT, then switch your iMac to use what the modem is providing, and not what the Airport Express is providing.
Above all, you do NOT want double NAT here.
Though it probably won't help you for this specific modem (unless you can gain control of it directly or via the ISP), I prefer the following general configuration for connecting a small business network to the Internet, when the ISP requires a modem:
The wild and wooly of the Internet,
and which conects to modem (and the "dumber" the better; preferably a modem implemented as a "bridge" and not as a "router", and with as few features and capabilities as I can acquire from the ISP),
and the modem then connects to a gateway device I manage (and which is inherently also a router, and provides the NAT),
the gateway then connects to network switches if and as needed,
and the switch (or the gateway, if that has an embedded switch) connects to WiFi.
And I prefer the gateway implement the NAT and VPN here, and not the WiFi device nor the modem.

Raw Socket always drop packets and return Destination Unreachable

Ho folks,
I have an application program that opens a raw socket to expect for UDP message incoming from the network.
However everytime I receive a package the Solaris 10 OS return a ICMP - Destination (port) unreachable, and no message
is send to my application.
I did test the same application in linux and it worked well, all that I have to do was disable ICMP responses using iptables.
Just to make things clear:
In linux the OS was sending the ICMP - Destionation (port) unreachable, however my program was
receiving the packets anyway. So just to stop those messages I did use the iptables. However, in
Solaris 10 the ICMP response is sending back and no message is forward to my application.
Would your guys help me to solve that?
Thanks in advance

Folks, here I go again...:-)
I have been spent some time, trying to figure out why it is not work. I read in books and internet, that BSD raw sockets DO NOT allow us to receive TCP/UDP packages. However the linux implementation DOES allow. That is because it work in linux but not in solaris.
Given that, such information is 100% true (book: Unix NetworkProgramming, 3rd edition), I would like to ask your guys what I can do to solve my problem.
Basically what I need is create an application that:
1) Allows to bind thousand of sockets at the same time (it is a media server that handles thousand of RTP connections)
This I believe I can do using socket multiplexing (e.g. select() )
2) Read not only the packet data, I need to retrieve the whole packet address (including IP, UDP, Upper Layers...)
When using SOCK_DGRAM with IPPROTO_UDP, I can get the messages but I can't get the IP header
3) Uses something like raw socket to send messages, here I believe I can use raw socket with no problem, is just sending messages
Thanks and Regards

New Install - ICMP Host Unreachable from gateway

Hi team,
I'm configuring a new solaris x86 box for the first time in a long time and I'm running into a problem that has me stumped.
I just installed Solaris 10 v7 on a P4 Dell box with an intel pro1000 adapter loaded.
Installed using ZFS and install went well. I set a static IP of 192.168.1.70 on a proper 192.168.1.x lan.
After install, everything seems to work fine but cannot ping a FQDN such as www.google.com, etc.
at first, I tried to join a local domain - maxximgroup.com and my computer name is set to sunzilla.
Here's my network config files;
sunzilla is set up with static IP = 192.168.1.70
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.70 netmask ffffff00 broadcast 192.168.1.255
ether 0:1b:21:27:56:2c
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
inet6 ::1/128
e1000g0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
inet6 fe80::21b:21ff:fe27:562c/10
ether 0:1b:21:27:56:2c
And /etc/hosts shows host name sunzilla associated w/ 192.168.1.70...
# cat /etc/hosts
# Internet host table
::1 localhost
127.0.0.1 localhost
192.168.1.70 sunzilla loghost
And my resolv.conf file shows my internal DNS routers as well as a 3rd I added (4.2.2.2) just in case...
# cat /etc/resolv.conf
domain maxximgroup.com
nameserver 192.168.1.20
nameserver 192.168.1.22
nameserver 4.2.2.2
search maxximgroup.com
I noticed the /etc/defaultrouter file was MISSING... so I created one pointing to my router...
# cat /etc/defaultrouter
192.168.1.1
And finally, I checked the /etc/nsswitch.conf file and it does indeed show hosts & ipnodes --> files & dns ...
# cat /etc/nsswitch.conf
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# /etc/nsswitch.dns:
# An example file that could be copied over to /etc/nsswitch.conf; it uses
# DNS for hosts lookups, otherwise it does not use any other naming service.
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.
# DNS service expects that an instance of svc:/network/dns/client be
# enabled and online.
passwd: files
group: files
# You must also set up the /etc/resolv.conf file for DNS name
# server lookup. See resolv.conf(4).
hosts: files dns
# Note that IPv4 addresses are searched for in all of the ipnodes databases
# before searching the hosts databases.
ipnodes: files dns
networks: files
protocols: files
rpc: files
ethers: files
netmasks: files
bootparams: files
publickey: files
# At present there isn't a 'files' backend for netgroup; the system will
# figure it out pretty quickly, and won't use netgroups at all.
netgroup: files
automount: files
aliases: files
services: files
printers: user files
auth_attr: files
prof_attr: files
project: files
tnrhtp: files
tnrhdb: files
I can ping local IP addresses ...
# ping 192.168.1.1
192.168.1.1 is alive
But not external addresses ...
# ping 67.15.211.8
ICMP Host Unreachable from gateway sunzilla (192.168.1.70)
for icmp from sunzilla (192.168.1.70) to ns1.siteground168.com (67.15.211.8)
ICMP Host Unreachable from gateway sunzilla (192.168.1.70)
for icmp from sunzilla (192.168.1.70) to ns1.siteground168.com (67.15.211.8)
ICMP Host Unreachable from gateway sunzilla (192.168.1.70)
for icmp from sunzilla (192.168.1.70) to ns1.siteground168.com (67.15.211.8)
ICMP Host Unreachable from gateway sunzilla (192.168.1.70)
for icmp from sunzilla (192.168.1.70) to ns1.siteground168.com (67.15.211.8)
^C#
and naturally, I can ping a FQDN either (confirmed to be pingable on a computer on the same lan) ...
# ping mycloud.local
ping: unknown host mycloud.local
Can anyone provide some guidance pls?

Thanks Robert. You were absolutely on the right track. It turns out that in my "rush" to get my new ZFS "toy" up and running, during the install, I gave Solaris a static address but told it to automatically find the gateway. Oops! When solaris 10 installed, it correctly decided that since it had a static IP, it should assign the gateway as itself! So, naturally, when I ran netstat -m, It showed my gateway as myself! 192.168.1.70 sunzilla.
I'm used to running Solaris on a Sparc platform and I'm a bit uncomfortable with reboots and I figured there would surely be a network restart command somewhere. After finding out that things have now changed in Solaris 10 quite a bit from Solaris 8, I just decided to init 6.
After the system came up, everything was happy : -)
So again, thanks to Robert for helping save the day!

JMS Module, Foreign Server: Destination unreachable

Hi,
In our OSB setup we have 2 weblogic domains (on RHEL5), one for hosting the OSB services and one that is used solely for the purpose of JMS messsaging.
Therefore we have configured a Foreign Server in our JMS Module on the OSB Domain with following config:
* JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
* JNDI Connection URL: t3://fsb-jms1-dev:7901,fsb-jms2-dev:7901
After deploying an EJB that makes use of this module we see following error in our log files every time when starting a Managed Server:
####<Jun 8, 2011 11:36:48 AM CEST> <Warning> <EJB> <esddev148> <osbms1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <11d1def534ea1be0:-27013fcb:1306e9a12ac:-8000-0000000000000016> <13075
25808959> <BEA-010061> <The Message-Driven EJB: MessageLogWriter is unable to connect to the JMS destination: fsb.jms.MessageLoggingQueue. The Error was:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java
.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:64)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java.rmi.ConnectException: Destination unreachab
le; nested exception is:
java.io.IOException: Empty server reply; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:352)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:612)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:563)
at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:789)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:341)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:194)
... 4 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:402)
at weblogic.rjvm.RJVMImpl.ensureConnectionEstablished(RJVMImpl.java:306)
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:350)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:613)
... 30 more
>
I've allready ensured that the managed servers of the jms cluster are reachable by issuing a connect command from WLST (although making the connection can be time consuming)
wls:/offline> connect('weblogic','******','t3://fsb-jms1-dev:7901')
Connecting to t3://fsb-jms1-dev:7901 with userid weblogic ...
Successfully connected to managed Server 'jmsms1' that belongs to domain 'jmsdevdomain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/jmsdevdomain/serverConfig> disconnect()
Disconnected from weblogic server: jmsms1
wls:/offline> connect('weblogic','******','t3://fsb-jms2-dev:7901')
Connecting to t3://fsb-jms2-dev:7901 with userid weblogic ...
Successfully connected to managed Server 'jmsms2' that belongs to domain 'jmsdevdomain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
In my search for a solution I've also read that this could be caused by a bad configured DNS server. Therefore I configured my /etc/nsswitch.conf file to contain only the property files under the parameter hosts.
Following is an extraction of my /etc/hosts file:
10.16.85.50 fsb-jms1-dev.localdomain fsb-jms1-dev
10.16.85.51 fsb-jms2-dev.localdomain fsb-jms2-dev
10.16.85.52 fsb-osb1-dev.localdomain fsb-osb1-dev
10.16.85.53 fsb-osb2-dev.localdomain fsb-osb2-dev
Does anybody have an idea how I can further debug this problem?
Kind Regards,
Davy

Maybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html

BAMAdapter Issue : java.rmi.ConnectException: Destination unreachable;

Hi,
I have installed SOA server and BAM server on same localhost but while calling BAM adapter from the BPEL process it's throwing below error.
*<Jun 24, 2011 6:56:51 PM BST> <Error> <oracle.soa.bpel.engine.ws> <BEA-000000>*
*<got FabricInvocationException java.rmi.ConnectException: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination*
Here are my JNDI configuration :: eis/bam/rmi
HostName     java.lang.String     localhost
InstanceName     java.lang.String     ADCServer1
Password     java.lang.String     *******
PortNumber     java.lang.String     9001
UserName     java.lang.String     weblogic
I have also tried with the eis/bam/soap but it is giving me
javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused
Do i need to modify any configuration file in server?
Please suggest.
Thanks,
Sagar

Hi,
I have installed SOA server and BAM server on same localhost but while calling BAM adapter from the BPEL process it's throwing below error.
*<Jun 24, 2011 6:56:51 PM BST> <Error> <oracle.soa.bpel.engine.ws> <BEA-000000>*
*<got FabricInvocationException java.rmi.ConnectException: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination*
Here are my JNDI configuration :: eis/bam/rmi
HostName     java.lang.String     localhost
InstanceName     java.lang.String     ADCServer1
Password     java.lang.String     *******
PortNumber     java.lang.String     9001
UserName     java.lang.String     weblogic
I have also tried with the eis/bam/soap but it is giving me
javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused
Do i need to modify any configuration file in server?
Please suggest.
Thanks,
Sagar

JTAPI + UDP = ICMP Port Unreachable

Hi,
We're writing an IVR application which register itself as a CTI Route Point. This CTI RP has one line, 2000, which receive the external call (PSTN) from a voice gateway. A customer calls 0800 number, then flows thru PSTN->E1->Gateway->CallManager (2000)->CTI RP.
JTAPI triggers an incoming call event (TermConnRingingEv), I answer this call (terminalConnection.answer()), I receive a TermEv event (CiscoRTPOutputStartedEv), get remote address and port by rtpOutStarted.getRTPOutputProperties() (getRemoteAddress and getRemotePort properties) and start sending RTP audio (CiscoRTPPayload.G711ULAW64K, 160).
Here begins my problems. Testing this scenario with internal calls only, it was 100% perfect! But using external calls (E1->gateway), all the time getRemoteAddress answers the same IP Address (of course, gateway address). But each time there's a different port, one for each call. Usually we have success and the audio comes to final destination: the mobile phone on PSTN; but sometimes the DatagramSocket.send(DatagramPacket) method throws exception "ICMP Port Unreachable" and the call remains active but mute.
There's no pattern for this problem, sometimes it works, sometimes doesn't.
Our CUCM version is 7.1, there's no Unity or IPCC on environment, just CallManager, Gateway and application.
StackTrace:
java.net.PortUnreachableException: ICMP Port Unreachable
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:612)
Thanx!

It means there is no UDP connectivity between whatever host gets the exception and whatever host that socket is connected to. Typically a firewall problem.
The addresses of 0.0.0.0 just mean that the socket is bound to all interfaces, it's not a problem.

Error with SessionBeans:Destination Unreachable

Hi all,
I'm trying to develop a simple Session Bean using Weblogic 8.1.
While deploying i got message as ejbc successful.
But while running client application i got following error.
Please anyone help to resolve this.
Thanks,
latha
E:\slsb>java Client
Exception in thread "main" javax.naming.CommunicationException [Root exception i
s java.net.ConnectException: t3://raghu:7001: Destination unreachable; neste
d exception is:
java.net.SocketException: Invalid argument: connect; No available router
to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:636)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at Client.main(Client.java:12)
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachab
le; nested exception is:
java.net.SocketException: Invalid argument: connect; No available router
to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:296)
... 7 more

Please check the following:
1. Check whether the weblogic is running on the localhost.
2. Check the port address is right or wrong
(I have never used weblogic so I can't tell you how to check it, if you don't know then browse the google)
3. Change the server name to 127.0.0.1 in the client code.
If the server is running perfectly at 127.0.0.1:7001 then there should be no problem. So check this constraints first.
Note: I have used Websphere there are lots of ports, the one I need for lookup in websphere is the BOOTSTRAP_ADDRESS. There are many other ports also. In websphere one can create multiple profile and for that profil;e this prot address varies from 2809,2810... etc.. I don't know whether in weblogic it is called as BOOTSTRAP_ADDRESS or not. But you have ensure that the particular port for weblogic (to perform lookup) is 7001 in your m/c. Please search through google for getting information on how to know the port in weblogic.

ICMPv6 Destination Unreachable (no route to the destination)

I deployed an IPv6 multicast using EIGRP for IPv6, hosts within the network can ping each other and multicast address (FF08::6678 and FF0E::6678); routers can see all routes in the network. However, when video is streamed from server by VLC, client cannot see the SAP announcement. Packets have been captured by Wireshark, there is an error message of ICMPv6 Destination Unreachable (no route to the destination) with the source address of the server and destination address of the client. The cable, EIGRPv6, ping command have been checked. I cannot find the fault why there is such a problem.
Could you please give me advice on the issue.

Try opening the file /etc/ssh_config from the terminal (you will need to use sudo) with the editor of your choice... eg:
sudo emacs /etc/ssh_config
Add the following lines to the end:
AddressFamily inet
BindAddress x.x.x.x
where x.x.x.x is the IP address of your computer behind your router (I use static IPs for consistent results).
Save and see if you don't have better luck with ssh.

ICMP Host Unreachable from gateway localhost (127.0.0.1)

I had a functional zone. But we had an outage and for some reason one of my zones is unreachable. Looks like the problem is that the default route has changed. How can I add a default route to a zone?
Thanks
Manish
--- global zone ---
-bash-3.00# zoneadm list -iv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
2 www running /export/zones/www native shared
4 java running /export/zones/java native shared
--- zone java ---
-bash-3.00# ping 131.247.16.130
ICMP Host Unreachable from gateway localhost (127.0.0.1)
for icmp from localhost (127.0.0.1) to 131.247.16.130
ICMP Host Unreachable from gateway localhost (127.0.0.1)
for icmp from localhost (127.0.0.1) to 131.247.16.130
ICMP Host Unreachable from gateway localhost (127.0.0.1)
for icmp from localhost (127.0.0.1) to 131.247.16.130
-bash-3.00# ifconfig -a
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0:3: flags=4001000842<BROADCAST,RUNNING,MULTICAST,IPv4,DUPLICATE> mtu 1500 index 2
inet 131.247.16.149 netmask ffffff80 broadcast 131.247.16.255
-bash-3.00# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
127.0.0.1 127.0.0.1 UH 4 61 lo0:1
-bash-3.00# route add default 131.247.16.254
add net default: gateway 131.247.16.254: insufficient privileges
--- zone www ---
-bash-3.00# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
default 131.247.16.254 UG 1 47
131.247.16.128 131.247.16.131 U 1 13 bge0:2
224.0.0.0 131.247.16.131 U 1 0 bge0:2
127.0.0.1 127.0.0.1 UH 4 108 lo0:2

ifconfig -a will show when you have a duplicated IP address.
It appears along with the text values for the interface flags ie
host-u010|global$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index
1
inet 127.0.0.1 netmask ff000000
bge0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> m
tu 1500 index 2
inet 10.236.93.156 netmask ffffffc0 broadcast 192.168.93.191
groupname data
host-u010|global$
You would see DUPLICATE or DUPLICATED in that field, and the flags would be different. Sorry, I don't have a duplicate IP situation going on right now, but my memory says it looked something like this:
host-u010|global$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index
1
inet 127.0.0.1 netmask ff000000
bge0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,DUPLICATE> m
tu 1500 index 2
inet 10.236.93.156 netmask ffffffc0 broadcast 192.168.93.191
groupname data
host-u010|global$
Cheers,

T3://127.0.0.1:7101: Destination unreachable; -- On jDeveloper 11gR1

I am new to weblogic, and have just installed Oracle Express, WLS, jDeveloper.
After running through the tutorial on 'Building a Web Application with JDeveloper 11g Using EJB, JAP, and JavaServerFaces', following all steps to the letter, I am able to make the DB connections alright, start the integrated server, but once I try running the HRFacadeBean in step 18, but it errors out.
It seems to me that the issue with recognizing the t3 protocol.
I have checked that 127.0.0.1:7101 is up and running as I get the welcome screen when I go to it and there are no errors listed on the server console screen in jDeveloper, but I get this trace in the log:
[EclipseLink/JPA Client] Adding Java options: -javaagent:C:\Oracle\Middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-0.jar
C:\Oracle\Middleware\jdk160_18\bin\javaw.exe -client -classpath C:\Oracle\Middleware\jdeveloper\myWork\.adf;C:\Oracle\Middleware\jdeveloper\myWork\EJBModel\classes;C:\Oracle\Middleware\modules\com.oracle.toplink_1.0.0.0_11-1-1-3-0.jar;C:\Oracle\Middleware\modules\org.eclipse.persistence_1.0.0.0_2-0.jar;C:\Oracle\Middleware\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.toplink_11.1.1\javax.persistence_2.0_preview.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\Oracle\Middleware\modules\javax.jsf_1.0.0.0_1-2.jar;C:\Oracle\Middleware\modules\javax.ejb_3.0.1.jar;C:\Oracle\Middleware\modules\javax.enterprise.deploy_1.2.jar;C:\Oracle\Middleware\modules\javax.interceptor_1.0.jar;C:\Oracle\Middleware\modules\javax.jms_1.1.1.jar;C:\Oracle\Middleware\modules\javax.jsp_1.1.0.0_2-1.jar;C:\Oracle\Middleware\modules\javax.jws_2.0.jar;C:\Oracle\Middleware\modules\javax.activation_1.1.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.mail_1.1.0.0_1-4-1.jar;C:\Oracle\Middleware\modules\javax.xml.soap_1.3.1.0.jar;C:\Oracle\Middleware\modules\javax.xml.rpc_1.2.1.jar;C:\Oracle\Middleware\modules\javax.xml.ws_2.1.1.jar;C:\Oracle\Middleware\modules\javax.management.j2ee_1.0.jar;C:\Oracle\Middleware\modules\javax.resource_1.5.1.jar;C:\Oracle\Middleware\modules\javax.servlet_1.0.0.0_2-5.jar;C:\Oracle\Middleware\modules\javax.transaction_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\Middleware\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\Oracle\Middleware\modules\javax.persistence_1.0.0.0_1-0-2.jar;C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -javaagent:C:\Oracle\Middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-0.jar -Dhttp.proxyHost=proxy.ulalaunch.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts= -Dhttps.proxyHost=proxy.ulalaunch.com -Dhttps.proxyPort=80 -Dhttps.nonProxyHosts= oracle.HRFacadeClient
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at oracle.HRFacadeClient.getInitialContext(HRFacadeClient.java:58)
     at oracle.HRFacadeClient.main(HRFacadeClient.java:13)
Caused by: java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
     ... 9 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     ... 12 more
Process exited with exit code 0.

Hi,
I guess the problem is with below information but I do not know from where they came!? maybe in the jdeveloper you have set the proxy or maybe your localhost is not bind to 127.0.0.1 and you must use your computer name.
Dhttp.proxyHost=proxy.ulalaunch.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts= -Dhttps.proxyHost=proxy.ulalaunch.com -Dhttps.proxyPort=80 -Dhttps.nonProxyHosts= oracle.HRFacadeClient

Destination unreachable; nested exception

Environment:
JDeveloper 11.1.1.3.0
Build JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660
Oracle 12.1.1
JDK 1.6
I got this exception on the '23rd' step of this tutorial
http://www.oracle.com/technology/obe/obe11jdev/ps1/ejb/ejb.html
Thanks for your help.
[EclipseLink/JPA Client] Adding Java options: -javaagent:C:\Oracle\Middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-0.jar
C:\Oracle\Middleware\jdk160_18\bin\javaw.exe -client -classpath C:\JDeveloper\mywork\HR_EJB_JPA_APP\.adf;C:\JDeveloper\mywork\HR_EJB_JPA_APP\EJBModel\classes;C:\Oracle\Middleware\modules\com.oracle.toplink_1.0.0.0_11-1-1-3-0.jar;C:\Oracle\Middleware\modules\org.eclipse.persistence_1.0.0.0_2-0.jar;C:\Oracle\Middleware\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.toplink_11.1.1\javax.persistence_2.0_preview.jar;C:\Oracle\Middleware\modules\javax.jsf_1.0.0.0_1-2.jar;C:\Oracle\Middleware\modules\javax.ejb_3.0.1.jar;C:\Oracle\Middleware\modules\javax.enterprise.deploy_1.2.jar;C:\Oracle\Middleware\modules\javax.interceptor_1.0.jar;C:\Oracle\Middleware\modules\javax.jms_1.1.1.jar;C:\Oracle\Middleware\modules\javax.jsp_1.1.0.0_2-1.jar;C:\Oracle\Middleware\modules\javax.jws_2.0.jar;C:\Oracle\Middleware\modules\javax.activation_1.1.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.mail_1.1.0.0_1-4-1.jar;C:\Oracle\Middleware\modules\javax.xml.soap_1.3.1.0.jar;C:\Oracle\Middleware\modules\javax.xml.rpc_1.2.1.jar;C:\Oracle\Middleware\modules\javax.xml.ws_2.1.1.jar;C:\Oracle\Middleware\modules\javax.management.j2ee_1.0.jar;C:\Oracle\Middleware\modules\javax.resource_1.5.1.jar;C:\Oracle\Middleware\modules\javax.servlet_1.0.0.0_2-5.jar;C:\Oracle\Middleware\modules\javax.transaction_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\Middleware\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\Oracle\Middleware\modules\javax.persistence_1.0.0.0_1-0-2.jar;C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar;C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\oracle\11g\ojdbc6.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-collation.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-lcsd.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-mapping.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-servlet.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-translation.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-utility.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.odl_11.1.1\ojdl.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.dms_11.1.1\dms.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.idm_11.1.1\identitystore.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adfm.jar;C:\Oracle\Middleware\oracle_common\modules\groovy-all-1.6.3.jar;C:\Oracle\Middleware\jdeveloper\adfdt\lib\adf-dt-at-rt.jar;C:\Oracle\Middleware\jdeveloper\adfdt\lib\adf-transactions-dt.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adfdt_common.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\db-ca.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\jdev-cm.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.ldap_11.1.1\ojmisc.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\commons-el.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\jsp-el-api.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\oracle-el.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.security_11.1.1\adf-share-security.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.security_11.1.1\adf-controller-security.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\adf-share-support.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share.ca_11.1.1\adf-share-ca.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share.ca_11.1.1\adf-share-base.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\adflogginghandler.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xmlef_11.1.1\xmlef.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.bali.share_11.1.1\share.jar;C:\Oracle\Middleware\modules\com.bea.core.apache.xercesImpl_2.8.1.jar;C:\Oracle\Middleware\modules\glassfish.jaxb_1.0.0.0_2-1-9.jar;C:\Oracle\Middleware\modules\javax.xml.bind_2.1.1.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -javaagent:C:\Oracle\Middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-0.jar oracle.MovieFacadeClient
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection refused: connect; No available router to destination]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at oracle.MovieFacadeClient.getInitialContext(MovieFacadeClient.java:49)
     at oracle.MovieFacadeClient.main(MovieFacadeClient.java:13)
Caused by: java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection refused: connect; No available router to destination
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
     ... 9 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection refused: connect; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     ... 12 more
Process exited with exit code 0.
Edited by: user13272654 on Jun 18, 2010 5:02 PM

Basically, it can't find the server.
Is the server running?
configured to listen on localhost?
try 3://127.0.0.1:7001 instead.
Check the port the server is listening on.
Pete

Destination unreachable exception ..???

Dear Sirs/Madam,
While restarting web logic managed servers in a clusters; we encountered below shown errors:
"avax.naming.CommunicationException. Root exception is java.net.ConnectException: t3://myservername.com:8100: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination"
We are running 4 managed servers in one cluster. One cluster spans 2 physical servers. Thus each box has 2 managed servers.
The cluster is running on weblogic 7.x on hpux 11i.
Please suggest what are the possible root cause of this exception and what are the mitigations ?
Thanks,
Shiv

Basically, it can't find the server.
Is the server running?
configured to listen on localhost?
try 3://127.0.0.1:7001 instead.
Check the port the server is listening on.
Pete

PXE DHCP ICMP:Destination Unreachable Message

Similar Messages

Maybe you are looking for