• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Can't link PC Companion and tablet
#1
Hello, I am having problems connecting my tablet (Samsung/Android) to my PC (Windows 10) trhough Companion. As didn't worked initially, I tried to manually WIFI connect matching IP on both devices. Didn't worked either. Then I make sure to follow all the steps I read on this forum and still don't get the connection. I rebooted the router, checked that my firewall is not blocking Companion and make suere I have free ports such as 888, 16568 and 16569 and still don't get to connect.

Any suggestion or advise will be appreciated!
Reply
#2
Are both devices on the same subnet, meaning they have the same first three octets of the IP address? (such as 192.168.1.X). Do you have a mesh router? If you connect both devices to a WiFi hotspot with your phone, and then try to connect, does that work?

Mike
Reply
#3
(03-21-2025, 09:44 AM)Zubersoft Wrote: Are both devices on the same subnet, meaning they have the same first three octets of the IP address? (such as 192.168.1.X). Do you have a mesh router? If you connect both devices to a WiFi hotspot with your phone, and then try to connect, does that work?

Mike

Thank you very much Mike. Yes, I was trying to connect through a Mesh router. Used the hotspot instead and went through inmediately. .I am new with MSP and still in the process of learning but so far I am amazed with such a superb porduct MSP is. Congrats and thanks for the help!
Reply
#4
I'm glad to hear that. If you can disable the mesh functionality, that might prevent the problem, otherwise it can be difficult if the TCP traffic is being blocked by the router.

Mike
Reply
#5
If I could piggy back onto this as my problem is the same.

I too have tried all the steps.  I notice my tablet (chromebook) shows an IP address with different subnet (100.115.92.22).  When I connect to my local Wifi, chromebook reports connection to 192.168.68.119 which is the same subnet as my PC.

Is there a way to tell Mobilesheets to reset the subnet?
Reply
#6
That address is from the CGNAT "Carrier Grade Network Address translation" range: 100.64.0.0 - 100.127.255.255 Which is used by carriers (ISPs).

My guess is that your device has a sim and is using that to access your mobile carrier which is assigning that address.

When you connect via WiFi you get a local address from your router.
You're only paranoid if you're wrong  Cool
I'm using an Onyx Boox Tab X, and play low brass: mainly 'Bone and Tuba
Reply
#7
(5 hours ago)Lawrie Wrote: That address is from the CGNAT "Carrier Grade Network Address translation" range: 100.64.0.0 - 100.127.255.255 Which is used by carriers (ISPs).

My guess is that your device has a sim and is using that to access your mobile carrier which is assigning that address.

When you connect via WiFi you get a local address from your router.

No sorry you're wrong, no SIM, just a plain ol chromebook that connects to WiFi.  As I said the IP of the chromebook is correct, just Mobilesheets showing the weird address
Reply
#8
This is because ChromeOS places a firewall between Android apps and the network layer. So MobileSheets will report a different IP address than what is actually used. You have to ignore the IP address MobileSheets is showing and instead use 192.168.68.119 as that is the correct one. This won't stop the connection from working though. I still need to find time to switch to DNSSD so that the discovery mechanism can get around these kinds of issues.

Mike
Reply




Users browsing this thread:
3 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2025 MyBB Group.