cancel
Showing results for 
Search instead for 
Did you mean: 

Cant connect to remote SUP Server from Unwired Workspace

Former Member
0 Kudos

We have a SUP Server running. I can connect to Sybase Control Center from my local machine with a FQDN and from Unwired Workspace which is running on the same machine on which the SUP Server is running. The FQDN is not an internet domain. I only added that domain name (IFSV29.ifl.local) to my local hosts file. I can also ping the domain name successfully. But I can't connect to the remote SUP server from my Unwired Workspace which is running on my local machine. It times out after a long time (several minutes). I observed that if I choose a non existing domain name or other wrong settings, that connection fails right away with an exception. But with the correct settings it just tries to connect for a really long time. So I think it can find the remote SUP server but something prevents a connection.

Does anyone has an idea what we should look at?

Kind Regards,

Rene

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

HI Rene,

Check your fire wall setting and close the firewall settings and and manually add the the port 8283 in the service file. and save the setting.

and try to open SCC now in your browser with IP add of the SUP host server.

Hope this helps

Regards

APS

Former Member
0 Kudos

Hi APS,

I can connect to SCC. The problem is something different. Please see my original post at the top.

Regards

Rene

Former Member
0 Kudos

Hello Rene,

It might be a firewall problem. Do you have a firewall between your local machine and the SUP server?

If yes, then first you should check if all the required ports are open on the firewall. For that, go on the SCC and navigate to "Servers -> <server host name> -> Properties Tab". There you can find all the fixed ports used by SUP.

Then, to establish a communication between the Unwired Workspace and the server, SUP uses a special protocol that randomly and dynamically choses ports inside a certain range. And it so happens that some firewalls don't support this protocol.  To test this, temporarily open all the ports on your firewall. If the connection still fails, then you have this problem. In this case I'm sorry but the only solution I know is to change your firewall...

Best regards,

Manuel

Former Member
0 Kudos

Hi Manuel,

our firewall doesnt block any port as it is behind a VPN. My local machine is connected to the VPN. We will try from a different local machine now.

Thanks,

Rene

Former Member
0 Kudos

So it could also be your local Windows firewall that blocks some commuincation.

If you haven't done it yet, Try deactivitating it and see what happens.

Former Member
0 Kudos

I dont think it is Firewall. I swichted it off entirely. I still get the same TimeoutException.

com.sybase.uep.admin.client.AdminException: org.omg.CORBA.COMM_FAILURE: java.net.SocketTimeoutException: Read timed out  vmcid: 0x0  minor code: 0  completed: No

          at com.sybase.sup.admin.client.impl.AdminContext.initialize(AdminContext.java:89)

          at com.sybase.sup.admin.client.impl.AdminContext.getInstance(AdminContext.java:35)

          at com.sybase.sup.admin.client.impl.ServerConnectionImpl.<init>(ServerConnectionImpl.java:22)

          at com.sybase.sup.admin.client.impl.ServerConnectionImpl.<init>(ServerConnectionImpl.java:29)

          at com.sybase.uep.admin.client.ServerConnectionManager.ping(ServerConnectionManager.java:191)

          at com.sybase.uep.admin.client.ServerConnectionManager.updateConnectionProperties(ServerConnectionManager.java:98)

          at com.sybase.uep.admin.client.ServerConnectionManager.clusterConnect(ServerConnectionManager.java:68)

          at com.sybase.uep.datasources.uepprofile.UEPServerConnection.checkCompatibility(UEPServerConnection.java:88)

          at com.sybase.uep.datasources.uepprofile.UEPServerConnection.<init>(UEPServerConnection.java:58)

          at com.sybase.uep.datasources.uepprofile.UEPConnectionFactory.createConnection(UEPConnectionFactory.java:16)

          at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(Unknown Source)

          at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(Unknown Source)

          at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(Unknown Source)

          at org.eclipse.datatools.connectivity.ui.PingJob.run(Unknown Source)

          at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: org.omg.CORBA.COMM_FAILURE: java.net.SocketTimeoutException: Read timed out  vmcid: 0x0  minor code: 0  completed: No

          at com.sybase.djc.rmi.iiop.CdrInputStream.read(CdrInputStream.java:1735)

          at com.sybase.djc.rmi.iiop.CdrInputStream.receive_message(CdrInputStream.java:462)

          at com.sybase.djc.rmi.iiop.CdrInputStream_DJC.receive_message(CdrInputStream_DJC.java:2237)

          at com.sybase.djc.rmi.iiop.CdrInputStream.receive_message(CdrInputStream.java:448)

          at com.sybase.djc.rmi.iiop.CdrInputStream_DJC.receive_message(CdrInputStream_DJC.java:2200)

          at com.sybase.djc.rmi.iiop.client.Connection.invoke(Connection.java:415)

          at com.sybase.djc.org.omg.CosNaming.iiop_stubs.NamingContext._is_a(NamingContext.java:63)

          at com.sybase.djc.rmi.iiop.client.ClientNamingContext.init(ClientNamingContext.java:697)

          at com.sybase.djc.rmi.iiop.client.ClientNamingContext.getInstance(ClientNamingContext.java:76)

          at com.sybase.sup.admin.client.impl.AdminContext.initialize(AdminContext.java:82)

          ... 14 more