# Winlogbeat connecting to server then times out

**URL:** <https://discuss.elastic.co/t/winlogbeat-connecting-to-server-then-times-out/140787>\
**Category:** Beats\
**Tags:** winlogbeat\
**Created:** [July 19, 2018, 6:26pm UTC](https://discuss.elastic.co/t/winlogbeat-connecting-to-server-then-times-out/140787 "2018-07-19T18:26:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stephen\_Meier](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@Stephen\_Meier](https://discuss.elastic.co/u/Stephen_Meier)\
**Post date:** [July 19, 2018, 6:26pm UTC](https://discuss.elastic.co/t/winlogbeat-connecting-to-server-then-times-out/140787/1 "2018-07-19T18:26:46Z")

</div>

I am really beating my head against the wall with this one. I have logstash (6.3.0) ingesting winlogbeat (6.3.0) events. However, whenever winlogbeat tries to upload to the logstash server I get

2018-07-19T11:17:38.466-0700 ERROR logstash/async.go:235 Failed to publish events caused by: read tcp 192.168:56169-\>10.2.0.59:5060: i/o timeout  
2018-07-19T11:17:38.486-0700 ERROR logstash/async.go:235 Failed to publish events caused by: client is not connected  
2018-07-19T11:17:39.491-0700 ERROR pipeline/output.go:92 Failed to publish events: client is not connected

I am able to connect to the port using test-networkconnection.

What am I missing?

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [July 20, 2018, 4:46am UTC](https://discuss.elastic.co/t/winlogbeat-connecting-to-server-then-times-out/140787/2 "2018-07-20T04:46:09Z")

</div>

> [@Stephen\_Meier](#):
>
> What am I missing?

Could you please share the output config you are using with Winlogbeat and the input config on Logstash.

You should also try the build-in test command.

`PS C:\Program Files\Winlogbeat > .\winlogbeat.exe test output`

---

<div class="post-metadata">

**Author:** ![Stephen\_Meier](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@Stephen\_Meier](https://discuss.elastic.co/u/Stephen_Meier)\
**Post date:** [July 24, 2018, 4:44pm UTC](https://discuss.elastic.co/t/winlogbeat-connecting-to-server-then-times-out/140787/3 "2018-07-24T16:44:08Z")

</div>

The odd thing is that I changed the ports from 5060 to 4060 and it started working. I think that there was something in the Firewall that was doing something to the traffic. It is a FortiGate firewall.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 21, 2018, 4:51pm UTC](https://discuss.elastic.co/t/winlogbeat-connecting-to-server-then-times-out/140787/4 "2018-08-21T16:51:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.