Skip to content
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.

Can't connect when running on different networks #12

Open
Sopor opened this issue May 11, 2019 · 1 comment
Open

Can't connect when running on different networks #12

Sopor opened this issue May 11, 2019 · 1 comment
Labels
pending waiting for later assesment

Comments

@Sopor
Copy link

Sopor commented May 11, 2019

I run my computers on 192.168.0 and my WiFi on 192.168.1 and i can't get it to work. If i use other apps i can connect but TrebleShot seems to not work. I haven't confirmed that TrebleShot work proper yet so maybe someone else can verify that TrebleShot do work and can send files if running on the same network.

I use Total Commander from my phone and i can connect to my computers over LAN, but maybe something else is needed in TrebleShot to get it to work?

I tried to send a file to my computer but it couldn't connect to 192.168.0.200, but it seems that Share via browser worked. I entered http://192.168.1.113:58732 in my web browser on my computer and i was able to download the file.

@velitasali
Copy link
Member

Hm. It looks like another bridging issue. My guess is that your Wi-Fi router is connected to another router. So when you make requests from the main router say from a computer connected to it with a cable, the request for the 192.168.1.* can route to the devices connected to Wi-Fi router because it is known a route for the main router, however when a device tries to connect from the Wi-Fi router to the main router the DNS is getting in the way and it tries to connect to it as if it is over the internet.

This is my assumption since you can connect to the web share portal.

@velitasali velitasali added the pending waiting for later assesment label Sep 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending waiting for later assesment
Projects
None yet
Development

No branches or pull requests

2 participants