Database Develop

WMWifiRouter

Being out of town in a hotel that has a flickering connection with a wireless (more spiritless than wireless....) I thought of giving my installed WMWifiRouter a try. I had it installed some time in January and never used it. Despite the successful connection between the Kaiser and the network, the laptop recognized the WMWifiRouter only twice, for very short time, and it never connected. I searched for instructions in the forum and the only available stated that WMWifiRouter 8 had everything packaged in the cab, no extra hacking needed. It also all referred to a website which apparently has been taken down. Has anybody made it work successfully? Are there any changes that need to be done to the phone other than installing and running the WMWifiRouter? Does the Internet Sharing Kaiser program need to be specially configured? Finally, does the Laptop need to be set up in any special way?
Thanks for any help!

you need to make an adhoc wifi connection between your laptop and phone before running the app...

shogunmark said:
you need to make an adhoc wifi connection between your laptop and phone before running the app...
Click to expand...
Click to collapse
I don't recall ever having to perform that step.

Nick Collision said:
I don't recall ever having to perform that step.
Click to expand...
Click to collapse
At some point you had made an adhoc connection to your phone, if it was there previously then you didnt have to do that first step. But if you never set up an adhoc connection to the other device then its necessary to do so before running the app.

How do you make an ad hoc Wifi connection between the phone and the laptop? I am not sure I understand what that means.Could you please explain in simple steps?

michalopoulosgk said:
How do you make an ad hoc Wifi connection between the phone and the laptop? I am not sure I understand what that means.Could you please explain in simple steps?
Click to expand...
Click to collapse
I could be wrong. But I believed the latest WmWifirouter package will handle everything on the PDA side include the adhoc SSID. Otherwise:
1. Start > Settings > Connections > "Wi-fi" > "Add New ..."
2. "wifirouter" for Netowork Name, "Connects to:" = "The Internet", Check "This is a device-to-device (ad-hoc) connection"
3. In Wmwifirouter, make sure to check "Use DHCP Allocator" so that Kaiser will acted as a DHCP server and assign IP to yr laptop, click "connect"
4. From yr laptop, search for "wifirouter" as SSID and connect to it.

The final version of the program does not allow for DHCP allocations etc., seems to do it all by itself. The ironic thing is that it connected somehow, after about 10 attempts, and I am usiing it to write this one.
Thanks for all your help and patience!

WMWiFiRouter site down
I'd like to give WMWiFiRouter a try. The site is down. How can I get a copy?
Thanks, Bren

The files had to be removed at the authors request. Keep checking his site for details!
http://www.wmwifirouter.com/
Or you can check this thread:
http://forum.xda-developers.com/showthread.php?t=357152
Also im going to lock this thread, all support details should be referred to the above thread due to the authors request to pull the software. I dont want to have this app sneaking its way in and having negative affects on the author.

Cannot get RDP working

OK, I have the program installed on the Kaiser, I have the port 3389 forwarded on my router. For the life of me, I can't figure out why I can't connect to the PC.
I even have the PCs alternate account and password and it's just not working. Someone please help.

you have to enable remote access on your host PC

I have also done that.

Try...
LogMeIn.com

Make sure your data connection on your phone is active before you try to connect.
The RDP client on this site does not seem to initiate the network on it's own.
I use bandswitch to close my idle connection and have to disable it when I try to rdp to home.

Do have something that you can telnet from? If so try telnetting to the PC you are trying to connect to via RDP.
telnet <ip> 3389
That will at least tell you if your PC is listening for rdp connections.

hmm, I tried telnetting myself using absolute telnet. Not exactly sure how to use it, but I entered in my IP address, and the port I have forwarded on my router and it kinda worked, but maybe not.
When I try to connect to 192.168.1.1, it won't connect.
when I try to connect to 192.168.1.101, it connects but does nothing.
I also tried initiating the data connection first, and it still didn't work...
Hmm, any other advice? I'd really like to get this working.

Try this, Jay...
JayIV said:
hmm, I tried telnetting myself using absolute telnet. Not exactly sure how to use it, but I entered in my IP address, and the port I have forwarded on my router and it kinda worked, but maybe not.
When I try to connect to 192.168.1.1, it won't connect.
when I try to connect to 192.168.1.101, it connects but does nothing.
I also tried initiating the data connection first, and it still didn't work...
Hmm, any other advice? I'd really like to get this working.
Click to expand...
Click to collapse
Now, just forwarning I am not very technically enclined about this stuff at all. Not yet anyway. I worked with exactly what you're working with. Trying to get RDP working... I found this article and it is now working for me beautifully. One word of warning, disable your PC's Firewall. I have McAfee and it was stopping the incoming request. Bad thing is we are all wireless, our IP's are changing at the drop of a hat. So if you figure out how to beat that be sure to share. LOL. Here's the link. Good luck!
http://www.aximsite.com/boards/vbarticles.php?do=article&articleid=210

