Skip to content

Commit f930343

Browse files
authored
feat(faq): add information on setting network to private in Windows (#914)
The issue of Windows devices being unable to connect directly with each other comes up often on the forum. One of them main reasons for the problem is Windows setting the default network profile to "Public" instead of "Private", which prevents direct connections. Instead of repeating the same instructions on how to change the network profile to "Private" over and over, add a new entry to the FAQ, which we can then use as a reference when needed. Signed-off-by: Tomasz Wilczyński <twilczynski@naver.com>
1 parent 7d2c6e7 commit f930343

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

users/faq-parts/troubleshooting.rst

+11-1
Original file line numberDiff line numberDiff line change
@@ -193,4 +193,14 @@ at the same location. This causes syncthing to attempt an automatic re-creation
193193
it will also reset the database state of this folder. It will be considered a "new" folder, meaning that its files
194194
will be merged with files from remote devices.
195195

196-
Also see the :ref:`marker FAQ <marker-faq>` for more information about the folder marker.
196+
Also see the :ref:`marker FAQ <marker-faq>` for more information about the folder marker.
197+
198+
Why do my Windows computers always connect through a relay?
199+
-----------------------------------------------------------
200+
201+
When connecting to a new network, Windows by default sets its profile to
202+
"Public". While being more secure, this setting commonly prevents applications
203+
like Syncthing from being able to establish direct connections with the device
204+
in question, forcing it to connect through a relay. If you would rather connect
205+
your devices directly, please follow `the official Microsoft instructions on how
206+
to change the network profile to "Private" <https://support.microsoft.com/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9#bkmk_network_profile>`__.

0 commit comments

Comments
 (0)