# Cannot telnet the dedicated master nodes on port 9200 after configuration
**URL:** https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928
**Category:** Elasticsearch
**Created:** [October 13, 2016, 11:21am UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928 "2016-10-13T11:21:49Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@ANU\_SARA\_VARGHESE](https://discuss.elastic.co/u/ANU_SARA_VARGHESE)
#### Post date: [October 13, 2016, 11:21am UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928/1 "2016-10-13T11:21:50Z")
Hi,
I want an architecture with three dedicated master node and 4 dedicated data node with one Load balance node (all in one cluster). For this I configured the the first dedicated master node
node.data: false
When I did the same configuration for the next master node I am not able to telnet the node on port 9200 (I get a Connection refused error).
How can I create 3 dedicated master node in elasticsearch within cluster along with 4 dedicated data nodes?
I had even set the discovery.zen.minimum\_master\_nodes: 2
Still I am facing this issue?
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [October 13, 2016, 11:29am UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928/2 "2016-10-13T11:29:26Z")
With the default configuration ES only listens on the loopback interface. Make sure you have adjusted the network.host setting.
[https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html)
---
### Author:  [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [October 13, 2016, 11:36am UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928/3 "2016-10-13T11:36:28Z")
Hard to tell from here, but maybe it is a binding problem? By default
elasticsearch binds to local host only. I'd you configure it to bind to a
non-local address then it'll just bind to that address. You can configure
it to bind to both the non-local address and local host by listing both as
a yaml array.
You may also want to check with `lsof`.
---
### Author:  [@ANU\_SARA\_VARGHESE](https://discuss.elastic.co/u/ANU_SARA_VARGHESE)
#### Post date: [October 13, 2016, 12:38pm UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928/4 "2016-10-13T12:38:39Z")
Hi,
I have bind the local address.
network.host: x.x.x.x # IP of the particular node. It's private IP
discovery.zen.ping.unicast.hosts: [all the master nodes and data nodes]
---
### Author:  [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [October 13, 2016, 2:48pm UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928/5 "2016-10-13T14:48:29Z")
Then it should work fine. Just make sure to telnet to `x.x.x.x` instead of `localhost`. If you can't do it from the other machine then I expect a networking issue. You can use `lsof` to figure out if Elasticsearch has bound to the right port on that address.
---
### Author:  [@ANU\_SARA\_VARGHESE](https://discuss.elastic.co/u/ANU_SARA_VARGHESE)
#### Post date: [October 14, 2016, 6:17am UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928/6 "2016-10-14T06:17:50Z")
Hi Nik,
I tried lsof . I could see the established connection between the data and master nodes only when I don't specify
node.data: false
in the configuration.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:12pm UTC](https://discuss.elastic.co/t/cannot-telnet-the-dedicated-master-nodes-on-port-9200-after-configuration/62928/7 "2017-07-05T22:12:28Z")