-- SOLVED --> For those who care...
Initial issue/goal: Ports open or blocked over 3G/4g? Getting a reverse VNC connection working on an android phone.
Resolution: Ultra VNC SC basically allows someone behind a firewall or router to, without any configuration required, share their desktop with someone (you) for technical support or any other means. I use it for friends and family and such, and it works great, but the real question and purpose of this thread was about open ports on a 3G/4G connection and what VNC apps allow listening. This is what worked for me: Remote VNC Pro from the market (~$6), DynDNS from the market (free), a dynamic DNS account that is supported by the DynDNS application (like no-ip, dyndns, etc), and a personalized/configured version of Ultra VNC SC (linked below). Port 5900 works, as well as a few others, but 80, 8080, and 443 won't.
VNC Application: Remote VNC Pro (for the phone)
VNC Application: Ultra VNC SC (for the client)
Dynamic DNS: DynDNS (update agent)
Mods/Admins feel free to move this thread and/or lock delete if I am breaking any rules (like advertising?) or something.
Re: [HELP] Reverse VNC Connection
I know with 4G you definitely get a publicly accessible IP without any proxy in the middle. I imagine 3G would be the same so it should be fine in that regards.
As for open ports, any app worth its chops should let you choose which port it listens on so that shouldn't be an issue.
Why don't you just buy one of the apps and give it a try? If it doesn't work you can always return it within 24 hours for a full refund.
Trial and Error
---- ORIGINAL FIRST POST ----
Not sure if this should go here or not, but I'm trying to see if I can get a Reverse VNC Application going. Looking at existing VNC applications for Android, the only one that allows listen mode is Remote VNC Pro v1.7.7 and above. Unfortunately, since it is not free, I cannot test the listening capabilities. Listening aside, I suppose my biggest issue will be open ports. Given 3G/4G addresses (NAT, I assume?) are out of our control, does anyone know what ports are open and what ports are not?
Has anyone else tried? Interested? Suggestions? Here's what I have so far:
VNC Application: Looking at Remote VNC Pro (for the phone)
VNC Application: Ultra VNC SC (for the client)
Dynamic DNS: DynDNS (update agent)
---- END FIRST POST ----
rdude said:
Why don't you just buy one of the apps and give it a try? If it doesn't work you can always return it within 24 hours for a full refund.
Click to expand...
Click to collapse
Well the idea was to see if anyone had already tried this and/or had the application to save me time troubleshooting. Since there has been no response, save yours, I went ahead and purchased it.
rdude said:
As for open ports, any app worth its chops should let you choose which port it listens on so that shouldn't be an issue.
Click to expand...
Click to collapse
Oh, it has the option to specify ports, but which ports are open over a 3G/4G connection is what I wanted to know. I tried 443 and 80, and both gave me permission errors. Surprisingly 1723 (PPTP) works, but VNC Pro on the phone just sits on the 'please wait while listening on <ip address>' screen forever. The computer running the Single Click VNC server says that the connection was successfully acquired, but the icon never changes colors (suggesting I am completely connected). The interesting thing is that when I cancel or close the connection on the computer, VNC Pro on my EVO closes the 'listening' window and gives me a java exception error.
*sigh* any ideas? I'm guessing the connection is going through but other traffic is getting blocked or something. Not sure what other ports to try, but I will fiddle around with it in the mean time.
Edit: I tried the standard ports on a local WiFi connection. I gave the phone a static IP, port forwarded everything appropriately, and then received the same results. I'm going to take a few screenshots and send and e-mail to the developer for now.
Edit: It appears to be an issue with Ultra VNC SC. Ultra VNC and Real VNC both worked by manually adding the viewer client from the installed server while using port 5900. Sort of defeats the purpose for me, but the developer said he would try it out and (hopefully) get it working.
Edit: The dev got back to me really quickly and we figured out the issues and fixed it over the weekend. He pushed out a new version of the application on Sunday. First post has been updated for those who care.
Bumping the thread for those who are interested in what worked for me, now that everything is fixed.
Nice, been interested in this. How is the refresh rate when your phone is on WiFi and also how is it on 3G?
I tried Screencast (http://code.google.com/p/androidscreencast/), but it only runs at 3-5 FPS, so it was pretty unusable.
I've only had it working for a day, and nobody has really needed my help, so my testing of the application has only been to confirm it works. The best thing I can say, for now, is that the reviews all brag about the performance and pinch-zoom, that the developer is pretty cool and was willing to return the application well beyond the 24 hour limit, should the application not meet my needs, and finally that he fixed the issue I was having in less than 48 hours from the time I reported it to him. Overall, as far as the application is concerned, I am pretty satisfied. For example, I wrote (and edited) this post while using it over 3G from my phone. I saw all the text as I was typing, so I would say the frame rate is satisfactory.
Edit: Wait, after following your link, I think you might be misunderstanding the purpose of this application. This allows you to control a PC from your Android, not the other way around. The purpose is to supply people with a pre-configured portable application that allows you to connect to the computer without any port forwarding or security changes on their machine. The application (uVNC SC) also "uninstalls" itself from their computer after the connection is closed. To reiterate, the primary benefit is to allow you (the admin) to connect to someone else (the user) without them having to do anything but double-click on your connection.
You're right. I misunderstood, didn't know what "reverse vnc" really meant.
Sorry, I knew people confused the two, so I could have been more clear. On that note, I am also interested in a... remote connection to my Android phone. Recording, in particular, would be great for demo's and setup instructions, given so many people have android devices now-days. But yeah, this is not the setup for that. =/
brennen.exe said:
Bumping the thread for those who are interested in what worked for me, now that everything is fixed.
Click to expand...
Click to collapse
Glad to hear you got it working! I'll try installing it this week and see how it goes.
Looks to me that I want to do exactly the same. Sorry to bump the thread but seems the best thing to do.
I want to support people OTA, since I don't need high framerates, just a view at some PC settings.
I have Remote VNC Pro and it allows the phone to Listen for incoming VNC connections. But it listens on a 10.20.xxx adress, instead of my WAN 3G/4G ip-adress.
I want to use GITSO (awesome little program) for the http://code.google.com/p/gitso/ support issues.
It works flawless pc-to-pc where I have my own portforward setup, saves tons of hassle with the people I want to support.
Hi all,
Please forgive me if I post a new thread in bad location but It's my very first post in this forum. I have searched xda threads for a long time till I decided to write as I have a problem that needs al least some clue from more advanced users.
I want to use a Remote Desktop feature by connecting from my HTC HD2 WM 6.5 vnc Viewer 1.0.1.17 to my PC with WinXP HOME and RealVNC server running. (I try to do it this way as I read in one of xda threads that original Remote Desktop built in hd2 will not work for WinXP Home).
So what I did is as follows:
- Installed RealVNC 4.3.2 Enterprise and had a server running on IP 192.168.1.10.
- Set port forwarding (as I use a router). I entered LAN servers on my router settings and set TCP; 5900/start/end; IPlocal 192.168.1.10
- Done the testing through "gotomyvnc.com" (cannot post links as I am a new member)
and got positive result on port 0
- Installed vncviewer on my hd2. Both PC and PPC were connected to the same network. (actually I tried using the internet connection from HD2 too) I tried to connect by setting:
Server: 192.168.1.10::5900 (port number)
with password and without password
or
Server 192.168.1.10:0 (display number instead)
Both firewalls on my PC (XP firewall + ESET NOD Business) and PPC (Mobile Security) were switched off.
I cannot at any way connect to my PC from HD2. The errors I obtain with different trials are:
"Cannot connect to specified server"
"Connection failed at authorization"
Perhaps I missed something or forget about some detail. Or maybe the whole approach is wrong? Hope you guys will be able to give me some advice cause I am totally run out of ideas.
Thanks in advance
Mike
Hi all,
Please forgive me if I post a new thread in bad location but It's my very first post in this forum. I have searched xda threads for a long time till I decided to write as I have a problem that needs al least some clue from more advanced users.
I want to use a Remote Desktop feature by connecting from my HTC HD2 WM 6.5 vnc Viewer 1.0.1.17 to my PC with WinXP HOME and RealVNC server running. (I try to do it this way as I read in one of xda threads that original Remote Desktop built in hd2 will not work for WinXP Home).
So what I did is as follows:
- Installed RealVNC 4.3.2 Enterprise and had a server running on IP 192.168.1.10.
- Set port forwarding (as I use a router). I entered LAN servers on my router settings and set TCP; 5900/start/end; IPlocal 192.168.1.10
- Done the testing through "gotomyvnc.com" (cannot post links as I am a new member)
and got positive result on port 0
- Installed vncviewer on my hd2. Both PC and PPC were connected to the same network. (actually I tried using the internet connection from HD2 too) I tried to connect by setting:
Server: 192.168.1.10::5900 (port number)
with password and without password
or
Server 192.168.1.10:0 (display number instead)
Both firewalls on my PC (XP firewall + ESET NOD Business) and PPC (Mobile Security) were switched off.
I cannot at any way connect to my PC from HD2. The errors I obtain with different trials are:
"Cannot connect to specified server"
"Connection failed at authorization"
Perhaps I missed something or forget about some detail. Or maybe the whole approach is wrong? Hope you guys will be able to give me some advice cause I am totally run out of ideas.
Thanks in advance
Mike
(moving the post from hd2 Themes and Apps)
The following is a 3-step process for gaining remote access to your PC Via your Android phone's data connection for FREE and without a static IP.
IT USES YOUR DATA PLAN SO MAKE SURE YOUR HAVE UNLIMITED DATA PLAN OR YOU'LL BE SAD!!!
It allows you to control and view your PC by accessing Windows Remote Desktop using Pocket Cloud on your Android. I used this method on my T-mobile Samsung Vibrant and am now using it on my HTC Amaze. Currently, I have only tested this using Windows XP. I HAVE NOT TRIED IT ON WINDOWS 7. Someone smarter than I can tweak the process for Windows 7 and MAC OS. Please feel free.
I put this little solution together from some forums I found scattered all over the internet. When I needed it, I couldn’t find the complete solution in one place so; I consolidated it for you here. The VB script in particular is not my original work and I can't remember where I got it for the life of me so; my apologies to the author for not properly citing it here. PLEASE NOTE THAT I AM ONLY POSTING THE METHOD I USED. USE IT AT YOUR OWN RISK!
Now…down to business!!!!!
Here is how it works:
Your PC automatically accesses a website to gather your WAN IP information and sends an "email-to-text message" to your Android on a schedule of your choice. This ensures that you always have access to your current WAN IP address. This is important; DSL providers change your WAN IP address as much as 10 times/day where cable internet providers only do it about once/month.
You then use this information to configure Pocket Cloud (available for free on the Android Market) to connect to your home router/PC. Using the current WAN IP as the "host address" in Pocket Cloud, you can connect, control, and view your PC remotely over your Android's data connection.
Requirements:
In order for connection to work, the following must be done before you start the steps. Don't worry, these are all easy.
· Your PC must be powered on with an internet connection (obviously)
· Windows XP must have a windows logon password set (assuming you are not on a home network with an actual server).
NOTE
If you have a modem connected directly with no router, you are all set. Skip the next bullet.
· Your router must be set to forward "remote desktop" activity (port 3389) to the PC to which you'd like to connect; make sure the router doesn't block the remote desktop application (see your router manual).
· Make sure your internet security software (see your software manual) and Windows XP ("my computer" properties under the "remote" tab) allows remote access to your PC.
STEP 1. Tweak the RED ITALIC TEXT ONLY of the VB Script (attached at the bottom) in by creating a new "note pad" file; pasting it in to "Note Pad"; and saving the file as "EmailIP.vbs".
NOTE
You can test your script by double clicking the .vbs file you just created. If you then get a text message with your IP address in it, you are good to go. The text message should only take a few minutes to arrive.
STEP 2. Schedule the script to run at any interval you'd like by browsing to it from within Windows Task Scheduler. This is under Start>All Programs>Accessories>System Tools>Scheduled Tasks. If you need help with task scheduler, Google it.
NOTE
The task should be scheduled more frequently for those using a DSL home internet provider. I set mine for every 2 hours as I use DSL at home. Cable internet can be scheduled to run much less often.
STEP 3. Install and configure Pocket Cloud RDP free from Android Market. using IP just texted to your Android and your Windows Logon information.
· Create a new connection in pocket cloud.
· Enter a nick name of your choice into the "Nick Name" field.
· Enter the WAN IP which was just texted to your phone into the "Host Address" field.
· Enter your windows logon user name and password into the "User Name" and "Password" fields.
· Leave everything else alone!
· Scroll to the bottom and hit "Save."
· Tap the connection and you should be connected to your PC with in seconds.
Cheers!
I use MyPhoneExplorer, very easy and noob-proof
i use teamviewer for this...
teamviewer does not require u to have static WAN ip...
the only thing u need is teamviewer account which is free...
I have create a vpn and get the static ip from no-ip.org
.
Thread moved. Would advise you to read forum rules and post in correct section.
enox2604 said:
I have create a vpn and get the static ip from no-ip.org
Click to expand...
Click to collapse
Good choice, however, no-ip and teamviewer both require that a 3rd party have certain terminal info or it pings the server periodically. This solution keeps third arties out of the equation with the exception of a collecting your own IP from an outside URL. Again, somone much smarter than I would be able to write a script that collects your WAN from the CMD prompt or something native to OS rather than a URL. If you know how, Please do and post it here.
orb3000 said:
Thread moved. Would advise you to read forum rules and post in correct section.
Click to expand...
Click to collapse
My Apologies. I did read them and didn't see a good fit anywhere as this is neither an App nor a game. It will take me some time to figure out where threads should be posted. Thanks for your patience.
Tutorial version 1.0 by: Talbot *TBOT* Simons “Monsieurtalbot”
WHY?
I was looking around the internet a while ago for a good tutorial on this. Sadly, after many years no one had released one – and after many hours of testing I have managed install and run a mumble (murmur) server - from an Android device using a Debian compatibility layer app called Debian NoRoot. It took a lot of tinkering over a couple years to discover this working method - and it works really well.
There are many benefits to having your own Mumble server… not to mention one that fits in the palm of your hand and can be transported… Not to mention one that can act independently – INCLUDING a built in WIFI network and battery – but using this method, not only is it possible to take a private VOIP server everywhere you go – it’s possible for it to run really smoothly with any mid-range smartphone made after 2012. Broadcast your own WIFI network and connect with friends in a private offline chat within WIFI range…. Or connect to a WIFI network, forward a port from your router and expand the coverage to all of the internet… All with an old android you probably have lying around somewhere. Use it anywhere a walkie talkie might be needed, but not available. Text chat is also included and working – and it’s all as private as possible really… You are even able to encrypt your connection at that point – or simply host it locally and use it anywhere you have a large local network you can tap off of… Hotels & cruises – speak between rooms via the WIFI… etc etc. I can see this being implemented in places where internet is scarce and communication is needed… It will work on devices many people are discarding – and in a world where privacy is becoming scarce – it’s nice to know that the method of your communication is safe.
DISCLAIMER - MUST READ
I am not responsible for any data loss or device damage. Proceed at your own risk, though none of what we’re doing here should be considered risky. I’m not including pictures as I’m a busy man – but the process is quite simple and the instructions are quite exact. I think you’ll be fine.
This has been tested on several Android devices of various screen sizes and processor architectures going back to 4.0. It should work on most if not all devices. An old Android you have sitting in a drawer is a perfect candidate for this – not a bad thing to just keep installed on your personal device as well if you’re a power user like me. The program we’ll be using is able to run most if not all Linux apps … A lot of possibility here. No root is required for most of the features to work in this tutorial. Root isn’t needed if you are on an unlocked device, or if you have tethering provisioned on your wireless account. Tethering is only needed if you plan on using the device to broadcast a WIFI network to make it truly independent from a WIFI router.
Some features of the server may or may not be broken, I personally don’t require much besides a server with no password. If anyone runs into any issues down the road, please let me know!
Click to expand...
Click to collapse
With that being said – let’s begin.
___________________________________________________________________________________
INSTALLATION -
1. Download the following apps from the Play Store on your Android “server device”.
1. Debian NoRoot – The Debian linux environment (takes about 900MB space on internal SD)
2. Plumble – (mumble client) either free or paid version is fine.
3. Fing – Network tools for scanning IPs and networks.
ALSO EITHER:
Stock WIFI hotspot feature (if you have active wireless service)
OR
WIFI Tether Router – (requires root) allows for WIFI networks to be created without a WAN connection.
OR
If you just want a local server hosted and want to use your home router (with or without port forwarding for WAN access to your server) – you can do that too.
Click to expand...
Click to collapse
2. Open the Debian NoRoot app you just downloaded – let it install and set your DPI and font scale to whatever is best for your device. Typically messing with the stock settings won’t do much good for you.
3. Open the terminal that is found on the desktop of Debian, or open it from the menu if your screen is small. Execute the following commands:
sudo apt-get update
(wait for the process to finish - accept any dependencies with Y)
sudo apt-get upgrade
(wait for the process to finish - accept any dependencies with Y)
sudo apt-get install mumble-server
(accept any dependencies with Y – there will be some errors, ignore them.)
sudo dpkg-reconfigure mumble-server
(Autostart: Yes, High Priority: No, Then set the super user password when prompted.)
sudo nano /etc/mumble-server.ini
(This is where you’ll edit the server info – there is much documentation on setting up a mumble server and configuring this file elsewhere on the web… Things like server name, welcome message, server password – etc etc are located in this setting file. Save the file and go back to the terminal.)
sudo /etc/init.d/mumble-server restart
(That’s it, the server should now be running with your new settings in the background. There is no UI and no icons that pop up.)
Click to expand...
Click to collapse
4. Once this is done – keep in mind even though you set the Autostart it is not going to work in this environment – so you will need to manually start the process via it’s script file – so lets create a shortcut to it on the desktop to make starting the server easier.
The script file is located at:
Code:
/usr/bin/murmur-user-wrapper
“Two finger tap” the file and “send to -> Desktop (create link)”
You will now double click this desktop link to start your server after you open the Debian Environment.
5. You can now press the home button to put the Debian environment in the background. Open the “Plumble” app you downloaded *on the same device* and set up a new server with the following settings:
Label : LOCAL SERVER
Address: 127.0.0.1 - leave the port as 64738 or change it as you like.
Username: Whatever you want – I used ADMIN for the server device.
Password: leave blank unless you set it up in the settings file.
Click to expand...
Click to collapse
Once you save the server if should show as online. Connect to it and change the default audio setting to push-to-talk in Plumble settings… If you don’t see it online, restart the phone, or some devices require to be connected to some form of network before the server will show as online. See the next step.
5. Once the server is running you have a number of options on how you can set it up and connect to it. – if you aren’t seeing the server – attempt the following - either step A, B or C first before ripping your hair out.
A. Connect to a WIFI network – set a static IP for your network in Android WIFI settings… You can then use it locally… or you can forward the port you used in the last step to the static IP you set in your router’s settings.
B. Broadcast a stock android hotspot – if you have active wireless service and tethering provisioned or an unlocked device – if you don’t, some custom Android roms will activate and broadcast a network anyway, some won’t… depends on device – your mileage may vary. This is cool for direct device to device communication but will not allow you to use it over the internet. Wireless carriers block a lot of ports incoming.
C. Open WIFI tether router – set it up based on your device. This app requires root but is the most likely to work in a completely offline scenario with no available external WIFI network or when you don’t have service but want to turn a couple phones into walkie talkies in the grocery store. Option B and C are very similar in function but C works with no service – in a plane, a cruise ship, the middle of nowhere, etc etc.
Click to expand...
Click to collapse
6. At this point – we can start connecting other devices… Either get the mumble client for PC/Mac or download “Plumble” and “Fing” on another android device. iPhone also has free mumble clients and network scanners.
7. Open “Fing” on the server device and run a scan if you are on a WIFI router network. Note your server device’s IP address and confirm that the devices you are trying to have connect have an IP address themselves. You may need to run “Fing” or another network scanning app on the secondary device to determine the server device’s IP address… Especially if you are doing this with option B or C for connection.
8. Open Plumble (Android) or your PC/Mac/iOS mumble client and configure it to the server IP you determined in the last step… As long as they are on the same network you should see the server online… Connect and set the push to talk setting on the second device. You should now be able to chat between the server device and the secondary device… and you should be able to connect multiple others as well.
9. Reboot the device.
10. At this point It’s 100% installed and ready to go. The server boot process to recap is quite simple.
- Connect the server device and secondary devices to the same network, hotspot, whatever.
- Open “Debian NoRoot” from a fresh device boot. Sometimes a fresh boot is needed for the server to run properly.
- Once Debian environment is fully loaded, two finger click the shortcut we created for the murmur server and choose the top option – “execute”
-Open Plumble on the server device and connect to the local server profile you created
- Determine the server’s IP address based on how you connected and set up the client devices.
- PROFIT.
Click to expand...
Click to collapse
I hope you enjoyed this tutorial and find it useful – if anyone takes these steps, please help the community and provide screenshots that I may add to this post. The information was sourced and pieced together from so many places… I’d like to thank… Google search - as well as the developers behind the apps used in this tutorial. I'm amazed that after all this time something just clicked and low and behold - it works!
Cheers and best wishes all!
Just an update - this is surprisingly stable, and I have had a server running on an old android device for over 2 weeks with no downtime.
Awesome work! I've been debating trying to port Murmur to Android for a while now as I have an Android STB sitting around that would make a perfect server.
zyperion said:
Awesome work! I've been debating trying to port Murmur to Android for a while now as I have an Android STB sitting around that would make a perfect server.
Click to expand...
Click to collapse
There's already an armhf distro for murmur on debian... This is actually still working great. It's the only reason this works... Same package for the raspberry pi. =]
Any app for Android that allows you to boot I to a chroot Linux environment this will work on...
Sent from my LG-US996 using Tapatalk
Yeah, it's a very clever solution that seems to be working pretty well. I'll have to give it a try! I've also been looking into trying to get Ubuntu installed on my Minix Neo X5 instead since I don't have any need for it as a media box anymore which makes Android far less desirable than a functional Linux install.