# Enterprise Search running on a docker container can't connect to Elasticsearch running as a service on windows **URL:** \ **Category:** Elasticsearch\ **Tags:** docker\ **Created:** [May 31, 2023, 7:51am UTC](https://discuss.elastic.co/t/enterprise-search-running-on-a-docker-container-cant-connect-to-elasticsearch-running-as-a-service-on-windows/334761 "2023-05-31T07:51:30Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [May 31, 2023, 11:54am UTC](https://discuss.elastic.co/t/enterprise-search-running-on-a-docker-container-cant-connect-to-elasticsearch-running-as-a-service-on-windows/334761/2 "2023-05-31T11:54:18Z")
Hi @Mtuni_Globbal Welcome to the community. This is a docker networking issue. See this same issue most likely > [@Filebeat Docker - Elasticsearch Host Issue](https://discuss.elastic.co/t/filebeat-docker-elasticsearch-host-issue/320083/2): > > Hi @mwsprotte Welcome to the community! Docker Networking Issue not Elastic... Another explanation Might be worth reading... if you are new to docker try using host.docker.internal docker run \ --net=elastic docker.elastic.co/beats/filebeat:7.17.4 \ setup -E setup.kibana.host=host.docker.internal:5601 \ -E output.elasticsearch.hosts=["https://host.docker.internal:9200"] try using `elasticsearch.host: http://host.docker.internal:9200` --- _[View the full topic](https://discuss.elastic.co/t/enterprise-search-running-on-a-docker-container-cant-connect-to-elasticsearch-running-as-a-service-on-windows/334761)._