mmmkay, got it working, kind of...
I was using the wrong ip address, not even realizing it. I was using my router assigned IP address- not the right ip address obviously. For future reference, and also because I have not seen this documented ANYWHERE else, you must use your ISP ASSIGNED IP ADDRESS, and the port forwarded on your router to connect to your desktop.
So, I got connected to my computer and all, great great. Now I need some help tackling my next problem. Apparently, I am not allowed to connect to my alternate account because of some kind of permission problem. I am not in the group RDC or whatever on the remote machine and I must be added manually. OK, sounds easy.... not. How the eff do I do this?
Yes, I am running Windows Vista Home Premium. I am aware that it came "missing remote". However, I have added the hack, and as far as I understand, I should now be able to RDC to my computer using my mobile...
Who can help?

JayIV said:
mmmkay, got it working, kind of...
I was using the wrong ip address, not even realizing it. I was using my router assigned IP address- not the right ip address obviously. For future reference, and also because I have not seen this documented ANYWHERE else, you must use your ISP ASSIGNED IP ADDRESS, and the port forwarded on your router to connect to your desktop.
So, I got connected to my computer and all, great great. Now I need some help tackling my next problem. Apparently, I am not allowed to connect to my alternate account because of some kind of permission problem. I am not in the group RDC or whatever on the remote machine and I must be added manually. OK, sounds easy.... not. How the eff do I do this?
Yes, I am running Windows Vista Home Premium. I am aware that it came "missing remote". However, I have added the hack, and as far as I understand, I should now be able to RDC to my computer using my mobile...
Who can help?
Click to expand...
Click to collapse
Having never used vista (yuk, yuk yuk) I don't know where the settings are, but being a fisher price os it should be fairly obvious.
Just add yourself to the remote desktop user group in the users and groups settings. If your account is an admin account you should have RDP access by default I believe

right click my computer, go to properties, click the remote tab. Click the "select remote users" button

I've already tried to things you two just mentioned. However, these options are not there. I think it has something to do with vista home premium...

I'm not sure about how or what you "hacked" to get RDP on your version of Vista, but there is a setting for RDP versions.
Under system properties -> remote tab
There are three options which essentially break down to this:
-Don't allow any RDP
-Allow all RDP (RDP 5 and RDP 6)
-Allow only RDP with NLA (RDP 6)
Vista and updated XP machines can have the RDP 6.0 program. Otherwise most systems are still RDP V5.
I found the allow all RDP (the second option) works well with from my kaiser to my Vista machine.

hotspot gives increasingly higher numbers

I am running frf91 and my hotspot is working. Every time I turn on the hotspot function of my phone and connect my computer, my computer sees it remembers the SSID and password but reports a higher number than the time before. For example my SSID shows 'androidap (5)'. Five is the number of times I have turned the feature on my phone and then connected my computer. I don't know if the problem is my phone or computer. I am using a dell latitude 6400 with win7 64bit.

It has something to do with your computer, more specifically - with bloatware that is most probably installed as WiFi control application. Nothing to do with Nexus. SSID doesn't change, otherwise you wouldn't be able to connect to it.

Thanks for your input Jack. My computer is recently formatted and I am only using the windows software to manage my wireless networks. I am not using any third party software. What kind of bloatware were you thinking? I am using Microsoft security essentials for antivirus but otherwise I try to keep things very clean. Maybe it's a driver issue? Any other thoughts?

Usually laptops come preinstalled with management SW from their manufacturer - including WiFi management apps that are bundled with the WiFi driver (Intel, Dell, etc). If you didn't install it and you're using the default Win7 networking - then my answer above isn't applicable.
Any chance of a screenshot showing this number?
Also, you could try changing the SSID, registering the laptop on the new network and checking if you're getting the same number increase as before.

michaelbart0n said:
I am only using the windows software to manage my wireless networks. .............Any other thoughts?
Click to expand...
Click to collapse
'bleedin Windoze again then !!

I have a Lenovo laptop with a fresh copy of Windows 7 Professional. No other WiFi management software.
I have this same issue. Everytime I WiFi tether, I get a new network connection with an increasingly higher number. It's not the SSID that changes, though. That's always the same. Just the connection name changes.
I prefer to just tether with USB, anyway. That way my phone gets a charge a the same time. I mostly use my WiFi tether for my iPad.

