Related
Is it possible to sync using activesync over the internet without running an exchange server? I'd like to be able to sync my XDA while I'm out and about to my PC at home.
:shock: :?: :?:
been trying to do the same for ages , but never found out how to do it
It can be done, under a few conditions:
1. You need to have a static IP address for you PC
2. You need to install Pocket Hosts or a similar free utility to map the WINS host name to your PC's IP address.
3. Your carrier / ISP must not have a firewall that blocks ports 5678 or 5679 (T-mobile seems to block this)
Remote active sync was designed with a local area network in mind and it is configured to connect to you computer by using the WINS name and not using an internet based DNS name. When you connect over an internet connection from your XDA, it is not able to find you PC.
If you install a free utility such as Pocket Hosts (http://zimac.de/cestuff.htm) you can configure the Pocket PC to be able to find you PC. This utility will allow you to configure you Pocket PC to map your PC Name to an IP address (similar to the HOST file on a Windows based PC)
Before I had the unlimited GPRS plan, I created a dial up connection to an ISP on my PocketPC Phone and it works perfectly. However, when I try the same thing over the GPRS connection, it does not work. From my end, it looks like T-Mobile blocks ports 5678 or 5679 on their firewall, which are the ports that remote active sync uses to complete the connection. (It looks like it is about to work, but then fails to complete the connection)
I have tried to convince t-mobile to fix this, but they keep claiming that it will not work out of the box, they don't know how to make it work, and they won't support it. They try to "upsell" me the sidekick or other device. I can't seem to get through to the right people. It seems crazy that a setting on their end blocks us from being able to sync over the air. After all, what is the point of a data connection if you are still restricted to using a cradle to sync. I understand that they don't want to support this and walk people through setting this up, but blocking the functionality seems pointless.
Anyone tested this on ATT? With number portability starting, I may have to explore other options. Anyone have an in at T-mobile that can get them to open up these ports on the firewall?
try www.yahoo.com
get an account (if you don't have one already)
login -- click on mail
the click the tab for addresses
on the next line to the right you will see the word "sync"
this will take you to download intellisync for yahoo
then follow instructions
sync you pda and your good to go, you will have your info on the internet and sync from anywhere
one more thing if youown a palm os and a pocket pc pda and you want to have both devices with same info (contacts, mail, notes etc. etc.)
the change the settings on your intellisync for your other device and resync
hope this helps it did for me...
Hi, I'm from the Philippines and my Network is SMART Communications. I tried synching with my active sync via GPRS but it seems it can't find my PC eventhough I used Pocket Hosts utility. It seems they block the port too. Anybody from Smart to please open the gate for us.
I've setup up my Win2k PC as dial-up server. And with the help of the Pocket Hosts utility, I can now be able to sync my Outlook over the air. But the call charges is killing me.
Jose
I've been investigating this myself too - and have to say T-Mobile's attitude is also alive and well here in the UK on O2 (via crapphone-whorehouse data support team).
I was actually shouted at by one of their 'tech' guys when I tried to persuade them that it could technically be done, but I needed to find out whether they were blocking the relevant ports. He eventually hung up on me! Fantastic service, eh!
I've been trying to get ActiveSync working over the Internet for the past few days and have finally managed to get it to work reliably. There are a couple of things that I have found...
Firstly, at least one of the ports required for ActiveSync does seem to be blocked when using GPRS (Vodadone UK in my case). Setting up a normal dial-up ISP connection results in first time connections to ActiveSync every time. It would be nice to know why there is problem over GPRS.
Secondly, my device was still connecting as Guest. Whilst reading through various other forums I found a fix that seem to work for this but it involves deleting a registry key. I wouldn't recommend it as I have know idea what else this key might be used for but it certainly solved the problem for me. The key I removed is HKLM/Ident/Username value is guest. The key is replaced automatically at some point (maybe after a reset) so if it stops working, you have to go and delete it again! There must be a better way....
That's great information, thanks.
I now have my device remote synching!
Just to summarise my steps to get things working on my XDA II:
1) XDA: Set up new work connection (don't you just hate the organisation of conenctions...) to a dial-up ISP over GSM, as O2 UK also block the ports required for activesync.
2) PC: Open sockets 990, 999, 5678, 5679 on my firewall
3) XDA: Use pockethosts to set up the IP address for my PC name
4) XDA: Change HKLM\Ident\User from guest to my normal PC logon user id
5) PC: Set allow network connections in activesync
6) XDA: Manually Connect to the ISP connection
7) XDA: Open activesync and click synch - away we go!
As an update to this, I had to do a full restore at the weekend after loosing all my data on the XDAII. The problem was not related to these changes but it made me look again at the Ident key. There are two keys normally like...
HKLM/Ident/Name Value<Your chosen PDA Name>
HKLM/Ident/OrigName Value<Pocket_PC>
This time I changed only HKLM/Ident/OrigName to the same value as in HKLM/Ident/Name and it connected first time. Also, this value does not seem to be reset unless you do a hard reset on the device. This may be better than changing the Username value though I have yet to try either on another computer where my preferred connection should actually be as a Guest.
Got it working
Thanks to andyclap's suggestions I finally got it working. It looks like T-mobile does not block any ports, but without the registry hack the error I got was the same as when I tested this over a dial up connection and blocked the ports on my firewall.
The other change since my last post is that I am using WM2003 and it requires you to set up a VPN connection to the PC instead of just using PocketHosts for the name resolution.
I am seriously frustrated here:
I have an Ameo 16 GB (T-Mobile UK) and for the 1st couple of weeks remote desktop was working fine, then suddenly it stopped working.
I thought I broke the settings somewhere, so I double-checked everything. The T-Mobile Ameo comes with the default T-Mobile Internet connection pre-configured. It actually states "This connection is pre-configured. It cannot be modified."
The default settings are programs that auto connect to the Net should connect using the default T-Mobile Internet connection, and programs that auto-connect to a private network should use "My Work Network".
"My Work Network" has no values set anywhere.
Normal Internet access is fine in either IE or Opera (branded by T-Mobile as Web'n'Walk).
I have changed so programs that auto-connect to private network use T-Mobile Internet connection, same result as before.
I have set up a custom Internet connection for "My Work Network" using "general.t-mobile.uk" as access point, "user" as username, "pass" as password and domain left blank. I can connect to the Internet with these settings, but not via Remote Desktop.
Sometimes, normally after having re-booted the Amea and manually connected to "My Work Network" (as per settings above) I can connect, but it drops the connection while I'm still typing in username and password.
Normally I get either of these error messages when trying to connect via Remote Desktop:
"Cannot connect. Likely reasons are:
1) Specified computer name or ip does not exist.
2) A network error occurred while establishing the connection"
or
"Cannot connect with current connection settings. To change your connection settings, tap Settings".
I have cleared storage memory on the Ameo five times. I have phoned T-Mobile tech support who basically told me to sod off - apparently as long as the device can browse the Net they've done their job!
I have had T-Mobile replace the device and this morning I received a brand-spanking-new Ameo. I fired it up, let it go through the customisations, and reboot, then I tried Remote Desktop without changing anything or installing anything. And I got the same as above!!!!!
Please, guys, I'm desperate! Any help is very welcome here! I do network support for a living and I got the Ameo because I can fit a server's entire screen in and have a seperate keyboard. Except now I can't use it!
I used to have a Universal, which I sold to help finance the Ameo, so I'm truly stuck!
Oh how I wish I could unlock the damn thing and flash a better ROM to it!
Just as an update, yes, I've tried using "My ISP" as well, with the same results. And yes, everything's just peachy on the servers I need to connect to - I can connect to those servers using other devices.
And no, using Logmein is NOT an option and please don't even mention any form of VNC - you have to be seriously foolish to run VNC on a server, you might as well pay for some banner ads that say "Come hack me!"
Please don't give me advice on setting up routers, or Remote Desktop on 2000 Server, Server 2003 or Server 2008. I can do those quite well.
What I cannot do is get my damn Ameo to connect and stay connected and I'm absolutely desperate for help there!
the same
my ameo on t-mobile has done same thing, stopped working about 2 weeks ago, was working fine till then, only reason i bought the damn thing (anmd yes, i too ebayed my exec, i regretting it
so anyone out there got any ideas? i have same problem using ICS so i am guessing either a network etting on the phone, or some idiot at t has closed rdp traffic (tried chanmging a port number to 80 on a test box behind my router, still no go)
What is the operating system on the target pc first off. as i had that problem with a hack fix on vista home premium
all i had to do was to re-apply the fix.
as far as remote desktop the Ameo 8gb model ( x7500) didn't have rdp on it so i used one of the ones from this forum but under another section ( i think it was networking but do s earch to find them )
needless to say mine has never stopped working
a good test is try it from your local wireless home network if it's a home pc, and if ti works then look at the forwards on your router, make sure 3398 is still forwarding to YOUR pc and that your pc still has the same IP.
if you have a static ip and no router. always check your firewall settings.
as far as other possibles if your internet is working and all other data connections then there's no reason it SHOULDN'T work as t-mobile do not filter out 3389 port.
it has to be a problem at the target machine or network in that case.
but feel free to tell us more about the target pc and how it's connected to the internet and maybe we can find a solution
also what RDP client are you using on your Ameo
Cyberjak, the target machines vary: Server 2003 Enterprise Edition running ISA Server 2006, and Server 2008.
RRAS is installed on the non-ISA servers, while ISA of course takes over where RRAS left off. In all cases ports 3389 (TC{P & UDP) is open for inbound access, and on the ISA box it is open for in and outbound access.
Had you read what I wrote in my second post you would have seen I need no help in setting up RDP. I build, support and maintain networks for a living and trust me when I say the issue is NOT with the remote servers, but with the Ameo! I can use a collegue's O2 Touch Diamond and connect to any of the servers, but not the Ameo 16 GB.
I'm using a default T-Mobile Windows Mobile 6.1 setup as my Ameo has never been unlocked or flashed, and I'm using the stock standard Remote Desktop client that came pre-loaded and that used to work.
The issue is either with the Ameo, or with T-Mobile blocking RDP.
NanoRuler said:
Oh how I wish I could unlock the damn thing and flash a better ROM to it!
Click to expand...
Click to collapse
Why can't you do this? Is your phone owned by the company and they would frown if you modified it? AP4 includes Remote Desktop Mobile, so you might try that ROM if you do unlock.
My device is a 7510 and Olipro's unlocker doesn't work on it. I have been explicitly told that the unlocker might brick it
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
I will give T-Mobile a ring today and see, I guessed it would be t-mobile as I ave a whole range of different RDP servers I connect to and none worked!
lol, T-Mobile took all of about 2 minutes to enable my RDP again, told them I knew it was there prob as I read on XDA-Developers, got to love the internet nice one NanoRuler
NanoRuler said:
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
Click to expand...
Click to collapse
RDP Port filtering or NAT misconfigured !
bhermer said:
lol, T-Mobile took all of about 2 minutes to enable my RDP again, told them I knew it was there prob as I read on XDA-Developers, got to love the internet nice one NanoRuler
Click to expand...
Click to collapse
Just realised what T-Mobile said in their e-mail "I have came across someone else with this problem" - was that you? That WOULD be funny!
Way I look at it if we don't stick together we'll get shafted by big corporations!
Used to know a guy who had something printed on the reverse of some of his business cards. It read "Doing business with your firm is like having sex: it gives one a feeling of warm bliss.....while being screwed!"
Thanks to T-Mobile I know what that feels like! Having said that I'll also categorically state the last guy I dealt with at T-Mobile knows his stuff and was very helpful.
Curious, it does lead to believe something about the ports being like group policy's that they use as the voice over ip ports only are open for WnW Max customers usually unless you scream at them after being with them for a long time. heheh
Nano, no offence mate but i've been doing similar work for years as well but it's sometimes the simple things so you can understand me asking.
you would ask a client the same thing.
NanoRuler said:
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
Click to expand...
Click to collapse
A possible solution for those of us on T-Mobile's standard web n walk
Sorry to resurrect this thread, but I thought I'd post my experiences here in case anyone else (like me) searches for a solution to enabling RDP on T-Mobile (UK at least).
I was having the same problem with remote desktop, it saying that the server was not available. I phoned up T-Mobile's helpdesk as recommended here and after getting past first line support (who didn't know what remote desktop was, and tried sending new connection settings to my phone to resolve the issue) I got through to someone who knew what they were talking about. Turns out that I'm on T-Mobile's "basic" or "handset-only" web-n-walk package, and it's not possible to use RDP on this. I assume they block the relevant ports. They told me that I could pay an extra fiver a month to upgrade to a version of web-n-walk which can handle RDP.
Well I told them I would think about it, but instead tried to find a way around it as the one or two times I need to use RDP are certainly not worth a fiver a month. My solution is probably only suitable for the more techy of us, but without much work and with no prior experience I managed to set up a SSH tunnel using FreeSSHd as a server running on my windows server (although a normal windows box should work fine - http://www.freesshd.com/) and zaTunnel as a client on my phone (http://www.zatelnet.com/zatunnel/main.php). Both programs are free.
Basically my phone takes all RDP connections and tunnels them over SSH to my windows server, which then turns them back into RDP connections. T-Mobile have no idea I'm using RDP, and if they block the SSH port in the future I can always change FreeSSHd to run on port 80 (for web). This will also work for other protocols T-Mobile might be blocking (FTP springs to mind).
Just thought I'd post this in case anyone was in my situation of needing RDP on their standard web'n'walk.
Cool! Thanks for posting your rather excellent work-around! I will certainly be referring people back to your solution.
I think T-Mobile's out of order for not allowing RDP on all plans, without absolutely clearly stating that on some plans it isn't allowed.
You're the customer and you pay for some bandwidth. Short of illegal activities, what you use that bandwidth for is none of their business.
T-Mobile Grrrr
Many Thanks for this thread.
My Remote Desktop stopped working on my phone last month but co-incidently it was around the time I was re-intsalling my server and also flashing numerous roms to my phone so thought it maybe something with that.
But then realised I could remote desktop over my wireless at home and from other networks across the net so it wasn't anything to do with config on my side. Thought either phone or network.
Flashed a rom with remote desktop that i KNEW worked and still nothing...
Thought - this MUST be T-Mobile... glad I'm not the only one.
Have sent an email and hopefully they'll enable Remote Desktop on my line.
There is no way I'm gonna start paying an extra £5 a month for something I've been using for the last 20 months as part of my package and have removed wihtout any notice/warning.
i'll tell 'em where to shove their £5 extra a month
SOLVED - But I'm not sure how, I was redesgning the app so that I could put it up here for other leo owners to test and gave it one last go to take a screenshot of the error to show people what I was looking for and viola it starts working (I never changed the TCP code) sorry anyone who finds this who has the same issue but it just randomly started working!!
Hi fellow devs,
After a massive googling session I have not been able to find an answer to the following issue:
I am writing a TCP client/server app with my PC as the server and the client being my HD2.
I am writing the app in VB.net using the .net compact framework 3.5 and the windows mobile 6 sdk.
I just cannot get the following code on the client side to work over wifi:
Code:
Dim ParsedIPAddress As IPAddress = IPAddress.Parse("192.168.1.10")
Dim client As New TcpClient()
client.Connect(ParsedIPAddress, 7209)
I get the following exception:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Click to expand...
Click to collapse
If I connect the phone via active sync it will work and I can send and recieve data ok so it appears there is no issue with the code itself.
While connected via active sync - if I turn off the server side app I get the following exception:
No connection could be made because the target machine actively refused it
Click to expand...
Click to collapse
However the exception message remains as the original if I do the above but using wifi so it just is not able to establish a link at all (or not even trying) using wifi??
-----------------
I have tried:
1. Ensuring that windows firewall on the server is off and not getting in the way of anything
2. Ensured that my mobile has got an active wifi connection and can see the machine (wifi remote control apps such as GRemotePro work ok)
3. Turned off all other types of data connection (GPRS,3G) to make sure my mobile has only one route out
------------------
Is there anyone out there who has successfully got TCP to work with the .net compact framework and if so how???
Should I be using another class rather than TCPClient maybe the underlying Sockets class?
Any help would be greatly appreciated.
Cheers,
Prime.
P.S. I don't mind if people only have a solution in C# I'm happy to do any translation etc...
Socket class also fails
Ok so I've tried the socket class now as well and that fails in exactly the same way over wifi, ensured that I can ping my device and ping my pc from the device so clearly the underlying hardware is working just not for the TCPClient or Socket... Any ideas anyone?
Have you enabled port forwarding for the relevant port and IP address in your wireless router?
That's the only thing that springs to mind for me.
Thanks for the reply but...
Hey John,
Thanks for trying to help although unfortunately this does not bear any consquence in this particular situation, you only need to do port forwarding if Network Address Translation is going on between you and the end point. In this case the endpoint (IP + Port) is on the internal LAN with no address translation in between. It appears the the internal WIFI adapter is not being accessed correctly from the application i.e. this is an internal issue on the phone not an issue with the network in general as I can run the same code via active sync and it works also I can convert the project to a standard windows pc app and run the same code from a pc and it works. Oh and of course every other damn (this is really wierd) wifi app I've got works so something with the .net cf and wifi maybe??
Cheers,
Tony.
A development...
Ok so I have dug out my old Orbit II just to see if this was device related and low and behold it is ARGGGHHH!!! The app works just fine on the Orbit II over wifi.
Does anyone know of any policies, security or otherwise, that would stop the HD2 (leo) from being able to use wifi from the .net cf?
<<--delete-->>
Generic reasons for communication failures
Hi
This is a pretty generic problem, I'm afraid you can't give an exact idea of where is the problem so I can't give also an exact solution.
Usually a communication problem is due to one of this three
1) The server does not listen or does not receive
2) There is a problem with the network
3) The client does not make the call
Type 1 should be checked trying to connect to the server with a PC or a laptop. You should be able to make the client run in a PC.
Usually when a (web) server has a (web) tcp service stopped, when you try to connect to it it rejects the connection (this is what that of "the target machine refused it" sounds to me). Start then the (web) service on the server. Change (web) for your application.
My advice is that you should have something in the server side where you could run a wireshark sniffer. Then you would see all the traffic coming from the PDA and see if your client is sending packets.
Type 2 are the ones that can be checked with a ping. Maybe there is a firewall somewhere dropping the packets.
Type 3 may be due to several things
a wrong code (I don't know, there is a lot of time since I made programs)
you're trying to connect to a dns name that can't be resolved. Try with IP address.
You have a wrong network configuration. The server should be in the same network but client is not able to get the server's (or the router's) MAC with the ARP protocol. So it doesn't make the call.
I hope it helps.
Regards
This morning I was confronted with something weird. My phone all of a sudden could not connect to a remote VPS server via POP3. It would just say No Connection.
The same phone however could connect to everything else, including other services on the same remote server. And, it could connect to other servers using POP3. If I switched to WiFi, it then connected just fine.
Drove me nuts trying to figure out what the issue.
Obvious things were checked, firewall, pop3 server etc... to no avail...
So finally, I figured that Verizon was having some weird 4G problem related to port 110.. I had the POP3 server, listen on a secondary port... Still nada...
While looking at the POP3 Server configs, I saw that they now had support for ipv6, but that by default it didn't listen to them. So I changed the configuration and bang.... the phone connected...
It was apparently trying to connect to ipv6 since the time I found it was failing.
Wonder if anyone has run into this.... Looking at the logs, my phone is the ONLY device connecting via ipv6, everything else is using ipv4.
Well this turned out to be pretty simple.
IF you publish an AAAA record for a host, and you are using Verizon 4G, it will use the AAAA entry for the host in liu of the AA record.
In my case, this had surprising results that once I figured it out made sense, but at the time caused a lot of confusion as to what was the trigger for the action that was taking place.
krelvinaz said:
Well this turned out to be pretty simple.
IF you publish an AAAA record for a host, and you are using Verizon 4G, it will use the AAAA entry for the host in liu of the AA record.
In my case, this had surprising results that once I figured it out made sense, but at the time caused a lot of confusion as to what was the trigger for the action that was taking place.
Click to expand...
Click to collapse
Yes.. you learned the hard way that LTE was rolled out with native IPv6 (and preferred stack too). Pretty smart to setup a new network using IPv6 and save us the headaches of upgrading later after the fact...
I have a grandfathered Unlimited Verizon Data Plan that my company is paying me to have. I do not like Verizon, and am out of contract, so I recently purchased a Nexus 5 and plan on paying monthly with Ting. I have to maintain a "company phone" but using Google Voice, and importing all my accounts, it is really trivial that I would be using the Nexus 5 on a different carrier, since they only subsidize their employees, the device does not actually belong to them.
Instead of leaving my GS3 in a shoe box somewhere or selling it, I wanted to try using it as a dedicated hotspot for my apartment since I live in an area that has capped data from ISP's and no real solution (read FIOS) yet.
I purchased a Netgear Wireless Bridge Adapter WNCE2001 and set it up to connect to the phone's wifi hotspot and plugged that into the WAN "internet" port of my router running Tomato 1.28 firmware.
All seemed ok as far as ability to surf the web, use netflix from my TV, etc however there was a huge problem with some of the things I host from my internal network, such as media servers Subsonic, and Plex.
I am not able to access anything hosted on my internal network from any external network, even though I have not touched or altered my configurations - just replaced the WAN / "internet" port of my router with the tethered data connection.
After days of research and reading I have attempted a few fixes, although none have truly worked so far:
1) I tried connecting the phone to an open VPN server and then routing that traffic through the built in wifi tethering . This indeed worked - I followed some threads linked below, and was able to verify that now everything on my network was using the Open VPN connection - however I could not figure out a way to forward the ports appropriately and access Subsonic or Plex from the outside world.
http://forum.xda-developers.com/showthread.php?t=1993689
http://forum.xda-developers.com/showthread.php?t=2317841
2) I attempted using SSH tunnel from a remote Linux Server and although I could verify tha the tunnel was getting data piped through, I could not actually access Subsonic or PLex from the outside world. I tried to use tsocks to force all traffic for each service to use an established SSH tunnel but did not have much success.
It is important to note that these methods were tested on a shared server of a friend of mines, as far as I know they do not have root access and can not alter the open VPN or Open SSH configs or manually open ports on the server side. I wanted to just test it out to verify that it could work because I do not have a dedi or vps at the moment, I would consider getting something small from digital ocean or Amazon EC2 if this could actually work.
3) Lastly, I tried to use this port forwarding app, which as far as I can tell did absolutely nothing
Any help or direction is much appreciated, at this point I am more frustrated because after hours of reading and trying things out I feel as though I am now even more confused as to why this isn't / can't / could be working?!?!
Another thread I found here that seems like maybe it could be similar is the ability of getting NAT free with XBL using tethered data. I dont play video games, but I am wondering if something similar could be done using a crossover cable to allow for opening up ports through the wireless ISP as well? The older computer I use to host my media stuff from is running Ubuntu, and I have a Macbook Laptop, I only run Win7/8 in VM's on occasion - ideally though I want to find a solution that only uses the Linux Laptop, the phone, and the router - I can't leave my laptop home.
TLDR;
Halp! :silly:
[old desktop]- - - - ->{ROUTER]- - - - - >[WIFI ADAPTER]- - - ->[TETHERED GS3]- - - >[VZW]- - -> INTERNETS :good:
How to I send media servers from one side to the other and avoid all the NATing and dynamic IP's ? :victory:
I use versavpn with verizon and connect with openvpn. They give 3 ports to forword and dedicated ip. You chose the ports u want to forward on there web site. I have plex and remote desktop and a ftp server running on my unlimited data Verizon plan 300 gigs used a month for 3 years now. This has worked OK for me. I also ditched the tethered phone and went for a 4glte router instead much less hassle.
Sent from my LG-VS980 using XDA-Developers mobile app