On my old Rom. it has IP Renew button and i can see the IP address. When i load the new 1.31.139 rom. The feature disappear.... :shock:
Any ideas? :roll:
Derek
Only a work around.
Renew IP feature is available in pocketWinc.
vxIPConfig also lets you renew IP leases.
Related
In my office, we use a Cisco VPN concentrator with OTP.
I tried to connect this afternoon using my soft token to generate a key, to no avail. I suspect the MS IPSec/L2TP implementation.
Anyone has a client working on WM5?
Cheers,
Hal
There are a few around, i'm about to start testing any / all that i can find as my work are about to replace our local PPTP VPN server with the Cisco Concentrator setup at our head office.
So far, i have only tested one, with limited success - Bluefire Mobile Security VPN: http://www.bluefiresecurity.com. This client was able to connect and authenticate using the group authentication however it failed at obtaining an IP Address. They at least have a trial version available for download so I was able to test it without having to pay
As i test more VPN clients, i'll post my results in this thread and it would be great if others could do the same as i really want to get this working.
Cheers,
Chris
Hi,
I've used Bluefire (Trial version) for a few days with Cisco Gateway of my Company, and it worked perfectly.
The only limitation is that when connection is lost (it happens very often in mobility) the sw is not capable to resume the connection, so you have to digit usr/pwd again..
"Me too!"
Here is a post with my experience on BlueFire - http://forum.xda-developers.com/viewtopic.php?t=52386
Did you find anything better for IPsec VPN for WM5? Thanks.
Problem with IP tunnel address on bluefire here. I did speak with Dennis Komisky who is the CTO of Bluefire at MEDC and he mentioned that the latest version fixes many Cisco related issues.
Alas, when I fired up the latest trial although it did correctly auto sense and set up my DH pairs, I still had the IP tunnel address issue. Unfortunately, I haven't had time to pursue this though even though Dennis told me to contact support and drop his name if I had problems....
Sleuth255 said:
Problem with IP tunnel address on bluefire here. I did speak with Dennis Komisky who is the CTO of Bluefire at MEDC and he mentioned that the latest version fixes many Cisco related issues.
Alas, when I fired up the latest trial although it did correctly auto sense and set up my DH pairs, I still had the IP tunnel address issue. Unfortunately, I haven't had time to pursue this though even though Dennis told me to contact support and drop his name if I had problems....
Click to expand...
Click to collapse
Hmm, and I got a completely reverse experience - I can connect with BlueFire to our corporate Cisco VPN w/o a problem (I had to manually set IKE/IPSEC parameters though) and absolutelly cannot connect with AnthaVPN... I wish their log messages were more detailed.
I upgraded my rom to 217 ROM w/CF2,ringers,themes and A2DP.
Ive done everything to allow for the DHCP to assign the 8125 an IP.
When I go to settings/connections/wireless LAN/ advanced it says associated to network with mac address and an IP address that locked in from my home router. When Im at work the IP address there is the IP address assigned from my home router. I click renew IP and it doesnt change.
When I go to settings/network cards/network adapters I select SDIO WLAN Wireless adapter I click on USe server assigned IP address and that doesnt work. There is the same Use specific IP address as the same IP address at home. There are actually hex figures in the use specific IP address.
When Im at home I cant get the wifi to surf the net either.
By the way I set the power setting mode to BEst performance. Im using a DLink 624 at home and a Belkin Wireless G+ at work.
When I had the stock Cingular Rom it worked flawlessly.
Help!?
Thanks
IS there some way to flush out the settings of the wifi card????
There seems to be some problems with AKU2 ROM's with certain routers. Not sure about either of the two you mentioned, but there are a few of us with problems with the new linksys SRX400 router. I will save you the trouble, at least in my situation, none of the 2.X ROMs work. I tried iMate, Qtek, both 2.17 and 2.8 and all the customized ones from summiter. Also it doesn't appear to be limited to the 8125, MadMonkeyBoy over on HoFo had a similar proble with his s200.
The only suggestion I have seen is to put in a manual IP, try to connect, disconnect, and then change it back to DHCP. It didn't work for me, but YMMV.
EDIT: take a look at this thread
http://forum.xda-developers.com/viewtopic.php?t=48431
Messing around with it here at work I guess by doing this..."The only suggestion I have seen is to put in a manual IP, try to connect, disconnect, and then change it back to DHCP. It didn't work for me, but YMMV. " It seemed to work... I was at lunch and of course I wasnt able to read this but I was able to see a wifi connection Ive used before like at paneras or something and It said connected but didnt give me an IP address...Ill have to try to do it manually connect disconnect DHCP see if it works at home,.
UNLESS...anyone else has any info...
Thanks!
Update...went to lunch and like I said I had a connection but not able to surf...
I went back to work and the connection that WAS working stopped working so I went to manually use an IP address...then I did assign automatically...and Im back in business at work. Ill try it when I get home and see if that works.
Seems kinda mickey mouse if you ask me...why is it like that???
Ill confirm more when Im home later.
Yep gotta do the assign IP address then click ok then do auto assign click ok and Im good to connect to any wifi as long as its open or I have the key.
Seems kinda mickey mouse...
Why is it like that??? The stock cingular rom didnt make you have to do that to connect.
I'm currently running wm5 ivan w/rd
i keep having this problem where i try to connect to a network, and it connects, but i can't do anything.
When i open up my ipconfig it shows the network ip address as 169.254.x.x where x is always something different. My router shows the mac address on the network but it's unreachable.
Does anyone have any idea where this ip is coming from? I've tried different radio versions, and it happens so far with 1.1.13 and 1.1.15 on both wm5 AND wm3.
169.254.xxx.xxx is a class of ip addresses set automatically to a device, when this can't connect the dhcp server. is a reserved network.
if your router is set as dhcp server, you must verify the link connection with pda. else you must configure the correct ip address manually to the pda.
download and run vxIPconfig and use that to release and renew a new IP from the DHCP server
Nine times out of ten this is caused by bad encryption settings. If you put in the wrong WEP key for example this is what you would see. You don't get error messages when it's wrong, which is kind-of by design and desirable for security reasons.
I'm downloading vxipconfig right now. I did a search last night and was reminded of 169.254.x.x coming up on machines when winsock is corrupt.
Another web site said something about how a pda will connect to the first computer with activesync through wifi under this ip address and try to sync, and then it will get a normal ip address. I don't know if this is true with this device.
@closer what do you mean verify the link connection? The router shows the pda's ip address in it's connection manager, but for any computer or pda i don't know a way to "verify the link" other than look at it. There's no command for this. The router is set up to correctly assign dhcp as i have 2 computers and 2 xbox's connected through lines, and 2 computers through wifi. I know i can manualy set the ip, which i often do for everything but the laptop, but this is a pain in the ass to try and find out the gateway of every single router when i'm out in town. That's a workaround, not a fix.
@Black6spdz I was using Myipconfig and it would release and renew to just a different 169.254.x.x. I'm going to try vxipconfig when this happens again.
--Well, last night i got pissed and abandoned working on it. Low and behold when i wake up today it's working fine and has the correct ip address. That sucks, because now i have no idea what was wrong.
so...
-It's time to go connect to some other networks and see if it resolves correctly.
-Then i'm going to go through the 3 different radio versions and see how they affect it.
when I had that problem it was because my settings were set up incorrectly.. If i were to use gprs, it'd work fine. But wifi would not. So i had to make a seperate setting with generic entries and not set up proxies. then wifi would work. sort of a pain. but it would work...
Anybody having an issue with inability to obtain IP address after connecting through USB to host.
I upgraded device to WM6 and now it can not get IP address from DHCP server.
Search and you shall find......
http://forum.xda-developers.com/showthread.php?t=270384&highlight=activesync+server+address
There are 2 solutions, however to return the default configuration follow my reply (last post in the thread).
Andy
Hey coders,
I have a question regarding the networking subsystem in Android.
I know that dhclient.conf in linux will allow a "timeout" parameter that lets you set the DHCP request timeout. I'm wondering if there's some way to do that in Android. It's not immediately obvious to me, so that's why I'm asking.
Before, when I was stock, my phone had no issues connecting to my work's wireless SSID--even though it would sometimes take a long time to obtain an IP address, it would eventually connect.
Now, I've flashed CyanogenMod 5.0.5.3-N1, and I can still associate with my work's wireless network, but it appears to timeout the attempt to obtain an IP address too soon. My Palm Pre and my laptop can connect to the same, and I've verified that my stock ROM can also still connect, but when I flash to CM, I can no longer obtain an IP address successfully anymore.
I'm wondering how difficult it would be to modify the DHCP obtain IP timeout?
Thanks everyone!
--Hans
same problem here as well also on cm5.0.3.1 and 5.0.6.test2...
Haven't tried modifying it, but you can look at /system/etc/dhcpcd/dhcpcd.conf. Here's a man page.
Doesn't seem to help. I added "timeout 360" to the bottom of dhcpcd.conf and it doesn't increase the time that passes between "obtaining IP Address from <SSID>" and "unsuccessful".
Must be something else in android?