# Add Host in same private network

**URL:** <https://forums.suse.com/t/add-host-in-same-private-network/10363>\
**Category:** Rancher 1.x\
**Created:** [May 10, 2018, 11:58am UTC](https://forums.suse.com/t/add-host-in-same-private-network/10363 "2018-05-10T11:58:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![asseeger](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@asseeger](https://forums.suse.com/u/asseeger)\
**Post date:** [May 10, 2018, 11:58am UTC](https://forums.suse.com/t/add-host-in-same-private-network/10363/1 "2018-05-10T11:58:28Z")

</div>

We have two CentOS VMs running in an ESXi environment.  
On `centos01 192.168.20.20` we have Rancher 1.6 up and running.  
Now I want to add `centos02 192.168.20.21` as a host with this command:

```auto
sudo docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock\
 -v /var/lib/rancher:/var/lib/rancher rancher/agent:v1.2.10\
http://192.168.20.20:8080/v1/scripts/CC2CF0AC9A34321C63FC:1514678400000:uZJHQdGE51f6w7N5J7Zr78AYzg

```

After doing that, in the hosts overview host `centos01` shows its docker0 IP `172.17.01` whereas `centos02` shows its ens192 IP `192.168.20.21`. I suppose they should be in the same range, shouldn’t they?

I can also see host `centos02` never being healthy for all its containers – as far as I can tell they cannot communicate.

Could somebody point me in the right direction here?

---

<div class="post-metadata">

**Author:** ![asseeger](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@asseeger](https://forums.suse.com/u/asseeger)\
**Post date:** [May 11, 2018, 5:18am UTC](https://forums.suse.com/t/add-host-in-same-private-network/10363/2 "2018-05-11T05:18:54Z")

</div>

**Resolved** my issue by going over the implementation of an environment again. For some reason I had activated the server as a worker. In my new cattle environment I set up a server and 3 workers and now it seems to work.