I have Win7 at home, I'll test it later.

Jack_R1 said:
Usually laptops come preinstalled with management SW from their manufacturer - including WiFi management apps that are bundled with the WiFi driver (Intel, Dell, etc). If you didn't install it and you're using the default Win7 networking - then my answer above isn't applicable.
Any chance of a screenshot showing this number?
Also, you could try changing the SSID, registering the laptop on the new network and checking if you're getting the same number increase as before.
Click to expand...
Click to collapse
Thanks again. I have tried changing the ssid and I am getting the same results. I have found that if I keep tether running on the phone and connect multiple times from the computer, the number doesn't climb. But when I toggle tether on the phone and connect it creates a new, higher number. Of course my mac friend can't reproduce this error with his ipad, all is fine there. I have reproduced this error on two win7 64 machines and an XP profession 32 machine.
The screenshot you requested is attached

I noticed this too even with USB tether. I am fairly certain that this is because your computer counts each connection as a different network because your phone uses dynamic ip addresses and that creates a different default gateway for your hotspot each time it is connected.

Ok, looks like it's creating a new "public network" each time you're connected to tethering.
I couldn't replicate it on XP, since XP doesn't create network profiles for connections.

This is a stock Android issue, right? Not something screwed up in just custom ROMs?
Can someone point me in the direction of the bug report on the Issues tracker? Or isn't there one?

It's because it is in a different IP range all the time.
You're worrying about nothing. It's simply a trivial number, nothing to even concern yourself with.

GldRush98 said:
It's because it is in a different IP range all the time.
Click to expand...
Click to collapse
No it isn't.
It's the MAC addres that changes every time.
Doesn't happen with the sense HTC hot spot or with barnacle.
It's incredible that no one has looked in to this annoying bug.

GldRush98 said:
You're worrying about nothing. It's simply a trivial number, nothing to even concern yourself with.
Click to expand...
Click to collapse
Wrong. Windows 7 takes 5 minutes to connect to the network when this happens, as opposed to the usual 10 seconds or so.
If it were just the number that had changed, nobody would care.

Further info on new MAC addresses
The Solutor said:
No it isn't.
It's the MAC addres that changes every time.
Doesn't happen with the sense HTC hot spot or with barnacle.
It's incredible that no one has looked in to this annoying bug.
Click to expand...
Click to collapse
To continue THE SOLUTOR's comment, I found this article that describes the new MAC address issue as it shows up in windows, but it also doesn't have a solution.
http://www.hanselman.com/blog/iPhoneTetheringPersonalHotspotShowsUpAAsANewNetworkEachTimePlusTheSmartQuoteIsSilly.aspx#2855ecae-2f14-4f40-a807-263e9798cc4c

Easy Root for Bionic Stock 4.1.2 (Jelly Bean)

4th Update 5/2/2013 - Found a bug... Nothing that would affect the overall functionality, but it could cause some users to think that their phone is successfully connected via USB debugging, when it really isn't.
Update: 5/2/2013 - Per user requests, adding link to VirtualBox download site on the original post.
3rd Update 5/1/2013 - I changed the code that 'finds' the exploit file to make sure it get executed successfully. It's now using the "PATH" environment to do this. This is more reliable than the actual Linux 'find' command I was using before. Also added some additional instructions to clarify some steps based on feedback from users. Finally, added code to detect if the network adapter is not configured correctly. It will alert the user to configure the network adapter properly in the VirtualBox application.
2nd Update 5/1/2013 - I added some lines to the script to stress the importance of pressing one of the three hardware buttons on the phone (Volume up, Volume Down, or Power) once the exploit has been executed. After discussing this with the author of the exploit, this is an important step to obtaining root.
UPDATE 5/1/2013 - New and improved .ova file. Contains improved logic in the exploit script to help with some of the problems that have been encountered by users.
If you've had trouble rooting, please download the new version and try again!
Hey folks, I'm a UNIX admin by profession, so I took the challenge over the weekend to come up with an easy root process for Bionic stock Jelly Bean, specifically for those who aren't familiar with Linux.
I decided to build a Linux VM under Oracle VirtualBox on my Windows PC. This seemed like the logical choice since VirtualBox is free, a relatively small download, is easy to install and it's easy to import VMs.
My first attempt was using CentOS Linux. It worked, but the file required for users to download was over 450MB... Back to the drawing board!
Started looking for very small Linux distros and found Tiny Core Linux. This worked well. The file required for download is 50 MB.
Everything you need to root the Bionic is here and it is automatic. The process will walk you through connecting to the Samba file share, connecting the phone in USB debugging mode, and OF COURSE, it will run the process to root the phone.
Here are the steps:
1) Install Sun VirtualBox on your Windows PC.
http://download.virtualbox.org/virtualbox/4.2.12/VirtualBox-4.2.12-84980-Win.exe
Note: We've had one report that this file also works with VMWare Workstation and VMWare Player. If you don't want to install VirtualBox feel free try the file with VMWare.
2) Download the VirtualBox .ova file containing the Linux VM from one of the following links:
http://www.knite.net/Bionic/Root_Bionic_JB_20130501-4.ova
http://www.mediafire.com/?a2i6forosp77xrd
https://dl.dropboxusercontent.com/s...fhiAIiSwc0jD1AdVFNY27QdoeKP9ot_7IdDetSvw&dl=1
3) Import the .ova file into VirtualBox. (Click "File" then "Import Appliance".)
4) Start the imported VM in VirtualBox (Click the big "Start" Button. It has a green arrow icon.)
5) Follow the instructions on the Linux console.
That should do it. If you need help I will be monitoring this thread.

