Hi,
I am successfully using ADB Wifi with my Android 11 device.
But each time you connect to the device using adb from the PC, you have to check the port number first at it is randomly defined by Android ! (the IP is fix as I have fixed it on my home network)
It you could specify the port address and have it fix, you could connect to your Android without having to grap the phone, go though the 'Developer options' menu to look at this port number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Set IP address to Static and you're fine.
jwoegerbauer said:
Set IP address to Static and you're fine.
Click to expand...
Click to collapse
I am using static IP address. The problem is with the port. It needs to be a static port.
ADB by default makes use of port 5555: of course you have to verify that port isn't blocked by switch or firewall. You alternately can use port 3389.
jwoegerbauer said:
ADB by default makes use of port 5555: of course you have to verify that port isn't blocked by switch or firewall. You alternately can use port 3389.
Click to expand...
Click to collapse
On the screenshot above the port given is 33515, can I specify I want to use another port like 5555 ?
I have Android 11, I have the impression it is only possible to use 5555 in Android 10.
On Android - where it doesn't matter what version - ports 5555 and/or 3389 are reserved for ADB. Point.
jwoegerbauer said:
On Android - where it doesn't matter what version - ports 5555 and/or 3389 are reserved for ADB. Point.
Click to expand...
Click to collapse
I have tried ports 5555 and 3889, they do not work:
But it worked with the port 40001 given by my phone wireless debug screen. This number is not static unfortunately.
No worries, jwoegerbauer doesn't know what they're talking about in this case or maybe don't understand the question fully.
You either connect to the phone via adb an issue the command
Code:
adb tcpip <port number>
to set the port to be fixed UNTIL the next reboot!
Or maybe you can localy execute the shell commands
Code:
setprop service.adb.tcp.port <port number>
stop adbd
start adbd
for which you might need root, I'm not sure. Also works only until the next reboot, AFAIK.
To set the port fixed even after a reboot you'd have to get more crafty. Maybe some kind of startup script that does it for you. And there are also "Wifi Debugging" apps in the app store (careful!) that may set the port for you.
All the best,
KurrKurr
I feel sorry for the OP, as much as I feel sorry for myself... as I have the same problem, and so does EVERYONE using the new Android 11 and Android 12 Developer options Wireless debugging features!
I found this thread trying to find someone (anyone!) who understands that adb, as of Android 11 has the ability to connect COMPLETELY wirelessly (i.e., no need for 5555 over USB!)
Android 12 even has the ability to add a new tile that makes it tremendously easier to connect COMPLETELY WIRELESSLY between adb on the PC and the Android phone.
(PSA) Using the new Android 12 TILE for 'Developer options' 'Wireless debugging' to establish adb connection over Wi-Fi without USB
The problem with most answers to this thread is people dont' seem to understand this is new with Android 11 and Android 12. The people who responded seem to think you first connect over USB with TCP port 5555 and then disconnect to use adb over Wi-Fi (which worked for years and still does but that's not the problem here).
The problem?
The problem is Android 11 and Android 12 use a RANDOM port between some range that seems to be within 3#### and 4#### but what we NEED is a command to FIND that port without LOOKING at the Android device to get that port.
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
That is the solution everyone needs (me included)!
The problem:
You can toggle wireless debugging on the quick tile, but you can't access the random port without knowing it.
Solution:
After using the quick tile to enable wireless debugging, you can use nmap (and awk) on your debug workstation to discover the open port to run "adb connect <IP>:<PORT>" with:
1) set Android 11/12/etc. to static IP. If you use DHCP ... you'll have to also discover the DHCP IP of your device. A static DHCP lease will also suffice to make things easy on you if you must rely on DHCP for the particular network you're accessing. In any event, you must be able to know or discover the IP address of your device in order to make this work.
2) turn on wireless debugging - you'll note that it changes the port every time wireless debugging is toggled on.
3) The ports are supposedly always within the range of 30000 to 49999.
4) since we have the IP and the port range, we can use nmap to obtain the listening port. So this step is to install nmap and awk if you dont have those commands (run "nmap" and "awk" on their own to see if you have them in your path)
5) run this code - set PHONE= to the static IP of your device. Mine is set to 192.168.19.19, so:
PHONE=192.168.19.19
adb connect ${PHONE}:$( nmap -sT ${PHONE} -p30000-49999 | awk -F/ '/tcp open/{print $1}' )
6) it should connect with something like this message:
connected to 192.168.19.19:42699
this is not a perfect solution if you happen to have other apps that open a listening TCP port in those ranges... but you could also filter those specific ports out with the nmap range. Most people won't be in this boat, but its probably worth mentioning for someones sake.
For Windows it looks like this. Feel free to suggest improvements.
I use gawk 3.1.6 & Nmap 7.92
Wireless_ADB_RecoverPhone.cmd
@nmap -p 30000-49999 -sS -T5 -A 192.168.178.21 | awk -F/ "/tcp open/{print $1}"
Click to expand...
Click to collapse
Wireless_ADB_Connect.cmd
@echo off
:MAIN
adb start-server
if defined PHONE_PORT goto :END
:CONNECT
echo Port scanning and connecting...
for /F %%I IN ('Wireless_ADB_RecoverPhone.cmd') DO @set PHONE_PORT=%%I
adb connect 192.168.178.21:%PHONE_PORT%
echo.
:END
adb devices
echo.
echo Connected!
Click to expand...
Click to collapse
Related
Introduction
This is the first release of an installable package to allow google android phones to connect to Cisco like VPN concentrators.
Details
The installing phone will require:
* Root user privileges on the phone.
* /dev/tun file
* Kernel with tun support (or tun module). (cyanogen should be good)
* A cisco, nortel or freeswan ipsec server to connect to.
How To
Installing this version
This is available in the android market as a free application. It should be called VPN Connections. (Not sure where it will be listed as yet).
The latest version of the application can also be downloaded from here and installed using adb.
Reporting bugs
Please inform us which ROM and version that you are using, if the /dev/tun exists, its permissions, and the output of logcat from a boot, also the version of this application that you are running.
If your ROM and version are already reported in the issue list, please comment in the thread as there has been some inconsistencies in reports.
Please be very careful when lodging a bug as it may contain company confidential information. Be sure to strip any secrets or passwords from the configuration files or debugging information.
http://code.google.com/p/get-a-robot-vpnc/issues/list
Known issues
May need to load the tun module manually first.
Usernames can not contain the @ symbol.
Does not currently work with one time pass devices (Rsa keys).
Reserved for changelog.
no longer needed.
I'm not trying to ping via DNS name, so dont be worred about that. I know the other hosts are up, reachable and pingable.
Tried TCP and ICMP connections.
Unfortunately I don't have any ideas for you.. I'd like to play with it some myself though, would love to have VPN working. Could you send me / post the compiled binaries? saiboogu [at] g mail
Thanks and good luck
Sent to said address.
A little more information.
When tcpdumping the connection, packets originating from the phone go out through the device.
When tcpdumping the connnection with packets originating from the internal network through the vpn, i can tell they make it to the rmnet0 device, but never make it to tun0 device.
Ok, so I have it working now ! Wahoo.
So.. going to tidy the code up, Clean up the shell script to be android specific (and set the DNS servers).
Great. Would be awesome if you could share your binaries. What about joining this project and submitting what you did?
Tried mailing the owner of the project, many weeks ago. No response. Guess its dead.
I'm going to try to get a build environment setup for the major releases. Please PM me within the next 7 days if you are interested.
I plan to not only release the binaries, but the source code and build environment also. Hopefully the upstream developers will also take my patches.
Is it possible to connect with this vpnc to a cisco concentrator 3000 vpn?
We use CiscoVPN at our University and it would be nice if Android will be able to connect to it.
N23 said:
Is it possible to connect with this vpnc to a cisco concentrator 3000 vpn?
We use CiscoVPN at our University and it would be nice if Android will be able to connect to it.
Click to expand...
Click to collapse
I got a copy of this a few days ago from ungamed.. At first I couldn't connect to our 3000 because I was lead to believe our concentrator only supported TCP NAT traversal (which isn't supported by vpnc), but after talking to someone who knew his stuff a little better, I connected via UDP and had no problems.
So, short answer -- as long as your concentrator is configured to accept some form of NAT traversal other than TCP, this should work.
Oh, and like ungamed said the DNS still needs some work. Not a problem for me, when I VPN to work I only need a single domain that I went ahead and put in my /etc/hosts
Awesome work
Hey guys,
Let me know if you can provide a package.
Would love trying this out.
Thanks,
Kiran.
You can find out a first download here. http://code.google.com/p/get-a-robot-vpnc/downloads/list
This is the console part of the project, not the GUI, I'm still building that this week. Requires a rooted phone 1.5 or above.
I think that the dns is fixed in this first download
Ungamedplayer said:
You can find out a first download here. http://code.google.com/p/get-a-robot-vpnc/downloads/list
This is the console part of the project, not the GUI, I'm still building that this week. Requires a rooted phone 1.5 or above.
Click to expand...
Click to collapse
It only works with Cupcake? That's bad because yet there's no (fully working) UK Cupecake out
But thank you very much! Maybe then the nice GUI is ready ;-)
N23 said:
It only works with Cupcake? That's bad because yet there's no (fully working) UK Cupecake out
But thank you very much! Maybe then the nice GUI is ready ;-)
Click to expand...
Click to collapse
Working on the interface is slower than me doing the actual port.
Thumbnail::
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full Shot Preview
I tried to use that package
I can get vpn connecting, but the apps do not use that tunnel afterwards.
Code:
# ./vpnc /data/data/org.codeandroid.vpnc/etc/vpnc/vpnc.conf --debug 1 --no-detach
vpnc version ERSION
Script: not found
IKE: not found
Perfect: not found
IPSec: not found
IPSec: not found
IPSec: not found
Xauth: not found
Xauth: not found
IKE SA selected psk+xauth-aes128-sha1
NAT status: no NAT-T VID seen
got address *************
Script: not found
IKE: not found
Perfect: not found
IPSec: not found
IPSec: not found
IPSec: not found
Xauth: not found
Xauth: not found
IPSEC SA selected aes128-sha1
VPNC started in foreground...
vpnc[2366]: can't open pidfile /var/run/vpnc/pid for writing
Do I need to call something afterwards?
Btw it did not work to pass --script to /data/data/org.codeandroid.vpnc/etc/vpnc/vpnc-script so I copied that script to the default location /etc/vpnc/vpnc-script...
maybe its not executed properly?
[deleted]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
search market for "ADB over WIFI Widget"
Notes:
- Rooted phone only.
A Widget to quickly enable/disable ADB over wifi. It will work over WIFI or Hotspot. IP and Port information will be shown on the icon. SU access may needed depends on your ROM and in that case, it would be slower (experimental).
If it didn't work, please email me, we will work it out.
Other features of the widget:
- Info on the icon can be enabled/disabled.
- The label under the icon can be customized or completely disabled
- You can specify port number
- you can set SU mode, please note that this feature is experimental and will slow down the widget operations a little.
App is free now!
I decided to make the widget free. download and enjoy. I will add some cool features soon.
Awesome. How do you get it to work??? Like is there something for the PC I have to download or run??
No software required on PC
Nothing needed on PC other than the ADB itself of course.
Make sure Debug mode is enabled on your phone.
this is the command on PC:
ADB connect IPORT
IP will be shown on the icon when you enable it and you can set port (also will be shown on the icon).
you should be on the same network with your phone, you cannot use 3G IP to connect it on the internet.
Have fun!
Excellent, thank You!
bohlool said:
Make sure Debug mode is enabled on your phone.
Click to expand...
Click to collapse
Dumb question: How do I do this?
I've got USB Debugging checked in Settings -> Applications -> Development, but that doesn't seem to do the trick to use ADB via WiFi.
I'm running Ruby 1.1.1 on an HTC Incredible, Super User Mode is checked (widget doesn't seem to work without it), and the widget says it's enabled, shows me the IP/port, but adb simply says "unable to connect to 192.168.1.xxx:5555" (I changed the port to 5555).
ardax said:
Dumb question: How do I do this?
I've got USB Debugging checked in Settings -> Applications -> Development, but that doesn't seem to do the trick to use ADB via WiFi.
I'm running Ruby 1.1.1 on an HTC Incredible, Super User Mode is checked (widget doesn't seem to work without it), and the widget says it's enabled, shows me the IP/port, but adb simply says "unable to connect to 192.168.1.xxx:5555" (I changed the port to 5555).
Click to expand...
Click to collapse
I take it that you've granted the application superuser permissions? You need to then need to activate the widget and adb connect xxxxxxx
Yes, it has permissions in superuser. I tap the widget to activate, it turns green and displays my phone's IP address + port. I open up a command window (w/ admin privileges, though that doesn't seem to matter), run "adb connect IPort" and get the "unable to connect" message.
adbWireless doesn't work either.
Rock on
Suite sauce! Great app
Where are you using this app? is it on your home network or a work/university? Because I also cannot connect in university, I've found a fix for it thats need a trick. I will add the trick to next version (Maybe I do it tonight, stay tuned), I hope it also work for you.
Just a test, can you use programs such as file managers to remotely access a share folder on your computer? because you should be on the same folder to do this.
Updated!
Check the updated version. Enable Change mask option and set different mask values. It fixed on my university's network with "255.255.0.0". you need to check the computer ip and your phone ip and determine what mask you should use. The goal is to make phone that you are on the same network as the computer.
Also a bug fixed.
Have fun.
The widget itself works like a charm, thanks a lot! But - look what I see in my Command Prompt window(on desktop computer under Windows 7) after successful connection with android device:
Code:
~ # cd /sys
cd /sys
/sys # ls
ls
←[1;34mandroid_gsensor←[0m ←[1;34mclass←[0m ←[1;34mfirmware←[0m
←[1;34mmodule←[0m
←[1;34mblock←[0m ←[1;34mdev←[0m ←[1;34mfs←[0m
←[1;34mpower←[0m
←[1;34mbus←[0m ←[1;34mdevices←[0m ←[1;34mkernel←[0m
/sys #
What this??? What all these "←[" mean???
Those are escape codes. With the right terminal program, they can control the cursor or change colors among other things. They are coming from whatever shell your ROM is running.
As for me, there must have been something wrong with my Ruby installation. The widget worked just fine after restoring a nandroid of Virtuous, and works great on my wife's Droid running Sapphire.
Sent from my ADR6300 using XDA App
excellent app!
can someone tell me how to post a review on the Android Market so I can rate this app and review it?
every noob there has posted a bad review but it worked for me
AfzalivE said:
excellent app!
can someone tell me how to post a review on the Android Market so I can rate this app and review it?
every noob there has posted a bad review but it worked for me
Click to expand...
Click to collapse
open app in Market, at the top click on stars to rate and on Post Comment to write a comment.
Thanks.
Can't find it in the market...
Can you please attach apk to this thread.
Tx.
Any chance you could post the APK... I don't have market access.
Thanks!
Billy
Hi,
very great idea, works fine with desire hd.
with friendly greet
starbase64
Very useful program, thanks!
I do have a question; Is enabling su when adding the widget required to make it work?
If I leave this toggle unchecked, the widget never turns green to indicate a connection is possible.
When it is checked, everything works as expected.
Is this toggle giving the widget su permission, or is it to grant permission to the wireless adb connection?
Please clarify the function of this toggle.
Thanks!
Given the nature of this program, is the source code available for this?
I thought some people might appreciate the instructions to get adb working over WiF:
Type this in your terminal emulator on your One X:
Code:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
(5555 can be whatever you want.)
Then check it with this:
Code:
getprop service.adb.tcp.port
When it returns "5555" then run this command in the terminal (or command prompt) on your computer:
Code:
adb connect 192.168.0.151
Obviously enter your device's IP address in place of 192.168.0.151. Your computer must have adb (duh!) and your phone must be on the same network.
And you should be connected!
To tell the One X to listen for adb on the USB port instead of TCP again, enter this into the terminal emulator:
Code:
su
setprop service.adb.tcp.port -1
stop adbd
start adbd
Or just reboot the phone.
And to tell your computer to use USB for adb instead of TCP:
Code:
adb usb
I would definitely use the USB cable to push large files or even small files that you really don't want to risk corrupting (partition images you plan on dding, etc).
Very importantly, keep in mind, when your phone is listening for adb via WiFi, it's wide open... anybody that that the adb installed and knows your device's IP address can access it without a password. Again, a simple reboot will turn it off though.
HTH,
Billy
PS - Your
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
are appreciated!
JeepFreak said:
I thought some people might appreciate the instructions to get adb working over WiF:
Type this in your terminal emulator on your One X:
Code:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
(5555 can be whatever you want.)
Then check it with this:
Code:
getprop service.adb.tcp.port
When it returns "5555" then run this command in the terminal (or command prompt) on your computer:
Code:
adb connect 192.168.0.151
Obviously enter your device's IP address in place of 192.168.0.151. Your computer must have adb (duh!) and your phone must be on the same network.
And you should be connected!
To tell the One X to listen for adb on the USB port instead of TCP again, enter this into the terminal emulator:
Code:
su
setprop service.adb.tcp.port -1
stop adbd
start adbd
Or just reboot the phone.
And to tell your computer to use USB for adb instead of TCP:
Code:
adb usb
I would definitely use the USB cable to push large files or even small files that you really don't want to risk corrupting (partition images you plan on dding, etc).
Very importantly, keep in mind, when your phone is listening for adb via WiFi, it's wide open... anybody that that the adb installed and knows your device's IP address can access it without a password. Again, a simple reboot will turn it off though.
HTH,
Billy
PS - Your
are appreciated!
Click to expand...
Click to collapse
I bet our usb plugs last longer doing things over WiFi. Thanks man
Sent from my HTC One X using XDA
Many custom ROMs and even some stock firmwares can change from usb to wifi in developer settings. Jellybean has this function built in with android so you dont need root or run any commands from terminal :good:
Thanks for the tut, this helps out a lot ^_^
leolawliet said:
Thanks for the tut, this helps out a lot ^_^
Click to expand...
Click to collapse
Instead of digging up a 13 month old thread by creating a post to say thanks, just hit the thanks button next time please.
Sent from my Evita.
timmaaa said:
Instead of digging up a 13 month old thread by creating a post to say thanks, just hit the thanks button next time please.
Sent from my Evita.
Click to expand...
Click to collapse
Already did, just wanted to personally say thanks.
Pressing the button is thanks enough, it's frowned upon to dig up such an old thread with a new post.
Sent from my Evita.
timmaaa said:
Pressing the button is thanks enough, it's frowned upon to dig up such an old thread with a new post.
Sent from my Evita.
Click to expand...
Click to collapse
So tell yourself to smile upon it; we're humans, not automatons; they were being polite, and that's a lovely thing to be in this age - you're not compelled to "frown upon it". You know, "netiquette" is not law, and humanity is a lovely thing to see
i've now seen it all...
glossywhite said:
So tell yourself to smile upon it; we're humans, not automatons; they were being polite, and that's a lovely thing to be in this age - you're not compelled to "frown upon it". You know, "netiquette" is not law, and humanity is a lovely thing to see
Click to expand...
Click to collapse
It makes me happy to see some actual humanity around these stuffy as of late parts! It's at best troubling and at worse ungrateful to have a policy in place that forbids a friendly human ”thanks". When someone feels the need to let that policy actually change their own personal level of gratitude there is something very bad happening.
A button can in no way replace a real human emotion. It provides a very impersonal response with very very little meaning.
I know there's probably a policy in place around here forbidding disagreement or self-expression against something that when looked at through other eyes is absolutely without meaning or need, but as a human I feel the need to stand up for my beliefs.
Thank you for your time.
droidparanoid said:
It makes me happy to see some actual humanity around these stuffy as of late parts! It's at best troubling and at worse ungrateful to have a policy in place that forbids a friendly human ”thanks". When someone feels the need to let that policy actually change their own personal level of gratitude there is something very bad happening.
A button can in no way replace a real human emotion. It provides a very impersonal response with very very little meaning.
I know there's probably a policy in place around here forbidding disagreement or self-expression against something that when looked at through other eyes is absolutely without meaning or need, but as a human I feel the need to stand up for my beliefs.
Thank you for your time.
Click to expand...
Click to collapse
AMEN!!!
God bless you my friend; the world's in a mess, and people are increasingly becoming entrenched in "the way it is" - well not me. Who wants to "fit in" and just be passive and live as if they're "enduring" life? Some people will NEVER like you - I found that is the case, and some people WILL NEVER have anything good to say. Well, that's up to them - for me, I AM ALWAYS going to SAY thank you, and people can just dislike that all they want - it's how I am, and if they "frown upon it", that just shows how lost they are, seriously.
BE NICE TO PEOPLE!!!!!!!
God bless you all
Landed here by googling a bit abt adb over wifi
And ... BAM ! Works straight !
I'll do some scripting around it but the core usage is all there,
BiG Thanks !
(Thanks button hit but cold not help posting a bit more )
I'm very late to this thread, but luckily, as of Android 11, adb works over wi-fi (without USB) on non-rooted Android phones via Developer options Wireless debugging switches.
Hi everyone,
it might be a stupid question but I was wondering if the Remote Desktop app could be used to access my laptop via internet.
I know it works very well when the Surface and the laptop are connected to the same Wireless router but I would like to know if th same as possible, given the fact that the laptop and the Surface are connected to different (distant) wifi networks.
I searched for this but could not find a clear answer or "how to" to do it.
Thank you very much
You can do it, look up port forwarding for remote desktop. You need to setup your router to do it.. I think the default port for RD is 3389
Thank you very much
You will also have to know the public IP address of the router, do the port forwarding and it works fine. You can use DynDNS or one of the other services to keep the IP address updated. Or, you can use TeamViewer to do it without touching your router. You have to set up an account at TeamViewer, but everything is free and it works well.
drowe said:
You will also have to know the public IP address of the router, do the port forwarding and it works fine. You can use DynDNS or one of the other services to keep the IP address updated. Or, you can use TeamViewer to do it without touching your router. You have to set up an account at TeamViewer, but everything is free and it works well.
Click to expand...
Click to collapse
Well I will try both ways and see what is the most convenient, thank you for your answer
I remote in from outside networks and it works great. Now I just wish we could enable the setting to allow us to transfer files. Where it shows us the local hard drive on the remote computer and all we have to do is drag and drop.
Sent from my SCH-I535 using xda app-developers app
Can you not? Remote Desktop still supports this, at least the desktop version (haven't tried the "Metro" one).
Huzzah!
I'm actually using metro-app on a daily basis with no-ip (so i don't have to remember my own ip-adress all the time)
So all you need to do is:
1. Get your self an account at: http://www.noip.com/
2. Create a host and install client
3. Open port: 3389 on your router and point it to the right computer
4. Allow it in the firewall
5. Connect
There is ofc more steps if you want to be more specific, but I think you'll figure it out
I would have to say Team Viewer is by far the easiest solution.
Yeah +1 Teamviewer here..
Trig0r said:
Yeah +1 Teamviewer here..
Click to expand...
Click to collapse
++1 just tried this out, dead simple to use and no networking mojo needed.
Interesting you guys have chosen TeamViewer so clearly,....I've just tried it, and it will make due for now, but I need to copy and paste text from pdfs constantly and I noticed it to be extremely laggy by comparison (to RD). I'm guessing it's because it needs to download more data than the native client, but if there are any suggestions on speeding it up please post.
Remote Desktop/RemoteApp Problems
I have not been able to connect while out-of-network.
I've waisted several days of productivity trying to resolve this by myself, then on the phone with Microsoft, and some of them aren't even familiar with Surface RT. So with connecting to RD in-network is pretty easy and effective, hopefully some here can confirm that they have the same problems and/or offer possible solutions.
As I see it, there are 3 interfaces where we can connect to RD on the Surface RT: The the pre-installed desktop Remote Desktop found via swipe and search, the metro downloadable Remote Desktop, and RemoteApp via control panel).
I see where the computer is pinged and port 3389 is open, so I will state the problems I see with each when I try log into a Windows 8 Host computer:
1) pre-installed RD:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's great and your computer name is there for you and ready while logged into your account and in-network. You have options like "Connect and don't warn me If server authentication fails" that I see helped out a lot of people on Windows Server with certificate issues.
Once out of network on Surface RT, however, you get "Remote Desktop can't find the computer ______. This might mean that "_____" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
2) Metro UI:
It seems to ping the computer faster when you put :3389 at the end of your IP. However, no success after trying with and without the port ending. The messages I get are....
3)RemoteApp:
this is the solution I've seen in most tutorials,...but the reason given for not connecting is "The remote computer cannot be authenticated due to problems with its security certificate."
Instead of the option to bypass it (which option 1 gives you), there is no other option and it says "Windows cannot continue setting up this connection. Contact your workplace administrator for assistance."
This message caused me to learn more about certificates than I ever wanted to know. I've tried starting up MMC and making sure the cert listed in Remote Desktop was copied to the Trusted Root Certificate Authorites folders (both sides as local computer certificates). I've tried different combinations and haven't really gotten anywhere.
If anyone connects via #3, please post specs on your certificate if you can find it.
Any help on getting any of these methods to work is appreciated. It bares repeating that port 3389 is listed as open on my home network, traffic is forwarded to the correct PC, and all firewalls are disabled until I can resolve this.
Hello Friends~!
Today I wanted to teach you how to remotely connect to your phone, or any android device, using Termux and a PC. This example assumes your android device is on the same wireless network as your pc. In order to remote into our device, we need to install a GUI within Termux. Two good options are the termux packages "fluxbox" or "xfce4".
METHOD 1: FLUXBOX
Fluxbox is a fast and light on resources "Windows Manager" GUI that takes up far less storage space than XFCE4 (266MB) But requires the use of TightVNC on our PC to connect to. (I couldn't get RDC to natively connect)
Spoiler: WHAT IT LOOKS LIKE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WRITTEN GUIDE:
Run these commands in Termux:
Code:
pkg install x11-repo
pkg update -y
pkg install aterm fluxbox tigervnc -y
vncserver -localhost
vncserver -kill :1
vncserver
ifconfig
Take note of the ip address ifconfig gave us.
Spoiler: EXAMPLE
Type in the ip address with the port number in TightVNC and then you will be asked for the password you set.
Spoiler: EXAMPLE
When you connect, type in:
Code:
fluxbox&
Then you will have a full GUI environment!
WEBSITE:
Fluxbox
Officical site of the fluxbox windowmanager.
fluxbox.org
METHOD 2: XFCE4
XFCE4 is a "Desktop Environment" GUI, with it's own unique background and features, but takes up more storage space and takes longer to install (1270MB). This setup can be used in both TightVNC and Windows built in Remote Desktop Connection.
Spoiler: WHAT IT LOOKS LIKE
WRITTEN GUIDE:
In Termux run these commands:
Code:
pkg install x11-repo
pkg update -y
pkg install xfce4 xfce4-goodies tigervnc xrdp -y
Then we need to run this code to be able to edit the rdp port:
Code:
nano ../usr/etc/xrdp/xrdp.ini
Scroll to the bottom and set to port 5901 (change the -1 to 5901) Now we need to press the ctrl key and type "o" and press enter to write out or save the changes and then ctrl + x to quit out of vim. ( ^ is CTRL )
Spoiler: EXAMPLE
Now run:
Code:
xrdp
vncserver -xstartup ../usr/bin/startxfce4 -listen tcp :1
ifconfig
Take note of the ip address ifconfig gave us.
Spoiler: EXAMPLE
Type in the ip address with the port number in TightVNC and then you will be asked for the password you set.
Spoiler: EXAMPLE
If you want to use Windows RDC instead, just type your IP address without the port number.
Spoiler: EXAMPLE
WEBSITE:
Xfce Desktop Environment
Xfce is a lightweight desktop environment for UNIX-like operating systems. It aims to be fast and low on system resources, while still being visually appealing and user friendly.
www.xfce.org
DOWNLOADS:
Termux Apk for Phone or Android Device - DIRECT DOWNLOAD LINK
TightVNC for Windows - DIRECT DOWNLOAD LINK
You can run the command "termux-setup-storage" and see that it sends the command to your phone in the background without showing the command was ran in the terminal, and it will ask you to grant permission. You can do so and you will have more control over your phone's remote session.
I have some theories on other ways to use these remote connections, outside of building linux environments, will post updates in the comments when we get there.
This guide is all thanks to @ze7zez for asking about this in the thread below, and then educating us on connecting to our devices in a different and much more storage efficient way :> They also shared how to connect VIA USB
HOW TO INSTALL LINUX ENVIRONMENTS ON YOUR PHONE AND REMOTE INTO THEM
A low bow of respect and a huge thank you from my side!
So far, every one of your tutorials is exemplary, logically and understandably written.
In my opinion, there is no need to install vim. The nano editor included in the distro is easy to use. Just mention that ^ is CTRL and you can use commands from the menu.
@ze7zez thank you so much!!! Got the guide updated. I kept literally pressing ^ and couldn't figure it out so i used vim... nano is so much easier haha. I think if I could comprehend better then maybe this clue would have helped but here we are
Was able to figure out the remote session into the Ubuntu machine without adding anything extra, like you said was possible! Just trying to learn how to build from scratch the machine now, hopefully in a few different ways now that a small understanding of GUIs is present
edit:
Spoiler: successio!!
was able to build this one from scratch! its xfce. going to try other guis now and try to understand better before writing anything up and sharing more machines