# Data nodes on windows, Master node in Rancher (docker/k8)
**URL:** https://discuss.elastic.co/t/data-nodes-on-windows-master-node-in-rancher-docker-k8/168264
**Category:** Elasticsearch
**Created:** [February 13, 2019, 5:43pm UTC](https://discuss.elastic.co/t/data-nodes-on-windows-master-node-in-rancher-docker-k8/168264 "2019-02-13T17:43:37Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Dan-Petter\_Jacobsen](https://discuss.elastic.co/u/Dan-Petter_Jacobsen)
#### Post date: [February 13, 2019, 5:43pm UTC](https://discuss.elastic.co/t/data-nodes-on-windows-master-node-in-rancher-docker-k8/168264/1 "2019-02-13T17:43:37Z")
Hi
We are setting up a cluster where two data nodes are in windows.
3 master nodes are inside rancher.
Data (two nodes):
discovery.zen.ping.unicast.hosts: ip.address.to.master, ip.to.other.data
Master (3 pods in on workload called master)
discovery.zen.ping.unicast.hosts: master, ip.to.data1, ip.to.data2
Master nodes can contact data nodes but it send internal ip address and port.
Master is available in network on 10.5.1.0:45621 (random port generated by rancher for testing, port 45621 is a proxy for port 9300 on internal rancher ip:port), and internal rancher ip is 10.50.5.57:9300
The master will then publish 10.50.5.57:9300 to data node and the result is a connection exception when master is trying to answer on that address.
is there a solution to this problem? or do i need to have the entire cluster on the same network?
Regards
Dan-Petter Jacobsen
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [February 13, 2019, 6:23pm UTC](https://discuss.elastic.co/t/data-nodes-on-windows-master-node-in-rancher-docker-k8/168264/2 "2019-02-13T18:23:03Z")
> [@Dan-Petter\_Jacobsen](#):
>
> Data (two nodes):
> discovery.zen.ping.unicast.hosts: ip.address.to.master, ip.to.other.data
>
> Master (3 pods in on workload called master)
> discovery.zen.ping.unicast.hosts: master, ip.to.data1, ip.to.data2
You only need to put the master-eligible nodes in the `discovery.zen.ping.unicast.hosts` setting on each node. There's no need to mention the data nodes there.
> [@Dan-Petter\_Jacobsen](#):
>
> do i need to have the entire cluster on the same network?
Yes. At least, you need each node to be able to access each other node in the cluster using its `transport.publish_host` address.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 13, 2019, 6:23pm UTC](https://discuss.elastic.co/t/data-nodes-on-windows-master-node-in-rancher-docker-k8/168264/3 "2019-03-13T18:23:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.