Willing Tester
I am not familiar with Linux but I am familiar with root, supersuser, recovery, and fxz/rsd lite. I am up for a new phone next month so I am willing to try this on my Bionic. This doesn't sound too hard....(famous last words). Will try on my Windows 7 laptop.
Will report if this works. Won't be able to until later today.
Thank you OP!

Found a problem with the script. Should work now. Download and import again, if you've already downloaded. I also managed to get the download down to 46MB by defragging and compacting the .vmdk file.
dl.dropboxusercontent.com/s/bb53ayj5c3nd5ie/Root_Bionic_JB.ova?token_hash=AAGSOYfPuDXTur_e9qlYl2JRERovPyfMwe-2xNzHXg4Lxg&dl=1

Downloading new link now. Haven't tried to root yet. I'm at work right now.
Do you have any other suggestions before I start? I don't have to be completely stock do I...? (all stock apps, no superuser, etc.) I am on stock jelly bean 4.2.1, ver. 98.72.22.XT875.Verizon.en.US, stock recovery...but I did use OTA Rootkeeper so I have a (semi-functioning) superuser install. Do you suggest starting fresh with fxz?
I will be home in a couple hours to give it a try.

Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?

Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!

Great, I just wanted to do something to make it easier for everyone, since so many seemed to be struggling with Linux.
lc75 said:
Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!
Click to expand...
Click to collapse

So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
TechnoHippie said:
Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?
Click to expand...
Click to collapse

marty45714 said:
So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
Click to expand...
Click to collapse
Ok that's gonna be my problem then ...I'll give it a shot when I get home and I'm not connected to my office network.

USB 3.0?
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.

I am struggling with the directions and feeling dumb about it... Not sure what to put for the "Host IP Address"
EDIT: Restarted the virtual machine and it gave me the information I needed. The first time around the field was blank.
I appear to still lack root because the SU app wants to update the binary and fails to do so.

I'm not sure, but one thing you can check. When the Linux console is up in the VirtualBox window, there is a section in the lower, right hand corner of that window that shows a bunch of icons. Click the USB icon and very that you see your Bionic as an option for hardware that is connected to your laptop.
Also, I'm making an assumption that you have the Motorola UBS drivers already loaded on your Windows system before you even started this whole process. Maybe I shouldn't make that assumption???
cakessi said:
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.
Click to expand...
Click to collapse

First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.

You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
MNEman13 said:
First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse

Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!

New link. See original post. I have it on Mediafire now.
dcmcc99 said:
Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
Click to expand...
Click to collapse

marty45714 said:
You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
Click to expand...
Click to collapse
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.

Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
MNEman13 said:
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.
Click to expand...
Click to collapse

I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
marty45714 said:
Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
Click to expand...
Click to collapse

Here are some tips that I posted for someone over on Droid Forums. Hopefully some of this will help us figure out what is going on:
Need you to do some investigation. Run the exploit again. Once your phone is connected to the SMB share and the Linux script verifies the connectivity, press Ctrl-C to break out of the script and return to the Linux command prompt. Make sure your phone is connected to USB. From there execute the following commands and share the output with me:
sudo ash
cd /home/guest/share
./adb.linux shell
(if you execute the above command and DO NOT see this prompt: [email protected]_targa/ $
then you have USB connectivity issues and need to make sure you get your phone successfully connected
to VirtualBox and the Linux VM)
ls -l /storage/rfs0
I want to see the output of the "ls" command to verify that the SMB share is being mounted to /storage/rfs0
This can cause the exploit to fail is it's not.
If you see no output from that command, run this command:
find /storage -name pwn
If you get that far and this looks good. Can you type:
su -
and see if you get a root prompt? A root prompt means your prompt will end with '#' instead of '$' before the cursor.
If you do get this, it could be that your Superuser app is simply broken and need re-installed.
The command that the exploit runs to root the phone, once you get this far is:
/storage/rfso/pwn 1
You can try running that manually and see what happens.
caskieadam said:
I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
Click to expand...
Click to collapse

