# Sycnthing doesn't work at my work network

**URL:** https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878
**Category:** Support
**Created:** [September 27, 2024, 1:48pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878 "2024-09-27T13:48:31Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![Qka](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/q/85e7bf/32.png) [@Qka](https://forum.syncthing.net/u/Qka)
#### Post date: [September 27, 2024, 1:48pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/1 "2024-09-27T13:48:31Z")

</div>

Hello, I’ve got a computer at home (a Raspberry Pi, which works as a 100% online device), an Android device and a second computer at work. The problem is, ST doesn’t synchronize file at work. I suspect it is blocked in some way by IT (intentionally or not).

Is it any way to make it working (without writing applications to the IT department)?

Below I am posting the fragment of the log:

```plaintext
[KDLVY] 2024/09/27 14:27:35 INFO: Established secure connection to KPZDDEK at 192.168.97.139:53631-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHJ4VK9087OE6TTU9N22VEL0
[KDLVY] 2024/09/27 14:27:35 INFO: Device KPZDDEK client is "syncthing v1.17.0" named "malinka" at 192.168.97.139:53631-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHJ4VK9087OE6TTU9N22VEL0
[KDLVY] 2024/09/27 14:27:41 INFO: Lost primary connection to KPZDDEK at 192.168.97.139:53631-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHJ4VK9087OE6TTU9N22VEL0: reading message: read tcp 192.168.97.139:53631->45.119.155.29:443: wsarecv: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta. (0 remain)
[KDLVY] 2024/09/27 14:27:41 INFO: Connection to KPZDDEK at 192.168.97.139:53631-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHJ4VK9087OE6TTU9N22VEL0 closed: reading message: read tcp 192.168.97.139:53631->45.119.155.29:443: wsarecv: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta.
[KDLVY] 2024/09/27 14:27:41 INFO: Puller (folder "eMka" (gcv7b-nwhww), item "ZGP-2024-09-26__19-08.mp3"): syncing: no connected device has the required version of this file
[KDLVY] 2024/09/27 14:27:41 INFO: Puller (folder "eMka" (gcv7b-nwhww), item "PDWI-2024-09-26__21-00.mp3"): syncing: no connected device has the required version of this file
[KDLVY] 2024/09/27 14:27:41 INFO: "eMka" (gcv7b-nwhww): Failed to sync 2 items
[KDLVY] 2024/09/27 14:27:41 INFO: Folder "eMka" (gcv7b-nwhww) isn't making sync progress - retrying in 16m5s.
[KDLVY] 2024/09/27 14:37:25 INFO: Established secure connection to KPZDDEK at 192.168.97.139:53722-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHK7B8QTHTOAD4KEKE5KSC92
[KDLVY] 2024/09/27 14:37:25 INFO: Device KPZDDEK client is "syncthing v1.17.0" named "malinka" at 192.168.97.139:53722-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHK7B8QTHTOAD4KEKE5KSC92
[KDLVY] 2024/09/27 14:37:27 INFO: Lost primary connection to KPZDDEK at 192.168.97.139:53722-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHK7B8QTHTOAD4KEKE5KSC92: reading message: read tcp 192.168.97.139:53722->45.119.155.29:443: wsarecv: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta. (0 remain)
[KDLVY] 2024/09/27 14:37:27 INFO: Connection to KPZDDEK at 192.168.97.139:53722-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHK7B8QTHTOAD4KEKE5KSC92 closed: reading message: read tcp 192.168.97.139:53722->45.119.155.29:443: wsarecv: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta.
[KDLVY] 2024/09/27 14:37:27 INFO: Puller (folder "eMka" (gcv7b-nwhww), item "PDWI-2024-09-26__21-00.mp3"): syncing: no connected device has the required version of this file
[KDLVY] 2024/09/27 14:37:27 INFO: Puller (folder "eMka" (gcv7b-nwhww), item "ZGP-2024-09-26__19-08.mp3"): syncing: no connected device has the required version of this file
[KDLVY] 2024/09/27 14:37:27 INFO: "eMka" (gcv7b-nwhww): Failed to sync 2 items
[KDLVY] 2024/09/27 14:37:27 INFO: Folder "eMka" (gcv7b-nwhww) isn't making sync progress - retrying in 16m1s.
[KDLVY] 2024/09/27 14:48:36 INFO: Established secure connection to KPZDDEK at 192.168.97.139:53853-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHLECSHC70GJR4N35UQELAUQ
[KDLVY] 2024/09/27 14:48:36 INFO: Device KPZDDEK client is "syncthing v1.17.0" named "malinka" at 192.168.97.139:53853-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHLECSHC70GJR4N35UQELAUQ
[KDLVY] 2024/09/27 14:48:38 INFO: Lost primary connection to KPZDDEK at 192.168.97.139:53853-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHLECSHC70GJR4N35UQELAUQ: reading message: read tcp 192.168.97.139:53853->45.119.155.29:443: wsarecv: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta. (0 remain)
[KDLVY] 2024/09/27 14:48:38 INFO: Connection to KPZDDEK at 192.168.97.139:53853-45.119.155.29:443/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-2VSHLECSHC70GJR4N35UQELAUQ closed: reading message: read tcp 192.168.97.139:53853->45.119.155.29:443: wsarecv: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta.
[KDLVY] 2024/09/27 14:48:38 INFO: Puller (folder "eMka" (gcv7b-nwhww), item "ZGP-2024-09-26__19-08.mp3"): syncing: no connected device has the required version of this file
[KDLVY] 2024/09/27 14:48:38 INFO: Puller (folder "eMka" (gcv7b-nwhww), item "PDWI-2024-09-26__21-00.mp3"): syncing: no connected device has the required version of this file
[KDLVY] 2024/09/27 14:48:38 INFO: "eMka" (gcv7b-nwhww): Failed to sync 2 items
[KDLVY] 2024/09/27 14:48:38 INFO: Folder "eMka" (gcv7b-nwhww) isn't making sync progress - retrying in 16m1s.

```

---

<div class="post-metadata">

### Author: ![chaos](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/c/9d8465/32.png) [@chaos](https://forum.syncthing.net/u/chaos)
#### Post date: [September 27, 2024, 5:34pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/2 "2024-09-27T17:34:06Z")

</div>

Keep in mind that I’m suggesting technical solutions; I do not know your employer’s policies nor can I give you any sort of legal advice. Don’t do anything that can get yourself in trouble.

One option would be to use a mesh VPN; I use NordVPN and Tailscale seems quite popular here. Getting Syncthing working over Nord’s Meshnet was incredibly easy for me.

Another option would be to turn on Global Discovery and also Enable Relaying (both for your device at home and your device at work). If those are on now, that’s an indicator that your employer’s IT department is blocking the traffic deliberately.

---

<div class="post-metadata">

### Author: ![mraneri](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/m/b19c9b/32.png) [@mraneri](https://forum.syncthing.net/u/mraneri)
#### Post date: [September 27, 2024, 6:21pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/3 "2024-09-27T18:21:44Z")

</div>

Unauthorized VPNs are against pretty much any sane IT department’s policies.

Make sure the nodes outside the company network are reachable. Port forwarded or otherwise. Probably the only way you’re gonna make a connection is if the work machine is calling out to the other machines.

If IT is blocking there’s probably a reason.

---

<div class="post-metadata">

### Author: ![bt90](https://forum.syncthing.net/user_avatar/forum.syncthing.net/bt90/32/18565_2.png) [@bt90](https://forum.syncthing.net/u/bt90)
#### Post date: [September 27, 2024, 7:30pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/4 "2024-09-27T19:30:46Z")

</div>

Always work _with_ your corporate IT and not against them.

---

<div class="post-metadata">

### Author: ![acolomb](https://forum.syncthing.net/user_avatar/forum.syncthing.net/acolomb/32/11343_2.png) [@acolomb](https://forum.syncthing.net/u/acolomb)
#### Post date: [September 27, 2024, 9:23pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/5 "2024-09-27T21:23:46Z")

</div>

When they ask you for “a list of IP addresses to white-list”, that’s when you know there is no more progress in sight.

---

<div class="post-metadata">

### Author: ![Qka](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/q/85e7bf/32.png) [@Qka](https://forum.syncthing.net/u/Qka)
#### Post date: [September 30, 2024, 6:17am UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/6 "2024-09-30T06:17:01Z")

</div>

Thank you for your reply!

VPN is what I’ve already tried, just to check if the problem may be caused by some blocking imposed by the IT department (nota bene, I used NordVPN 😉 ). And over the VPN Syncthing works.

About Global Discovery and Relaying - as far as I know - I have both options enabled.

---

<div class="post-metadata">

### Author: ![Qka](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/q/85e7bf/32.png) [@Qka](https://forum.syncthing.net/u/Qka)
#### Post date: [September 30, 2024, 6:19am UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/7 "2024-09-30T06:19:05Z")

</div>

I have no influence on port forwarding performed by the IT department. But I’ll try to ask them anyway. Thank you!

---

<div class="post-metadata">

### Author: ![Qka](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/q/85e7bf/32.png) [@Qka](https://forum.syncthing.net/u/Qka)
#### Post date: [September 30, 2024, 6:20am UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/8 "2024-09-30T06:20:55Z")

</div>

100% agree!

---

<div class="post-metadata">

### Author: ![Qka](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/q/85e7bf/32.png) [@Qka](https://forum.syncthing.net/u/Qka)
#### Post date: [September 30, 2024, 6:21am UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/9 "2024-09-30T06:21:33Z")

</div>

Sorry, I don’t get it?..

---

<div class="post-metadata">

### Author: ![acolomb](https://forum.syncthing.net/user_avatar/forum.syncthing.net/acolomb/32/11343_2.png) [@acolomb](https://forum.syncthing.net/u/acolomb)
#### Post date: [September 30, 2024, 10:43am UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/10 "2024-09-30T10:43:01Z")

</div>

Just my usual rant about corporate IT departments often locking down stuff blindly and not considering network usage patterns that are beyond searching Google, browsing some web sites, and their own internal applications. Especially the thought that IP addresses can be used as criteria to separate good from bad behavior, is still very common but IMHO very outdated.

---

<div class="post-metadata">

### Author: ![Qka](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/q/85e7bf/32.png) [@Qka](https://forum.syncthing.net/u/Qka)
#### Post date: [September 30, 2024, 3:45pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/11 "2024-09-30T15:45:51Z")

</div>

Yeah… I write to them. If everything goes well, I’ll now more details shortly. Thanks!

---

<div class="post-metadata">

### Author: ![system](https://forum-uploads.syncthingcdn.net/original/2X/0/0b50e0a202b22ae6a67190759e8c868805b8ed9f.png) [@system](https://forum.syncthing.net/u/system)
#### Post date: [October 30, 2024, 3:46pm UTC](https://forum.syncthing.net/t/sycnthing-doesnt-work-at-my-work-network/22878/12 "2024-10-30T15:46:05Z")

</div>

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