I am brand new to the PDA world, but have been in IT for 10 years. I'm trying to use my X30 for different things at work (mainly Terminal Services). I have configured our connection settings and key, I get connected with excellent signal, I get an IP via DHCP, but I can't ping any IP's on the network nor can they ping me. I've read through the Wifi guid, FAQ's, and the Wifi threads but haven't seen this problem. I am running ROM A05. Any guidence would be greatly appriciated.
I got the same problem. The DHCP Server won`t assign my X50v an IP Adress if i use our Netgear AP nor if i use the SMC AP. But i do get an IP Adress if i use a Asus Pocket AP with the same settings as with the above mentioned AP.
Its wierd and won`t help you much but thats my problem here and i just wanted to let u know: U R NOT ALONE :approve:
i hope this will help. i had that prob b4. but i tried to assign it manually then soft restarted the turned it to auto assign again. dhcp server is assigning it well since then. can view the ip on the dell utility properties since then :) i cant figure out the logical thing i did but it worked :)
__________________
"The ideals which have lighted my way, and time after time have given
me new courage to face life cheerfully, have been kindness, beauty, and
truth." - A. Einstein
So if you're getting a 169.254 address it means that there is NOT communication at the right layers with the DHCP server.
Even if you filled in the gateway you would not get anywhere.
It's likely to be an issue with the WEP configuration, (turn it off and try it) or a router issue.
1. Turn off power saving on the Axim's Wifi interface and test.
2. Turn off WEP and test.
3. Check the firmware on the router is up to date.
Armagedon> I've seen that problem with the Netgear routers before. It seems that some of them send DHCP packets that don't (IMO) fully confirm to the RFCs. WM2003 seems more sensitive than other OSs to this issue. So your XP machine will be fine, WM2003 will not. I should point out that just because I say that it does "not appear" do not assume that I'm 100% right. It was a conclusion I came too late one night with lots of Coke (the drink) and a packet sniffer trace. I could have missed something else. Regardless, ensure that the devices have the latest firmware and see if that helps.
__________________
Always read stuff that will make you look good if you die in the middle of it.
169.254.73.135 is not a normal IP. That IP is used (I THINK for DHCP to obtain the correct IP) what you want is probably 192.168.0.2 or something along those lines. You dont have a DNS either which is why most URLs wont work either.
Check your WEP key again as im pretty sure different wep keys means you wont get the IP.
Even if you assign your GW manually you won`t get anywhere. The problem is your PPC don`t gets an IP Adress from your DHCP Server.
Quote:
IP: 169.254.73.135
This IP isn`t an IP Adress you got from the DHCP Server. Its the IP your PPC auto-assigns if your network didn`t provides one.
The Subnet Mask is the same thing. I don`t think you use 255.255.0.0 as your subnet at the office, do you!?
Same thing with DHCP Server. 255.255.255.255 isn`t a valid IP you could use for your DHCP Server. Its just a broadcast adress which is inserted by windows cause it can`t find a DHCP.
You got the same problem as i did. And, shame on me, i didn`t found a way to solve this. I used another Access Point and it worked. But i don`t know why that happend. I have to reverse engeneer that a more the next days/weeks if i find the time to do that.
I got an Smoothwall as DHCP Server. Which DHCP Server do you use?
just turn the wep off. hihihihi :) thats what i did
__________________
"The ideals which have lighted my way, and time after time have given
me new courage to face life cheerfully, have been kindness, beauty, and
truth." - A. Einstein
169.254.73.135 is not a normal IP. That IP is used (I THINK for DHCP to obtain the correct IP) what you want is probably 192.168.0.2 or something along those lines. You dont have a DNS either which is why most URLs wont work either.
Check your WEP key again as im pretty sure different wep keys means you wont get the IP.
What happens is that if a DHCP configured devices cannot obtain an IP address from a DHCP server it picks an address from the 169.254.x.x range. The idea is that if you have two computers connection, both configured for DHCP but with no DHCP server, they can still talk to each other by choosing 169.254.x.x address. With >65,000 addresses to choose from the changes of having them overlap is pretty slim :)
__________________
Always read stuff that will make you look good if you die in the middle of it.
Armagedon> I've seen that problem with the Netgear routers before. It seems that some of them send DHCP packets that don't (IMO) fully confirm to the RFCs. WM2003 seems more sensitive than other OSs to this issue. So your XP machine will be fine, WM2003 will not. I should point out that just because I say that it does "not appear" do not assume that I'm 100% right. It was a conclusion I came too late one night with lots of Coke (the drink) and a packet sniffer trace. I could have missed something else. Regardless, ensure that the devices have the latest firmware and see if that helps.
My XP Notebook didn`t got an IP Adress too. But if i tried to set this IP to a static IP it worked. On the PPC i tried the same... no way. Even if i assigned a static ip.
I am at the office atm and i am working on this issue cause i want to find out why this happens. And since i don`t have anytthing else to do i try to work that out.
If i have any new information i`ll let you know :hide:
Ok....we're getting somewhere now. I've learned that the access points at work don't serve DHCP so I need to use a static. I've done this and have populated the correct subnet and gateway. Now when I try to ping an IP on the network, it gets further than before, but still fails. I still cannot ping my axim from the network. Here's a rundown of what happens.
1. If i remove all wireless settings and turn on wifi, I get a prompt asking if the network found connects me to the internet or work. I select work. Then it prompts me for a WEP key. I put in the key and nothing happens. If I look at my networks, I see an available with no SSID. If I tell it to connect, It just says connecting until I disable the wifi.
2. I manually add a wireless setting with the correct SSID. I select work, then tell it that it's an AD-HOC connection. On the network key tab, I enter the OPEN, WEP, and the wep key with key index 1. I then unckeck the box on the 802.1x tab. After turning wifi off then back on, it automatically connects to the newly created network with perfect signal. In the network troubleshooting, I see the correct static IP, GW, and Subnet and DNS/WINS but still can't ping anything by IP or name.
I'm closer but still no dice. Thank you for all of the replies.
It shouldn't be an Ad-Hoc setup if you have access points. Ad-Hoc would be Axim to Axim. Infrastr5ucture is what connects you to the access points.
What are your firewall settings on the desktop side? I found Zone Alarm was blocking all of my ports. I had to loosen up the firewall to get the ports to open to the Axim.
I tried it without the ad-hoc connection setting and nothing changed. I do see why you shouldn't use it now though. I brought a laptop with Windows XP down here, and got on with no problems. I got served with a DHCP address and could do anything on the network. If I plug the same settngs into my X30, I don't get an IP. If I use a static, I can't ping anything.
Is there something to the 802.1x setting? Should I be using this? If I check the box, and click properties on both smart card and PEAP, I get an error that says "Cannot log into wireless network. This network requires a personal certificate to positively identify you." Is this a canned message, or is it actually spelling out my probelm?
No offense, but it's not the kind of thing that you should expect to find an answer to by guess work. The best thing is to confirm with your IT staff exactly what the security settings are. Otherwise if you try them all you'll be there forever :)
Also maybe you can clarify about getting farther with the ping.
Quote:
Now when I try to ping an IP on the network, it gets further than before, but still fails.
__________________
Always read stuff that will make you look good if you die in the middle of it.
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
Wifi Connected, get IP, but can't ping anything
