port not opening

[rajesh73]

Hi

I have HP-UX 11.11. when iam opening one particilar port i am getting below error.

C:\Documents and Settings\>telnet 200.81.1.12 1515
Connecting To 200.81.1.12...Could not open connection to the host, on port 1515: Connect failed

when iam opening another port 1055, it is working fine

Regds
Rajesh

[Sachin Kumbla · Accepted solution]

Hi

Do you have access on the destination client (200.81.1.12) from your source server on port 1515.



Rgds.,
Sachin Kumbla.

[rajesh73]

actullay 200.81.1.12 (HP-UX server) is a server iam trying to connect from normal windows pc from command prompt.

and then i tried to connect another port 1055 it is connecting but when iam trying to connect 1515 i cant able.

what setting i have change in my server (200.81.1.12)

1515 port is used for catia application, from lan & wan i can able work catia application, from vpn i cant able to use catia

[Sachin Kumbla]

Hi

There may be a firewall between your windows machine & the server.
You need to take the firewall acces from your windows machine to the server on port 1515.

You can chk with your network team.


Rgds.,
Sachin Kumbla.

[rajesh73]

If u don,t mind

yes allready i told to our netwok & wan team they are blaming the problem with unix server. eventhough i added the port in /etc/services.

Thanks & Regds
Rajesh

[Horia Chirculescu]

Hello,

Do you have a station directly connected in the same LAN as your server? If the port would appear to be closed from this station, maybe you have a firewall on your HP-UX server.

Horia.

[rajesh73]

Hi Horia.

iam not configured any firewall in server. see i can able to connect application through wan also one state to another state but i can't able to VPN

Regds
Rajesh

[Horia Chirculescu]

> from vpn i cant able to use catia

Did you checked your VPN settings? Maybe the VPN is blocking connections to that port.

What kind of VPN are you using?

Horia.

[Steven Schweda]

> Connecting To 200.81.1.12...Could not open
> connection to the host, on port 1515:
> Connect failed

I assume that that's Windows-speak for
"Connection refused", which would mean that
no one is listening at port 1515 on the
system at 200.81.1.12.

> 1515 port is used for catia application
> [...]

So, I'd guess that there's some part of
CATIA which you need to start/run.

> yes allready i told to our netwok & wan
> team they are blaming the problem with unix
> server. eventhough i added the port in
> /etc/services.

Adding something to "/etc/services" will not,
by itself, cause any program to start
listening at any particular port.

Curiosity: What, exactly, did you add to
"/etc/services"?

Have you read the CATIA documentation? Did
it tell you to edit "/etc/services", or was
that your own idea?

It's a common misconception that adding
things to "/etc/services" does more than it
does. See, for example, the (unappreciated)
discussion at:

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1409414

A quick Google search for
catia port 1515
suggests that this port is used by the CATIA
license server. Are you running the CATIA
license server? (I suspect not.)

Have you run
netstat -an
on the HP-UX system to see if anyone is
listening at port 1515?

[Horia Chirculescu]

Steven:>Are you running the CATIA
license server? (I suspect not.)

Rajesh already told us on his second post that
from LAN he can use the application, so the daemon must be running and listening on the required port:

>1515 port is used for catia application, from lan & wan i can able work catia application, from vpn i cant able to use catia

Horia.

[Steven E. Protter]

Shalom Rajesh,

A lot of confusion about the term "port open"

Two things need to happen for a port to be "open" in the context that you refer to it.

1) Port 1515 in this case needs an application listening on it. Otherwise you will get connection refused and think the port is closed. netstat -an | grep 1515
Nothing listening, don't bother with the firewall, get the application listening.
2) Network connectivity. That means there must be a network socket between the server in the client. The telnet test you give will after step 1 is dealt with let you know if you can establish a socket.

However if you can not establish a socket, there are a few possible causes. It could be a simple firewall issue. It could be on the server or the client or any router between the two systems.

SEP

[Horia Chirculescu]

>However if you can not establish a socket, there are a few possible causes. It could be a simple firewall issue. It could be on the server or the client or any router between the two systems.

In other words, go to your HP-UX server and issue a

telnet localhost 1515

If this works then your daemon is listening.

Then go to some station from the LAN (can be a windows) and issue:

telnet 1515

If this works then your network is OK.

We already know that when you go on some windows station located somewhere on the VPN (not on LAN) this telnet is not working.

Some daemons have the possibility to listen on only some IP's/interfaces. Maybe the VPN's end from your HP UX part is having another interface virtual or not. The CATIA daemon should be configured to listen also on that interface.

Horia.