P20 Pro Huawei share with pc not working

I just got my new P20 Pro and wanted to try out Huawei's share aka Air drop. Anyway I've managed to locate my phone on my PC [windows 10] but , I can't connect to it. It says error check my name or network ? Any one know a fix for this ? I've tried changing the name from my phone but nothing works. Huawei suggest to clicl the diagnose button which also does nothing.
Help please! Thanks in advance

FIX!
For anyone with this problem I found a fix. Go to control panel > Programs > Turn on or off windows features > Scroll down to SMB 1.0 File sharing support, Click the plus to expand and then check all 3 sub boxes!

windows can not get access to \\ P20PRO
It is possible that the name of the location is not well written or that there is a problem with the network.
Error code: 0 * 80070035

Works fine here and on my Mac.

you need to activate smb direct/client/server

Hijacking this thread. Tried this and still can't connect. Using a Sky Q router.

Yea, i have problems also with the P20 pro and windows 10. I have turned on the SMB settings and still no luck while i can see all my other device in the network just fine...

i did it on widows 10
1. Plug the USB cable into the phone and the computer.
2. Touch Settings.
3. Touch Wireless & networks.
4. Touch Tethering & portable hotspot.
5. Touch the USB tethering slider to turn it on.
6. The phone is now tethered.
7. On the computer, wait for the device drivers to install then click Home network.
8. Wait while the computer automatically applies the settings and connects to the network.
9. Setup is complete. Click Close.
10. Unplug ur phone and it will be working
good luck ^_^

MennaSamir said:
i did it on widows 10
1. Plug the USB cable into the phone and the computer.
2. Touch Settings.
3. Touch Wireless & networks.
4. Touch Tethering & portable hotspot.
5. Touch the USB tethering slider to turn it on.
6. The phone is now tethered.
7. On the computer, wait for the device drivers to install then click Home network.
8. Wait while the computer automatically applies the settings and connects to the network.
9. Setup is complete. Click Close.
10. Unplug ur phone and it will be working
good luck ^_^
Click to expand...
Click to collapse
Worked for me Thanks:good:

U must enable tethering on the comp or laptop and voala, on the network is appearing my phone wuth all folders

I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.

Lyssion said:
I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.
Click to expand...
Click to collapse
Nope, not working and i think huawei is pretty **** when it comes to pc connectivity

It wasn't working for me, for a while, until I realised I had to turn on "computer share" in Huawei Share settings! Duh, like..

It wasn't working for me. Why? Is there another way?
---------- Post added at 07:13 PM ---------- Previous post was at 07:12 PM ----------
Darian John said:
For anyone with this problem I found a fix. Go to control panel > Programs > Turn on or off windows features > Scroll down to SMB 1.0 File sharing support, Click the plus to expand and then check all 3 sub boxes!
Click to expand...
Click to collapse
It wasn't working for me. Why? Is there another way?

Lyssion said:
I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.
Click to expand...
Click to collapse
This worked for me, Thanks :good::good:

Lyssion said:
I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.
Click to expand...
Click to collapse
Thank u very much. I had the same problem and now it's working:good::good::good:

Darian John said:
For anyone with this problem I found a fix. Go to control panel > Programs > Turn on or off windows features > Scroll down to SMB 1.0 File sharing support, Click the plus to expand and then check all 3 sub boxes!
Click to expand...
Click to collapse
That worked. Thank you very much. :good:

If it still helps i think i got it.
Use the original huawei charging cable you got with the phone.
I tried it all.. tethering, debugging, hisuite etc.. but nothing worked
1. step Install HiSuite on computer,
2. step plug in your phone with original cable,
3. step HiSuite on computer will run by itself,
4. step select transfer files on your phone,
5. step computer will ask you if you all it to install HiSuite on your phone and click ok,
6. step on your phone pop up will show to install HiSuite on Huawei.
Maybe also go to settings - connections - usb thetering (if needed) and thick it.
Hope it helps, it did for me - but barley lost my mind...
Good luck,
Toni

@frozenflame123
Topic is for "Huawei share" not for "HiSuite"

You great! Thank a lot! I had the same problem with the Honor9 Lite e I solved it thanks to your suggestion!