Anyone else having trouble with att tilt vpn over edge? I've had several smartphones in the past, the last being tmobile wing, and have never had any problems creating a vpn connection with url exceptions. With this new tilt it seems like I can connect the vpn only over wifi, it does not attempt to connect to the vpn when just using edge. I've reset the device several times both with and without the att customization.
Any ideas for this problem would be appreciated.
Thanks,
-J
TILT VPN Connection problems
I have been trying to make VPN connections over EDGE and 3G also. I find that the connection does get made if I connect manually, but as soon as I try to access something through IE, RD or Opera, it drops the connection. I have seen the connection maintained for up to a minute, but I cannot access anything.
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Round 1
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Sorry for that last double post. I did go back to the att kiosk again today and tried another tilt, which had the same results. I decided to return the one I had purchased and think i may try the regular htc kaiser with the front camera.
If anyone can verify that that version of phone works with pptp, that would be great.
From your last message I tried a few other things and I too was able to manually connect ( even get a prompt for login credentials to the vpn ) however the IE still will not try to connet with the url exception or keep the vpn connection open after IE is opened.
It's sad to think the att tilt is not working in thie regard. It takes away quite a bit of functionality for those who do use the vpn feature.
-J
PIE will "ignore" exceptions for work connection using EDGE
I see similar problem with 8525 at&t WM 5.0 device (HTC Hermes) exact version Microsoft ® Windows Mobile™ Version 5.0 with the Messaging and Security Feature Pack. 5.0 OS 5.1.478 (Build 15706.3.5.2)
PIE will "ignore" exceptions for work connection using EDGE. However other applications like “ActiveSync” and “Terminal Service Client” work properly.
If Wi-Fi connection used for Internet, PIE as well works properly.
FYI on previous device 8525 Cingular
Microsoft ® Windows Mobile™ Version 5.0 OS 5.1.195 (Build 14955.2.3.0)
work exceptions works with PIE
it continues...
I ordered htc kaiser, had it shipped opened it, configured, and the results were.....
it would use work exceptions as it should, dialing the vpn when using PIE and calling trying to access a host in the exceptions list.
It did not however want to connect to the host even after establishing a connection with the vpn server.
I dont know why, but I thought of checking the ip address with PocketLan on the gprs interface. The ip address was a 10.x.x.x but the kicker was the subnet mask using 255.0.0.0. That may cause a problem with routing as my vpn tunnel is not a full 10/8 but still a 10/16. Anyway I decided to try the online tech chat and spoke with "Marcus"
I asked if there had been any changes in the last month or so on as far as ip address scopes using wap.cingular He said yes. I'm still not sure if that was actually the case or not . I went ahead and upgraded to the pda connect unlimited to use the isp.cingular, as the "pda personal max" just uses wap.cingular.
I had to connect several times with the isp.cingular to have the connection get a public ip address rather than a nat'd 10.x.x.x. It DOES now work properly with url exceptions, connecting the vpn, the whole ball of wax with isp.cingular
Unfortunately I had already returned the ATT Tilt so I dont have any way to test if it was the att software causing it or not. If anyone would like to let me borrow one for a few days we can do that
I am going to test with another vpn connection using a 192.168 or 172.16 etc. ip scope and see if it works with wap.cingular getting a 10.x.x.x address.
Anyways, thats it for now. I'll post again after the vpn test with the different scope.
Thanks,
-J
Today I setup a vpn server with a 192.168.x.x scope. Using wap.cingular i was able to connect to the vpn and hosts within the vpn.
I tried again to connect to the 10.x.x.x vpn and try to edit the routing table using the PocketLan but each time I try to edit something it returns an error.
I'll have to try to find another utility or see if there a way to edit the routing table.
I'm hoping theres a way to change the default route for the 10.x network.
Here's some of the info when connecting over a wap.cingular connection
ip: 10.67.x.x
gateway: 10.67.x.x ( same as ip address )
subnet mask: 255.0.0.0/8
DNS: 66.209.10.201, 66.102.163.231
WINS: 10.11.12.13, 10.11.12.14 ( kind of hard to imagine any reason for wins entries? 10-11-12-13 seems like they may just be fake address. I dont know how window mobile does it's resolution, but that doesnt seem like it would be in the customers interest to be pointed to non-existant wins, if thats what they are. This may just be place holder entries for the PocketLAN software?)
Here's some of the info when connecting over a isp.cingular connection
ip: 166.128.x.x
gateway: 166.128.x.x ( same as ip address )
subnet mask: 255.255.0.0/16
DNS: 209.183.48.11, 208.183.48.10
WINS: 10.11.12.13, 10.11.12.14 ( same comments as before )
See Arin Whois for this netblock
OrgName: Service Provider Corporation
OrgID: SPC-10
Address: 442 Route 202-206 North
Address: # 485
City: Bedminster
StateProv: NJ
PostalCode: 07921-0523
Country: US
NetRange: 166.128.0.0 - 166.255.255.255
CIDR: 166.128.0.0/9
NetName: NETBLK-CDPD-B
NetHandle: NET-166-128-0-0-1
Parent: NET-166-0-0-0-0
NetType: Direct Assignment
NameServer: NS1.WIRELESSDATASPCO.ORG
NameServer: NS.CDPDSPCO.ORG
Comment:
RegDate: 1993-07-09
Updated: 2005-01-07
RTechHandle: WDSPC-ARIN
RTechName: WDSPCo Helpdesk
RTechPhone: +1-215-489-7599
RTechEmail: [email protected]
OrgTechHandle: WDSPC-ARIN
OrgTechName: WDSPCo Helpdesk
OrgTechPhone: +1-215-489-7599
OrgTechEmail: [email protected]
# ARIN WHOIS database, last updated 2007-11-02 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
I just thought of testing tracreroutes form both isp and wap.cingular. It does then show the problem with the ip information when trying to route.
When using the tilt though at first, none of this seemed possible at the time ( as I thought I was going a little nuts ) since the url exceptions never seem to attempt to connect to the vpn at all. As if the exceptions were ignored when using anything except WIFI.
Thats it for now. Post something new later.
-J
jakedahs,
Very informative. Looks like its' been a few weeks. New insights?
Best,
Things are still working good with the kaiser and the isp.cingular. I haven't come across another ATT Tilt again to test it out again. Any other things you can think to test to put on this forum?
Thanks,
-J
LOL! I'm so far behind, I don't have a clue.
Tilt and VPN PPTP
jakedahs said:
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Click to expand...
Click to collapse
I too am having issues with my Tilt and VPN. So when I got the Tilt 10 days ago, I had a blackberry 8300 (Curve), when i left the store they had me on the same BlackBerry Data plan. The VPN worked fine - Perfectly in fact. A few days later when I questioned why I was still using a blackberry plan the CSR at AT&T said I should be on a PDA data plan and changed my service. After that the VPN stopped working. I contacted AT&T chat support and also called their complex data device support department and after changing a bunch of settings on the phone they finally gave up and said they could not support the VPN option. Nice Huh?
When I get home I am going to try connecting over WiFi and trying the VPN. This should tell me if the routing / VPN issue is related to traffic over AT&T or if there is something wrong with the phone.
Additionally, when the VPN worked it used to show a " balloon status " telling me VPN was connecting. Now it no longer does that. Even if I do force the VPN to connect and then try to use the connection is disconnects immediately.
I'm guessing you're going to have the same result. If you'd like we can run through some tests using different scopes of vpn's. I'd be interested in trying the tilt again since I know the kaiser I have works ok and I'm not crazy
VPN
jakedahs said:
I'm guessing you're going to have the same result. If you'd like we can run through some tests using different scopes of vpn's. I'd be interested in trying the tilt again since I know the kaiser I have works ok and I'm not crazy
Click to expand...
Click to collapse
What kind of tests were you thinking?
wap.cingular - isp.cingular / netowrk settings
jakedahs said:
I ordered htc kaiser, had it shipped opened it, configured, and the results were.....
it would use work exceptions as it should, dialing the vpn when using PIE and calling trying to access a host in the exceptions list.
It did not however want to connect to the host even after establishing a connection with the vpn server.
I dont know why, but I thought of checking the ip address with PocketLan on the gprs interface. The ip address was a 10.x.x.x but the kicker was the subnet mask using 255.0.0.0. That may cause a problem with routing as my vpn tunnel is not a full 10/8 but still a 10/16. Anyway I decided to try the online tech chat and spoke with "Marcus"
I asked if there had been any changes in the last month or so on as far as ip address scopes using wap.cingular He said yes. I'm still not sure if that was actually the case or not . I went ahead and upgraded to the pda connect unlimited to use the isp.cingular, as the "pda personal max" just uses wap.cingular.
I had to connect several times with the isp.cingular to have the connection get a public ip address rather than a nat'd 10.x.x.x. It DOES now work properly with url exceptions, connecting the vpn, the whole ball of wax with isp.cingular
Unfortunately I had already returned the ATT Tilt so I dont have any way to test if it was the att software causing it or not. If anyone would like to let me borrow one for a few days we can do that
I am going to test with another vpn connection using a 192.168 or 172.16 etc. ip scope and see if it works with wap.cingular getting a 10.x.x.x address.
Anyways, thats it for now. I'll post again after the vpn test with the different scope.
Thanks,
-J
Click to expand...
Click to collapse
Since they had me change my plan and settings around I called and confirmed that I now have the PDA Connect Unlimited plan. However, in the phone's connection settings what should the two network and subsequent individual network setting be? Mine was set to Media Net and Media Net.
I tried setting it to ATT ISP but it still did not work.
I just use isp.cingular all the time. Have you created work url exceptions for your vpn connection? The problem I was having when I had the tilt is even though I had the exceptions it would never attempt to dial the vpn when going to a web site on the vpn network. I'm thinking it may have been ATT that cripled the phone somewhat. The regular HTC Kaiser I have now works fine.
VPN - TILT
So I confirmed that if I use my WiFi connection the VPN works perfectly.
There is some issue with routing over AT&T data network. I tried chatting with their online chat support and they could not give me the settings I needed. It was clearly beyond their scope of knowledge. I will try calling their complex data support department to see if I can get the right settings.
How can a company offer data services and not understand their own network?
Vpn - Tilt - Settings
I found this posting at the cingular.com forum.
Since I need to call tomorrow to confirm my provisioning and my data plan subscription I cannot tell if they will work but I thought I would make the info public.
Here's what I've done to VPN using L2TP successfully... (someone else)
- Have PDA Unlimited Plan
- Call to have your account "provisioned" to use isp.cingular
- Create a new connection using the isp.cingular settings
- Configure device to always use that connection
- Create a new VPN connection
- Import appropriate certificates (if necessary)
- Disable (preferably remove) Proxy settings in Registry
- Create an Exception list for Intranet addresses
- Configure device networks to use isp.cingular for Internet access and vpn for 'Your Work/Intranet' network
One thing I have noticed is that if I let the device connect automagically to VPN, it will disconnect after a short period of inactivity. If I manually/force connect to VPN, it stays that way until I disconnect session.
I can connect either via 3G or Edge with no issues/problems.
VPN Access over anything on the tilt would be nice
I am unable to either one of my 2 vpn's using any connection configuration. I It seems like it wants to connect but then gives me an error msg telling me to check username and password.
Can anyone shed anylite what I'm doing wrong?
Tilt Vpn over Edge
With a little patience i figured it out! if you connect to your VPN first and then go to IE it will disconnect you. But if you go to IE, Opera, whatever first and then go to the address that you have in your exception list the tilt will connect to MediaNet and then connect to your VPN server and work!
every morning when i wake up, i use home wifi to surf a bit before i go out
the n1's network *always* get stuck, as if it can't resolve any hostname
Using that "Phone Info" app (*#*#4636#*#*), i ran a ping test:
Ping IpAddr: Pass
Ping Hostname(www.google.com): Fail: Host unreachable
I suppose this means either my dns setting is incorrect or the dns is down,
so i did another test using "DNS lookup" app from market,
i tried resolving hostname with 8.8.8.8 (google's public dns) or my network operator's dns
both's working fine
rebooting the phone always fix the problem, and the problem seems to appear after wifi usage
I suppose this means the switching between wifi / 3g some how get the phone into a stuck situation?
Is anyone experiencing anything like this? I guess I am not the only one
mods: yea this might not be exactly android development, but this is the closest sub forum
please move this thread as you see appropriate
Same here.
There was another thread on this issue, suggesting clearing the cache and using setprop (or some command like that) for dns settings through GScript Lite. But a reboot always works for me, when the other methods fail.
glad that i m not alone : )
are you referring to this?
http://forum.xda-developers.com/showthread.php?t=640029&highlight=dns
i will try that app and see how it works,
is there any easy way to do a setprop whenever i need? i m unrooted
I had this problem (and not just between WiFi and 3G, but 3G and Edge, 3G and no service, etc.) on the stock Nexus 2.1 software, and also on my Milestone under 2.0 and 2.0.1 (though MUCH less frequently under 2.0.1).
You don't typically need to reboot, just go to airplane mode and back.
This might be a reason to unlock and install another ROM, because I have never had this problem under any Cyanogen build I've used (just 5.0.4.1, 5.0.5 and 5.0.5.1).
Setprop doesn't seems to work without root
$setprop net.dns1 8.8.8.8
$getprop net.dns2
192.168.0.1
I will file a bug report to see what google says
n1 is a good computer but not such a good phone, its been months since initial release but they have yet to fix many basic bugs
I had no problem with my god old g1 back then
got this issue too, but no need to reboot the phone, just disable and enable the wifi again will work.
I know that this thread will probably be over in approximately 3 posts, but I figured this was the place to ask to get a good answer.
I am part of staff for a site that uses my IP to enable staff functions. These functions are set to the IP I'm on. However, it never works considering my IP constantly changes when I'm on the T-Mobile network, and I do not have access to wifi. Is there any possible way at all, to be able to make this work, either from my N1, or on my PC using my N1 as a 3G hotspot? I'm not all that knowledgeable about networking, but I'm thinking there has to be some possible way to make this work somehow. Maybe I'm wrong and it is one of the impossible things to do on a cell network.
Thanks for any help.
how often does it change ? is the running at home or the pc u are tethering with it ? are you using a 3g network service for a server
Every couple minutes at least. One minute it's for example, something like 208.54.27.50 and in a matter of 5 minutes the last two digits could be changed. I use the 3G hotspot at home and there's no difference from that and using the phone's browser itself. I do not use T-Mobile 3G to operate any servers.
If it is via your provider you have no control over it changing as they assign you a dynamic IP. If you were at home you could set it to a static local IP (Over WiFi) but outside your LAN on T-Mobile's WAN you have no control over DHCP
All I use for internet access on the go and at home is the 3G hotspot that I get from my phone. Would I need an actual Wifi connection from an ISP other than T-Mobile to set it to a static local IP?
looks like that just cant be done.. either ur site changes ur auth to id pw based one(atleast in ur case)
or ..
if its a job of just checking somthing, u can find a friend or family member with a 24/7 online pc(with a a static ip) and just do the job thru a remote desktop connection
All right guys. Thanks. Very much appreciate your thoughts and for not flaming me due to an obvious answer. Thank you again.
I have done about everything. I can connect to my Android phone (using tether), my house, other open networks PERFECTLY, but unfortunately my gym uses a WEP network and I cannot get my tablet to connect to their network.
I have rebooted, forgot the network and set it up again (a million times) I have done EVERYTHING. My Android phone can connect to the gym network perfectly. Any suggestions?
Anyone have any suggestions? Does anyone connect to a WEP secured network and know that this works?
I had the same problem and found out the solution changing some values in the set up router.
Sent from my X10i using XDA App
I'm connected to our home browser which uses WEP. I think it's a matter of settings/wireless and networks/Wi-Fi settings/add wi-fi network. Once you are in the 'add' page, it asks about security, you should be able to input the data.
Jim
I have had same problems, honeycomb handles WPA and WPA2 enterprise networks weird compared to gingerbread. I have had problems with connections too. Try to use the "wifi advanced config editor" and make sure settings are correct for that network (after you attempt to connect to it in settings app). I hope google fixed this problem in ICS or i will be furious. Most of these kind of bugs are laziness on coders or just people who missed lines of code and then don't want to release an update (or wait till next update release rather than a hotfix).
1337GameDev said:
I have had same problems, honeycomb handles WPA and WPA2 enterprise networks weird compared to gingerbread. I have had problems with connections too. Try to use the "wifi advanced config editor" and make sure settings are correct for that network (after you attempt to connect to it in settings app). I hope google fixed this problem in ICS or i will be furious. Most of these kind of bugs are laziness on coders or just people who missed lines of code and then don't want to release an update (or wait till next update release rather than a hotfix).
Click to expand...
Click to collapse
So just to make sure I understand...
Basically the way I originally connected was that I let the tablet scan for networks, and it found the gym network. Once it found the gym network, I selected it and entered the password. I left the proxy and DHCP settings alone and pressed connect, and cannot get it to connect.
What you are suggesting that I do is delete the network, and add the network MANUALLY (where I input securtiy, SSID, passcode, etc.).. Is that right?
So I installed the Advanced Wifi tool, to no avail.
Here is the funny thing. I have a Samsung Epic 4G phone which uses Gingerbread, and it connects to the WEP just fine. I installed the Advanced Wifi on there as well, and went through the settings that were autoconfigured for the gym. Each setting matched my tablet perfectly, yet my tablet cannot pull an IP address, but my phone can.
I'm having the same issue. Thought it was the tab, just received replacement and still a No Go! Every other device in my house connects to this network. And the Gtab also connected perfectly until recently... no clue what to do now.
So I have a Galaxy S7 Edge and I cannot even get to my router settings page (192.168.0.1) when connected to wifi. All other devices work in my home currently.
Using Angry IP Scanner on my desktop, my phone showed up under 192.168.0.105 with an insane ping of 295ms and no name.
I changed the ip settings to static and set the DNS to 8.8.8.8 and 8.8.4.4.
The ping improved to 19ms, but still has no internet. I then switched back to DHCP and it went to 695ms ping.
I get "ERR_Connection_Refused" in chrome on the phone
This is all I can tell you other than my screen is shattered, but It has been for a long time, and I don't know why that would effect the connectivity just right now.
Remember this is also happening on cellular. I have restarted both the phone and the modem and router.
Something really weird just happened as I was typing this, an instagram notification came in, but when entering instagram, nothing loads.
Edit: I can make calls just fine.