# Why Are Remote Devices Disconnected?

**URL:** https://forum.syncthing.net/t/why-are-remote-devices-disconnected/19547
**Category:** Support
**Created:** [December 28, 2022, 5:22pm UTC](https://forum.syncthing.net/t/why-are-remote-devices-disconnected/19547 "2022-12-28T17:22:53Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![bwa11](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/b/e9a140/32.png) [@bwa11](https://forum.syncthing.net/u/bwa11)
#### Post date: [December 29, 2022, 12:06am UTC](https://forum.syncthing.net/t/why-are-remote-devices-disconnected/19547/15 "2022-12-29T00:06:01Z")

</div>

Thanks for your help. I found the solution to the problem.

I looked at another post on the same issue and found something interesting.

> [@Remote devices showing disconnected](https://forum.syncthing.net/t/remote-devices-showing-disconnected/11251/13):
>
> Hard coding ip addresses on every side and potentially removing dynamic from addresses it will make it connect faster, as it can avoid discovery, yet it will still potentially be in the minutes, as the timeouts for old connections are long, as are the reconnect intervals. Also, devices disconnecting and reconnecting when you add folders is expected as this is how the implementation resets the state of what we believe the cluster should look like, so there is not much you can do there.

It is possible to specify the devices by IP address and port instead of “dynamic”. That way devices connect faster. In the Remote Devices \> Edit \> Advanced, I deleted the word “dynamic” and added tcp://192.168.0.33:22022. On the other host I added tcp://192.168.0.34:22022 and they connected instantly. I no longer see the word “Disconnected”.

Client A: 192.168.0.33

Client B: 192.168.0.34

Everything is working fine now.

---

_[View the full topic](https://forum.syncthing.net/t/why-are-remote-devices-disconnected/19547)._
