Not positive this is the best forum for this, but here's an issue I'm having:
I utilize an IPSec VPN to connect to a "work" network to get access to a specific internal website, however, once on the page, further links from the page go to a shortened hostname ("servername" instead of "servername.domain.dom"). For some reason on my devices (GS5/Kindle Fire HD; 4.4.2 and 4.4.4) have no problem finding the page utilizing the "servername.domain.dom" but they show "website cannot be found" when it switches to just the hostname. This is annoying as each link I follow beyond the main page I have to edit the URL to.
My computers at home (Win 7 and OSX 10.9), my iOS devices, as well as our Android 4.4.2 powered tablets at work (stock android VPN app, same webpage shortcut on the home screen) all have no problem following the switch to the shortened hostname. My iOS devices have been tested on LTE/Wi-Fi; the work tablets operate on Wi-Fi (NOT the network it VPNs to) and 3G/LTE. My personal devices (all) are on AT&T, "work" devices are on Sprint
What am I missing here? (I setup the tablets @ work, thus I'm really at a loss for what I'm missing to do on my personal stuff)
Unfortunately I have no control over VPN settings/protocols... I'd love to figure out why this is happening only on my devices...
Hi Guys/Girls,
Living in Australia we've got some issues getting to Netflix.
We need to use DNS servers for proxies so we can connect (Geoblocking and such)
I'm not looking at wanting to set the DNS on the Wi-Fi connection itself, as I often use networks out of my own Wi-Fi connection at home.
I know I need to set IP addresses manually in the Wi-Fi menu for the DNS option to show up.
I am unable to get Netflix to work at all.
I've tried 2 used apps on my phone (Galaxy S5)
DNS forwarder - http://goo.gl/VGpr0M
Static DNS for Wifi - [STRIKE]http://goo.gl/LQV8br[/STRIKE] - Since looked and stated it's not working on 5.0 yet..
Testing the apps on my KitKat 4.4.2 S5 - This works fine.
Tested on my Nexus 9 5.0 (LRX21L) - Fails to work (Netflix is not available in your country)
Does anyone know if the way of setting DNS with apps is broken since the changeover?
Since lollipop, android seems to have a problem with custom DNS server...
I've post on diffrents threads on XDA and opened a issue on the android tracker : https://code.google.com/p/android/issues/detail?id=79504
Ah, that makes sense then.
I shall keep an eye on that!
Somewhat baffled here, I have a Unitech TB100 tablet at work that I need to get a VPN connection setup on. Its a re-branded ruggedized Asus tablet running Android 3.2.
Being as it runs 3.2, many of the VPN apps (which require 4.0 or higher) wont work, so I am trying to use the built in IPSec VPN client to talk to our Sonicwall firewall.
I have followed the directions at support.software.dell.com/kb/sw8658 but when I go to connect, the tablet says that the attempt failed to connect and the Sonicwall logs say that it started negotiations, then they say that it received duplicate packets and its dropping the duplicates.
My phone is a Droid 4 running Paranoid Android 4.4.4 (a build from late Oct) and it connected right up when I used the same settings as I used in the tablet.
Anyone have any experience or thoughts with this?
Thanks
Aaron Z
An update for anyone who may run across this down the road, the problem is that the tablet is connecting via Straight Talk (using the ATT network) who apparently blocks PPTP VPN connections (see straighttalkwirelessforum.com/viewtopic.php?f=6792&t=1203070 for more info)
When I tethered the tablet to my Page Plus phone, the VPN connected right up. When I switched back to the Straight Talk data connection, it refused to connect again.
Aaron Z
Hi all
I've setup VPn tunnels to my office on my S9+. I've setup a PPTP from the built in client and IPsec and SSL from the Fortinet Client and none of them are working.
I'm sure that authentications are correct as I use same settings on my laptop running windows 10 and on a iPhone 7 plus.
Anyone with the same problem?
This might not help you exactly but there seems to be an issue with the stock ROM and VPNs. Adguard, which blocks ads via VPN, was also having the same issue and the devs have reported it to Samsung from what I understand. The fix will probably come during a later update since VPN issues are a bigndeal, especially for people who need to use their devices in a corporate environment.
My VPNs include one PPTP and one IPSec/PSK, and they both connect without issues on four different Verizon S9+ phones.
tasmaniandevil69 said:
Hi all
I've setup VPn tunnels to my office on my S9+. I've setup a PPTP from the built in client and IPsec and SSL from the Fortinet Client and none of them are working.
I'm sure that authentications are correct as I use same settings on my laptop running windows 10 and on a iPhone 7 plus.
Anyone with the same problem?
Click to expand...
Click to collapse
Same here, PPTP not working on my s9+. But IPSec/PSK working (slow speed)
Hi
same here . It's little different for me
PPTP work with S9 but in hotspot, i can't connect to PPTP VPN on my laptop with wifi of S9 !
There is a really problem with PPTP ...
I opened ticket here : https://forum.xda-developers.com/galaxy-s9/help/hotspot-vpn-pptp-issue-t3765773 !
New firmware for s9+ and s9
I m waiting new file for my s9.
Bug of vpn pptp is solved ?
not solved with last firmware ...
jpbl1976 said:
This might not help you exactly but there seems to be an issue with the stock ROM and VPNs. Adguard, which blocks ads via VPN, was also having the same issue and the devs have reported it to Samsung from what I understand. The fix will probably come during a later update since VPN issues are a bigndeal, especially for people who need to use their devices in a corporate environment.
Click to expand...
Click to collapse
Hola
I just wanted to give you a heads up that Adguard dev's have figured out a temporary workaround to make the their VPN ad blocking features stick. You'll need to check their forums for the actual setting (or use their nightly release which has the setting enabled by default). I have this setting enabled and now I am able to browse ad free for the most part without issues.
I've just update the phone and it's now working yet. Besides that the problem is even worst because I can't even connect VPNs on my laptop if using the phone as hotspot.
I've reported to Samsung and I'm waiting for a call and a remote assistence but if I can get a fix in a few days the phone will be returned because this is a big issue for my work.
tasmaniandevil69 said:
I've just update the phone and it's now working yet. Besides that the problem is even worst because I can't even connect VPNs on my laptop if using the phone as hotspot.
I've reported to Samsung and I'm waiting for a call and a remote assistence but if I can get a fix in a few days the phone will be returned because this is a big issue for my work.
Click to expand...
Click to collapse
I used this functionality fairly frequently with my (Verizon) S8+.
I've just completed about an hour of testing with my (Verizon) S9+.
I tried the USB tether, the Bluetooth tether, and the Hotspot networking on the phone. In each case I established a network connection to the public Internet without issue.
The VPN connections from my Windows 10 system, however - using that S9+ connection - all fail now with one exception.
The PPTP, L2TP/PSK and IKEv2 connections (that all work[ed] with my S8+) will not connect using my S9+.
The one exception is the Microsoft-specific SSTP variant, which tunnels over port-443. That one will connect with the S9+ in all three networking scenarios - USB, bluetooth and Hotspot WiFi.
This seems to indicate that the new phone does not pass TCP port 1723 and/or GRE 47 (PPTP) and UDP ports 500 and/or 4500 (L2TP and IKEv2) through it's network tethering and the WiFi connections.
Bummer.
At least I can still use SSTP to get to my server resources - which is 90% of my VPN needs anyway - but the other connections are dead now.
Connections FROM the phone, using it's built-in PPTP and L2TP profiles to host networks, continue to work properly on the S9+ -- as they did on the S8+.
afh3 said:
I used this functionality fairly frequently with my (Verizon) S8+.
I've just completed about an hour of testing with my (Verizon) S9+.
I tried the USB tether, the Bluetooth tether, and the Hotspot networking on the phone. In each case I established a network connection to the public Internet without issue.
The VPN connections from my Windows 10 system, however - using that S9+ connection - all fail now with one exception.
The PPTP, L2TP/PSK and IKEv2 connections (that all work[ed] with my S8+) will not connect using my S9+.
The one exception is the Microsoft-specific SSTP variant, which tunnels over port-443. That one will connect with the S9+ in all three networking scenarios - USB, bluetooth and Hotspot WiFi.
This seems to indicate that the new phone does not pass TCP port 1723 and/or GRE 47 (PPTP) and UDP ports 500 and/or 4500 (L2TP and IKEv2) through it's network tethering and the WiFi connections.
Bummer.
At least I can still use SSTP to get to my server resources - which is 90% of my VPN needs anyway - but the other connections are dead now.
Connections FROM the phone, using it's built-in PPTP and L2TP profiles to host networks, continue to work properly on the S9+ -- as they did on the S8+.
Click to expand...
Click to collapse
That is the Snapdragon version? Does it have a special ROM from Verizon or is the stock Samsung?
Maybe that is the difference
tasmaniandevil69 said:
That is the Snapdragon version? Does it have a special ROM from Verizon or is the stock Samsung?
Maybe that is the difference
Click to expand...
Click to collapse
Stock Verizon (SD845 8.0) S9+ compared with a stock Verizon (SD835 7.0) S8+. I suppose the difference might be explained by going from Android 7 to Android 8, but I have no way of testing that hypothesis at this time.
(The last phone I modified was a 2013 Motorola RAZR. I've subsequently switched to using my phones as phones, rather than as a hobby. )
If someone has a different experience with employing a networked platform's VPN while using a similar phone in a tethered or hotspot configuration, it would interesting to know.
My own successes with the phone's built-in VPN (PPTP and L2TP) - as separate from the scenario described above -
apparently differ from those of others in this thread for reasons I cannot explain.
I'm in the same boat - a new S9 and can't connect to my work VPN when using the phone as a hotspot. It works fine on S8 and Iphones. Does anyone know how to fix this? This is a critical issue for me as I work remotely quite a bit.
julianskipworth said:
I'm in the same boat - a new S9 and can't connect to my work VPN when using the phone as a hotspot. It works fine on S8 and Iphones. Does anyone know how to fix this? This is a critical issue for me as I work remotely quite a bit.
Click to expand...
Click to collapse
I think there is no fix yet. I had someone from Samsung support connected to my S9 last Tuesday and they could not find anything so they escalated the problem inside Samsung but until now no further news.
S9+ work with IPSEC!
My Samsung S9+ work with IPSEC - tested on Andoid version 8.0.0..
grube007 said:
My Samsung S9+ work with IPSEC - tested on Andoid version 8.0.0..
Click to expand...
Click to collapse
What CPU does it have? Is it unlocked or from what network/provider is it?
tasmaniandevil69 said:
What CPU does it have? Is it unlocked or from what network/provider is it?
Click to expand...
Click to collapse
CPU - Exynos 9810 - 2,7 GHz, its on Croatian network - T-Com ( T-mobile ) - locked.
New update in germany : G960FXXS1ARD1
Maybe a good patch ...
My S9 unlocked (SD) can connect to my L2TP/Ipsec VPN but disconnects within a minute or so (even if the connection is under constant use.) I have another Anrdoid 7 device (and a Windows 10 laptop) that has no problem with the same VPN/router/WiFi combination and can stay connected for hours. I don't know how to escalate this with Samsung in a way where they just don't blame my other hardware.
https://eu.community.samsung.com/t5/Galaxy-S9-S9/VPN-PPTP-Broken-with-HotSpot-Galaxy-S9/td-p/522153
So I have had my Galaxy Tab S7 (non +) for a while now, and overall, am very happy with it. I have only one problem, using a Linux machine for work and wanting to VNC to it, to use my tablet as a second screen (with an Headless-Ghost-Display aka dummy HDMI plug).
Regardless of my specific use case, any VNC connection that I try to establish over TCP/UDP, using my Galaxy Tab S7 as the client, behaves VERY oddly. First, it will work for like 1-10 seconds, then the connection cuts out and the VNC screen freezes on the tablet (not the actual tab hardware freezes, really just the VNC image), while logs on Host and Client still act like the connection is just fine. Only when disconnecting the frozen VNC session from the Tab Client, does the Host SOMETIMES detect that the connection is lost (sometimes, the host still doesn't realize it until I shut the vnc server down by force).
And even weirder, it then, 9/10 times, completely messes with the hosts Wi-Fi connection, and makes it unable to reach any sites before resetting the Wi-Fi connection.
The issue does NOT seem to be the host computer, as it happens with other LINUX hosts as well (oddly, any remote connection from the Tab to Windows works just fine).
The issue is NOT with any specific VNC client I use, as I tried A LOT and it happens on all of them. (oh, and I also tried many VNC servers, including NoMachine with it's own NX protocol, same story)
The issue also does not seem to be with my network, since connecting to the same host laptop, or any other VNC host using any other client device on the same network, works just fine.
The issue seems to be something specific to VCN connections that happens on the Galaxy Tab S7. And only going over TCP/UDP. Using a ADB reverse connection to have a wired VNC connection with the Tab S7 works just fine (be it kinda slow and sluggish sometimes).
This is as far as I can manage to track the problem down, since, as described above, any log of any host or client doesn't really give any usable error messages and just acts like everything is fine until the connection is forced shut. After a lot of digging, I found few others who did report a similar problem, but no one had any solution.
My only guess at this point, is that the KNOX security Samsung built in has some kind of problem with it? And as far as I know, on the Galaxy Tab S7, that's built into a hardware ship?
Maybe someone here has a neat idea? This is kinda frustrating and baffling to me :O