Problem when connect from windows to unix

I installed openJMS on unix.  It works well with the local tomcat (installed
in the same unix box), I can send/receive messages to/from a queue.  But
when I try to connect from tomcat on windows I got an exeption error:

javax.naming.CommunicationException: Failed to get registry service for URL:
tcp://999.999.999.999:3035 [Root exception is java.rmi.ConnectIOException:
Failed to create connection; nested exception is: 
	org.exolab.jms.net.connector.ConnectException: Failed to connect to
999.999.999.999:3035]
	at
org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContextFactory.java:146)
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
	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 SimplePublisher.doGet(SimplePublisher.java:46)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
	at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
	at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
	at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
	at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
	at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
	at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
	at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
	at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
	at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
	at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
	at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
	at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
	at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
	at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
	at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
	at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
	at java.lang.Thread.run(Thread.java:534)
Caused by: java.rmi.ConnectIOException: Failed to create connection; nested
exception is: 
	org.exolab.jms.net.connector.ConnectException: Failed to connect to
999.999.999.999:3035
	at org.exolab.jms.net.orb.Locator.getProxy(Locator.java:137)
	at org.exolab.jms.net.orb.Locator.getRegistry(Locator.java:103)
	at org.exolab.jms.net.orb.DefaultORB.getRegistry(DefaultORB.java:285)
	at org.exolab.jms.client.net.SharedORB.getRegistry(SharedORB.java:121)
	at
org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContextFactory.java:144)
	... 31 more
Caused by: org.exolab.jms.net.connector.ConnectException: Failed to connect
to 999.999.999.999:3035
	at
org.exolab.jms.net.socket.SocketManagedConnection.createSocketProtected(SocketManagedConnection.java:268)
	at
org.exolab.jms.net.socket.SocketManagedConnection.createSocket(SocketManagedConnection.java:182)
	at
org.exolab.jms.net.socket.SocketManagedConnection.<init>(SocketManagedConnection.java:114)
	at
org.exolab.jms.net.tcp.TCPManagedConnection.<init>(TCPManagedConnection.java:75)
	at
org.exolab.jms.net.tcp.TCPManagedConnectionFactory.createManagedConnection(TCPManagedConnectionFactory.java:98)
	at
org.exolab.jms.net.connector.DefaultConnectionPool.createManagedConnection(DefaultConnectionPool.java:233)
	at
org.exolab.jms.net.connector.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:140)
	at
org.exolab.jms.net.connector.AbstractConnectionFactory.getConnection(AbstractConnectionFactory.java:167)
	at
org.exolab.jms.net.connector.AbstractConnectionManager.getConnection(AbstractConnectionManager.java:208)
	at org.exolab.jms.net.orb.Locator.getProxy(Locator.java:131)
	... 35 more

With 999.999.999.999 is the real ip address.
What should I do to fix the problem?
Please help me... it's urgent

Thanks in advance
-- 
View this message in context: http://www.nabble.com/Problem-when-connect-from-windows-to-unix-tf3488913.html#a9743032
Sent from the OpenJMS - User mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV