# Transport Port?
**URL:** https://discuss.elastic.co/t/transport-port/6226
**Category:** Elasticsearch
**Created:** [December 22, 2011, 11:23pm UTC](https://discuss.elastic.co/t/transport-port/6226 "2011-12-22T23:23:30Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Edward\_Giardina](https://discuss.elastic.co/u/Edward_Giardina)
#### Post date: [December 22, 2011, 11:23pm UTC](https://discuss.elastic.co/t/transport-port/6226/1 "2011-12-22T23:23:30Z")
Does anyone know what the port(s) used for the transport client
connections? Our client is in Java and we are receiving the following
stack trace. We have ports 9200 and 9300 open, but we dont know if
there are other ports that need to be open through the firewall. We
are hosting on Rackspace Cloud servers and use Unicast for the ES
standalone instances.
org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:
145)
at
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:
222)
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [December 22, 2011, 11:48pm UTC](https://discuss.elastic.co/t/transport-port/6226/2 "2011-12-22T23:48:12Z")
9200 is the HTTP port. The Java transport client needs to use port 9300 to
connect to the other nodes.
On Fri, Dec 23, 2011 at 1:23 AM, Edward Giardina
[egiardina@servicetask.com](mailto:egiardina@servicetask.com)wrote:
> Does anyone know what the port(s) used for the transport client
> connections? Our client is in Java and we are receiving the following
> stack trace. We have ports 9200 and 9300 open, but we dont know if
> there are other ports that need to be open through the firewall. We
> are hosting on Rackspace Cloud servers and use Unicast for the ES
> standalone instances.
>
> org.elasticsearch.client.transport.NoNodeAvailableException: No node
> available
> at
>
> org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:
> 145)
> at
>
> org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:
> 222)
---
### Author:  [@Edward\_Giardina](https://discuss.elastic.co/u/Edward_Giardina)
#### Post date: [December 22, 2011, 11:52pm UTC](https://discuss.elastic.co/t/transport-port/6226/3 "2011-12-22T23:52:09Z")
Thanks. Since our ES cluster is setup to use unicast, does that mean
the java api clients also need to be configured to use unicast when
connecting to the cluster?
On Dec 22, 6:48 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> 9200 is the HTTP port. The Java transport client needs to use port 9300 to
> connect to the other nodes.
>
> On Fri, Dec 23, 2011 at 1:23 AM, Edward Giardina
> [egiard...@servicetask.com](mailto:egiard...@servicetask.com)wrote:
>
> > Does anyone know what the port(s) used for the transport client
> > connections? Our client is in Java and we are receiving the following
> > stack trace. We have ports 9200 and 9300 open, but we dont know if
> > there are other ports that need to be open through the firewall. We
> > are hosting on Rackspace Cloud servers and use Unicast for the ES
> > standalone instances.
>
> > org.elasticsearch.client.transport.NoNodeAvailableException: No node
> > available
> > at
>
> > org.elasticsearch.client.transport.TransportClientNodesService.execute(Tran sportClientNodesService.java:
> > 145)
> > at
>
> > org.elasticsearch.client.transport.support.InternalTransportIndicesAdminCli ent.create(InternalTransportIndicesAdminClient.java:
> > 222)
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [December 22, 2011, 11:58pm UTC](https://discuss.elastic.co/t/transport-port/6226/4 "2011-12-22T23:58:59Z")
Not when you use the TransportClient.
On Fri, Dec 23, 2011 at 1:52 AM, Edward Giardina
[egiardina@servicetask.com](mailto:egiardina@servicetask.com)wrote:
> Thanks. Since our ES cluster is setup to use unicast, does that mean
> the java api clients also need to be configured to use unicast when
> connecting to the cluster?
>
> On Dec 22, 6:48 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
>
> > 9200 is the HTTP port. The Java transport client needs to use port 9300
> > to
> > connect to the other nodes.
> >
> > On Fri, Dec 23, 2011 at 1:23 AM, Edward Giardina
> > [egiard...@servicetask.com](mailto:egiard...@servicetask.com)wrote:
> >
> > > Does anyone know what the port(s) used for the transport client
> > > connections? Our client is in Java and we are receiving the following
> > > stack trace. We have ports 9200 and 9300 open, but we dont know if
> > > there are other ports that need to be open through the firewall. We
> > > are hosting on Rackspace Cloud servers and use Unicast for the ES
> > > standalone instances.
> >
> > > org.elasticsearch.client.transport.NoNodeAvailableException: No node
> > > available
> > > at
> >
> > >
>
> org.elasticsearch.client.transport.TransportClientNodesService.execute(Tran
> sportClientNodesService.java:
>
> > > 1.
> > >
> > > at
> >
> > >
>
> org.elasticsearch.client.transport.support.InternalTransportIndicesAdminCli
> ent.create(InternalTransportIndicesAdminClient.java:
>
> > > 1.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 3:44am UTC](https://discuss.elastic.co/t/transport-port/6226/5 "2017-07-06T03:44:28Z")