I have been having ongoing issues with my 6 pro trying to use Chrome Remote Desktop app to connect to my home computer. If I use it while on Wi-Fi it works fine but when using Verizon data it doesn’t. Anyone else using chrome remote with success?
5g or lte ?
I use this every day on multiple wifi signals and on lte/5G without issue. Lte is pretty slow to connect and function and sometimes it'll tell me my list is empty but a close and reopen fixes that every time.
No problems using it to connect to my self-built Windows 10 PC from my Pixel 6 Pro. I tested using both Wi-Fi and my mobile data (which is AT&T).
Same. Googled like a weeek ago. Seems to be a problem with Verizon.
It works fine with wifi but won't stay connected on mobile data so you are not alone.
Related
I am having a problem tethering my laptop and my desktop computer to my Galaxy Nexus ever since I installed the 4.2 update. My Nexus 7 tablet does not seem to have any issues connecting.
My laptop is a Lenovo Thinkpad T60-2007 which has an Atheros 42T0825 wifi chip. It used to connect to the Android 4.1 Galaxy Nexus hotspot without any problems under Win XP. Immediately following upgrading the Galaxy Nexus to Android 4.2 the laptop had problems. The laptop would connect to the tethering wifi hotspot, but would not be able to browse the internet (or in a few rare circumstances, would browse extremely slowly with frequent errors that would prevent web pages from loading).
I tried a factory reset on the Galaxy Nexus (which still left the phone at android 4.2), and there was no change in behavior.
I tried removing the wifi password and running the hotspot as an 'open network' and there was no change in behavior.
I tried a Windows XP reinstall on the laptop (to Windows XP SP3) and there was no change in behavior.
I replaced the wifi card (with and identical model) and there was no change in behavior
As a last resort (and because the laptop needed it), I installed Windows 7 Ultimate 64-bit on a new SSD and put in additional 2 GB of RAM.
Now although the laptop can still see the hotspot, it cannot connect to it. Even though the correct password is typed at the prompt, it gives a 'Network Security Key mismatch' error and will not connect. The laptop can connect to the hotspot if it is set as 'open', but will not connect to any sites or web pages (i.e. same problem as before with Win XP).
The laptop *does* work with the Galaxy Nexus via USB tethering, which suggests that there is some kind of wifi issue, but the laptop connects to my home wifi network (Linksys E3000 running stock firmware) just fine.
My desktop computer (running Windows 7) exhibits the same behavior as the laptop under Windows 7.
I was able to get a Macbook and a Dell Latitude laptop to connect to the wifi hotspot and successfully browse the internet (I will have to look up the model numbers later).
I am writing to try to find out whether anyone has noticed any similar problems/incompatibilities and whether anyone might know the causes.
Is there a problem with the b/g/n connectivity of my laptop? Did the wifi hotspot b/g/n configuration on Android change with the 4.2 update? Might a bad install of android 4.2 on my phone be to blame? Maybe there is a problem with g or n protocols? Which does the 4.2 hotspot use?
Thanks in advance
same problem with me
Tarzanman said:
I am having a problem tethering my laptop and my desktop computer to my Galaxy Nexus ever since I installed the 4.2 update. My Nexus 7 tablet does not seem to have any issues connecting.
My laptop is a Lenovo Thinkpad T60-2007 which has an Atheros 42T0825 wifi chip. It used to connect to the Android 4.1 Galaxy Nexus hotspot without any problems under Win XP. Immediately following upgrading the Galaxy Nexus to Android 4.2 the laptop had problems. The laptop would connect to the tethering wifi hotspot, but would not be able to browse the internet (or in a few rare circumstances, would browse extremely slowly with frequent errors that would prevent web pages from loading).
I tried a factory reset on the Galaxy Nexus (which still left the phone at android 4.2), and there was no change in behavior.
I tried removing the wifi password and running the hotspot as an 'open network' and there was no change in behavior.
I tried a Windows XP reinstall on the laptop (to Windows XP SP3) and there was no change in behavior.
I replaced the wifi card (with and identical model) and there was no change in behavior
As a last resort (and because the laptop needed it), I installed Windows 7 Ultimate 64-bit on a new SSD and put in additional 2 GB of RAM.
Now although the laptop can still see the hotspot, it cannot connect to it. Even though the correct password is typed at the prompt, it gives a 'Network Security Key mismatch' error and will not connect. The laptop can connect to the hotspot if it is set as 'open', but will not connect to any sites or web pages (i.e. same problem as before with Win XP).
The laptop *does* work with the Galaxy Nexus via USB tethering, which suggests that there is some kind of wifi issue, but the laptop connects to my home wifi network (Linksys E3000 running stock firmware) just fine.
My desktop computer (running Windows 7) exhibits the same behavior as the laptop under Windows 7.
I was able to get a Macbook and a Dell Latitude laptop to connect to the wifi hotspot and successfully browse the internet (I will have to look up the model numbers later).
I am writing to try to find out whether anyone has noticed any similar problems/incompatibilities and whether anyone might know the causes.
Is there a problem with the b/g/n connectivity of my laptop? Did the wifi hotspot b/g/n configuration on Android change with the 4.2 update? Might a bad install of android 4.2 on my phone be to blame? Maybe there is a problem with g or n protocols? Which does the 4.2 hotspot use?
Thanks in advance
Click to expand...
Click to collapse
i am also facing the same problem when i try to connect to any wi-fi network. it stucks on obtaining ip address. even though the password is correct. even i tried hotspot way to connect. via different s/w like connectify even i tried to make hotspot via cmd shell commands too. in that same it is not able to connect.
i dont know what the problem. i am currently using 4.2.1 rooted JB. i am planning for factory reset. but as you did earlier and no success so i might not do.
even with open wifi network it is not able to connect..!! it happen after the update..
deeprocks31 said:
i am also facing the same problem when i try to connect to any wi-fi network. it stucks on obtaining ip address. even though the password is correct. even i tried hotspot way to connect. via different s/w like connectify even i tried to make hotspot via cmd shell commands too. in that same it is not able to connect.
i dont know what the problem. i am currently using 4.2.1 rooted JB. i am planning for factory reset. but as you did earlier and no success so i might not do.
even with open wifi network it is not able to connect..!! it happen after the update..
Click to expand...
Click to collapse
The inability to either create a mobile hotspot and connect to it is why I went back to stock rooted 4.1.1. I have tried Muzzy and AOKP and could not create and connect to a hotspot using native tethering or Wifi Tether. It has been a while since I checked the forums, but did not see a solution that helped me
PS - I was trying to tether mobile devices not laptops though
My issue resolved on its own...!! Don't know how..!! but now I can use WiFi tether and also reverse tethering too..!! Reverse tethering is really too handy thanks to xda members for making awesome apps.
Sent from my Galaxy Nexus using xda premium
Tarzanman said:
I am having a problem tethering my laptop and my desktop computer to my Galaxy Nexus ever since I installed the 4.2 update. My Nexus 7 tablet does not seem to have any issues connecting.
My laptop is a Lenovo Thinkpad T60-2007 which has an Atheros 42T0825 wifi chip. It used to connect to the Android 4.1 Galaxy Nexus hotspot without any problems under Win XP. Immediately following upgrading the Galaxy Nexus to Android 4.2 the laptop had problems. The laptop would connect to the tethering wifi hotspot, but would not be able to browse the internet (or in a few rare circumstances, would browse extremely slowly with frequent errors that would prevent web pages from loading).
I tried a factory reset on the Galaxy Nexus (which still left the phone at android 4.2), and there was no change in behavior.
I tried removing the wifi password and running the hotspot as an 'open network' and there was no change in behavior.
I tried a Windows XP reinstall on the laptop (to Windows XP SP3) and there was no change in behavior.
I replaced the wifi card (with and identical model) and there was no change in behavior
As a last resort (and because the laptop needed it), I installed Windows 7 Ultimate 64-bit on a new SSD and put in additional 2 GB of RAM.
Now although the laptop can still see the hotspot, it cannot connect to it. Even though the correct password is typed at the prompt, it gives a 'Network Security Key mismatch' error and will not connect. The laptop can connect to the hotspot if it is set as 'open', but will not connect to any sites or web pages (i.e. same problem as before with Win XP).
The laptop *does* work with the Galaxy Nexus via USB tethering, which suggests that there is some kind of wifi issue, but the laptop connects to my home wifi network (Linksys E3000 running stock firmware) just fine.
My desktop computer (running Windows 7) exhibits the same behavior as the laptop under Windows 7.
I was able to get a Macbook and a Dell Latitude laptop to connect to the wifi hotspot and successfully browse the internet (I will have to look up the model numbers later).
I am writing to try to find out whether anyone has noticed any similar problems/incompatibilities and whether anyone might know the causes.
Is there a problem with the b/g/n connectivity of my laptop? Did the wifi hotspot b/g/n configuration on Android change with the 4.2 update? Might a bad install of android 4.2 on my phone be to blame? Maybe there is a problem with g or n protocols? Which does the 4.2 hotspot use?
Thanks in advance
Click to expand...
Click to collapse
I have not been able to get any form of wifi AP to work since flashing over to 10.1 CM. it turns on the AP and I can get wifi to link but can't get an IP and any kind of connectivity to the internet... so far, I haven't been able to find any help for the issue but I'll keep reading!
this was after a wipe data & cache install of 10.1.
I have tried google searching this, searching through the forums and can't find anything really, I found 1 google search and it wasn't helpful. My issue is when I turn on my wifi hotspot using the stock fire phone OS it will not work. So first when the computer/tablet tries to connect it take around a minute to just connect to the hotspot, while doing this windows states it is taking longer than usual. Then once it does connect I only have limited connectivity. Now funny thing is when I use CM11 rom the hotspot works fine, but there things about it I don't like so I'm sticking with Fire OS for now.
I have tried on a desktop pc, laptop, tablet and a intel nuc, I have tried on Windows 8.1 and Windows 10, both same issue, I can browse the web fine on the phone itself, but never a hotspot. My apn settings all appear to be correct and I'm using straight talk through Tmobile. I even had the phone replaced, same problem. Anyone else have similar issues?
My home network has fast and stable internet connection, both wired (Ethernet) connections are fine, as well as Wifi ones (Surface 3 Pro works well, Lumia 930 with Windows 10 Mobile works well).
However, Android / LG G4 has problems recognizing it has internet available. While it is connected to access point (with great signal strength), and at about 500Mbps transfer rate, it shows 5-10 times per hour "internet not available for 'ssid'" error, will disconnect and connect to LTE instead.
I have "switch to mobile data enabled" under Wifi settings, and would like to keep this. Just to make this switching much less aggressive. Is there a fix for this?
Radek Hulán said:
My home network has fast and stable internet connection, both wired (Ethernet) connections are fine, as well as Wifi ones (Surface 3 Pro works well, Lumia 930 with Windows 10 Mobile works well).
However, Android / LG G4 has problems recognizing it has internet available. While it is connected to access point (with great signal strength), and at about 500Mbps transfer rate, it shows 5-10 times per hour "internet not available for 'ssid'" error, will disconnect and connect to LTE instead.
I have "switch to mobile data enabled" under Wifi settings, and would like to keep this. Just to make this switching much less aggressive. Is there a fix for this?
Click to expand...
Click to collapse
I have no end of WiFi problems on my G4 too. All my other devices and Android devices are absolutely fine. Does it on any WiFi network that I connect to.
Theres a few threads about this, I even posted a logcat but ndidn't hear anything back
Hello,
I'm facing this issue that YouTube play store and other few apps like paytm do not work on mobile data(YouTube works fine in chrome), but they work fine when I'm connected to WiFi (any WiFi works, even hotspot created from other phone using same mobile operator)
When I open YouTube it gets stuck on loading and after sometime asks to check my network. If I want to use YouTube in app I have to connect to any WiFi network and launch YouTube app which loads within 2,3 seconds. After I do that even if I disconnect WiFi and start using mobile data for the app it works perfectly.
I tried few things when I was searching solution for this but couldn't find solution.
I also tried different rom and other network it doesn't load.
Currently I'm on RRemix 8.1.
Thanks in advance
Is anyone having an issue with rdp clients connecting and then suddenly dropping 5G or LTE on the pixel 6 or pro? Some people on the other Reddit threads are saying Verizon is the issue.
EDIT/UPDATE: I now have done a little more troubleshooting. I took my pixel 6 pro and tried using Chrome remote desktop on 5G and LTE and when I connect it automatically shuts down the radio and turns on the radio again and does this as an endless loop if you're trying to get into Chrome remote desktop.
Then I masked my data by using VPN and on 5G and LTE the same behavior happens when using Chrome remote desktop.
After these failed, then I turned on hotspot with a VPN and VPN tethering and connected my other device with Chrome remote desktop installed. An apple device, connected to my PC that I remoted into.
Before I didn't have to do any of this and could just connect to the RDP client on Verizon with 5G and LTE on my previous pixel device.
I need to bump this.. can anyone with a pixel 6 or pro try using any remote desktop client and verify it works on any isp with 5g or LTE? Does mobile connection disconnect over and over?
rester555 said:
I need to bump this.. can anyone with a pixel 6 or pro try using any remote desktop client and verify it works on any isp with 5g or LTE? Does mobile connection disconnect over and over?
Click to expand...
Click to collapse
I use Remote Desktop and it works fine on LTE/5G on my 6 Pro.
who's your carrier? I remember a carrier in the US was blocking remote desktop port and the only way around it was to use a VPN or to change the port number. If you Google it you'll see the issue (I think it was VZW and any company using their infrastructure).
sidenote, there's a reason why carriers block this port and specifically rdp. it's one of the worst security holes you'll ever create. Create a VPN on your network and login to your PC using this method. Or even TeamViewer is a better option than opening up rdp to the web. Horrible, horrible idea, and it shouldn't be allowed (internal is ok but even then it's not recommended and should always be avoided).
Alekos said:
I use Remote Desktop and it works fine on LTE/5G on my 6 Pro.
who's your carrier? I remember a carrier in the US was blocking remote desktop port and the only way around it was to use a VPN or to change the port number. If you Google it you'll see the issue (I think it was VZW and any company using their infrastructure).
sidenote, there's a reason why carriers block this port and specifically rdp. it's one of the worst security holes you'll ever create. Create a VPN on your network and login to your PC using this method. Or even TeamViewer is a better option than opening up rdp to the web. Horrible, horrible idea, and it shouldn't be allowed (internal is ok but even then it's not recommended and should always be avoided).
Click to expand...
Click to collapse
It's interesting that you say that, I've been using every other pixel phone with RDP on Verizon and it was no issue until the pixel 6 pro.
UPDATE: I added more information to 1st post.
rester555 said:
It's interesting that you say that, I've been using every other pixel phone with RDP on Verizon and it was no issue until the pixel 6 pro.
UPDATE: I added more information to 1st post.
Click to expand...
Click to collapse
If you can access remote desktop locally then there shouldn't be a difference (unless your Carrier or router is blocking the connection) but....
I've never heard of an app shutting down a mobile connection that is bizarre behavior. Just all I can think of is making sure all your apps and play services are updated That's two different things and your system and play system (also 2 different things, 4 Total). restart your device, also force LTE mode for now in network settings, see if that helps.
when you open Chrome remote desktop on Android when exactly does the mobile connection reset or change?
can you duplicate that every single time? If you can I would reach out to Google and provide then with the bug...
In any event does that happen with just the MS remote desktop app?
Alekos said:
If you can access remote desktop locally then there's no difference whatsoever.
I've never heard of an app shutting down a mobile connection that is bizarre behavior
Click to expand...
Click to collapse
It's interesting that this only has occurred now and I use the exact same provider for 10 years and every other pixel device works with multiple RDP clients
rester555 said:
It's interesting that this only has occurred now and I use the exact same provider for 10 years and every other pixel device works with multiple RDP clients
Click to expand...
Click to collapse
I updated my comment while thinking it over ..
does it happen on both remote desktop apps on your Pixel 6? (the network change?) it might not actually be an issue and your problem is most likely Verizon. Tons of threads on VZW official forums about this on their network - again they do it for a good reason but its not all Verizon Customers and good luck getting any help from them (worth to try though)
I just tested Chrome Remote Desktop on my 6 Pro's 4G to my desktop and it's working without a hitch.
roirraW edor ehT said:
I just tested Chrome Remote Desktop on my 6 Pro's 4G to my desktop and it's working without a hitch.
Click to expand...
Click to collapse
What is your isp?
So TeamViewer rdp works. Chrome remote desktop does not... Something screwy is going on here.
rester555 said:
So TeamViewer rdp works. Chrome remote desktop does not... Something screwy is going on here.
Click to expand...
Click to collapse
I'm not on Verizon and it works for me (Chrome rdp and MS rdp.- mobile LTE/5G). does MS RDP app on Android cause a similar issue?
rester555 said:
What is your isp?
Click to expand...
Click to collapse
My ISP is Spectrum and my mobile carrier is AT&T.
MS rdp works too