PPC2003 Wi-fi: Not Easy

[tmulli]

Ok, either the wi-fi setup on PPC 2003 is not any easier, I'm stupid or I am just so frustrated that I cannot calmly think thru the situation on how to get my ipaq to connect out to the net from work. What am I missing? Here's the low-down:

Trying to get iPaq 3950 (upgraded to 2003) with Linksys WCF11 connected to wireless network at the office to get out to the net. I have a Linksys WAP11 AP connected to our wired network. I can connect to the AP fine - I popped in my card and the ipaq found the network, I entered my WEP key and it registers at 'connected'. But when I try to go somewhere in PIE, I get 1 of 2 messages: 'Cannot connect with your current settings' or 'The page you are looking for cannot be found'.

My settings in the connection manager are:

'Select Netowrks': Connect to the internet using - My ISP
Connect to private network using - My Work Netowork

'Network Card' - Wirelsss network properties: 'Connects to': Work
WEP is enabled, the key is provided automatically, and the enable network access using PEAP is also checked. 'Also my network card aconnects to': Work

What am I missing, or why am i not able to get out to the internet? Help, please!!

Thanks!!

[Jason Dunn]

You need to change it to THE INTERNET. Microsoft assumes that everyone on the planet is running a proxy server, and thus for most people, the WORK setting doesn't provide Internet access. :roll:

[Dazbot]

Odd, I've got a WLAN card and under network card its set up for "My NIC connects to Work", I've got a Dlink Wireless Router and I don't have a proxy server but it says this network connects to the Internet.

I can access both the local network and Internet at the same time which is very useful.

[tmulli]

I have 'my network card connects to' set to The Internet' I am getting 'page not found' message. Curiously, when I go back in to check, the setting has changed back to 'Work'.

Dazbot, that's how I had myine setup prior to upgrading to 2003, but after I discovered that Linksys does not have 2003 drivers for their card, so had to locate alternative drivers which seem to work. I have tried both settings (the internet and work with connects to internet checked). Not sure what's going on. :cry:

[Dazbot]

I had it set up the same on my 3850 using the a D-link 660W with the newer 2002 driver.

Is it getting an IP and Gateway address? Try ftp://ftp.cam.com/cambridge/win/vxUtil.zip see what says.

[tmulli]

It's getting an IP, but no gateway. The IP is not anywhere close to anything used on our internal network and also the subnet mask is wrong. It is showing 255.255.0.0 and should be 255.255.255.0. Not sure if that is affecting anything. Gateway is set to 0.0.0.0.

[Steven Cedrone]

It's getting an IP, but no gateway. The IP is not anywhere close to anything used on our internal network and also the subnet mask is wrong. It is showing 255.255.0.0 and should be 255.255.255.0. Not sure if that is affecting anything. Gateway is set to 0.0.0.0.

Can you assign a static IP address? Make sure you check with your IT department before assigning an address though...

Steve

[Dazbot]

Without the gateway address you aren't going anywhere near the Internet cause the PPC doesn't know which PC/router to ask to get online. :(

Does the IP start with 169, if it does then its not getting an IP from a DHCP server. In which case try setting it up manually with the IP, Subnet and gateway address.

[tmulli]

Yes it was 169.something.something.something. I set the IP and subnet manually, but not the gateway. I am able to ping my server on my network, but not get out to the net.

My AP has a static IP and subnet, but not gateway assigned. Should it have? And should it be set to the same as our network?

I set the IP and sub on my wi-fi, but not the gateway. Should this be the same as our network?

[Dazbot]

Yes it was 169.something.something.something. I set the IP and subnet manually, but not the gateway. I am able to ping my server on my network, but not get out to the net.

My AP has a static IP and subnet, but not gateway assigned. Should it have? And should it be set to the same as our network?

I set the IP and sub on my wi-fi, but not the gateway. Should this be the same as our network?

It looks like your PPC can't find a DHCP server, 169.x.x.x is an IP automatically assigned by the PPC.

The gateway address should be the PC or Router that's connected to the Internet, on my home network I have a D-Link 614+ which is an AP, ethernet router and DHCP server, its IP is 192.168.0.254.

So each PC that I've statically assigned an IP to has this address as the gateway address.

For the PCs and PPC that are DHCP enabled they get a dynamic IP, the same subnet as the rest of the PCs and the same gateway IP of 192.168.0.254.

Hope this helps

[tmulli]

Ok, I set the gateway on my card to the IP of our DHCP server on our network. Still can't get out. :cry:

[shawnc]

You guys are hilarious. This thread would be no less understandable to me if it were in greek! :wink:

[Dazbot]

Ok, I set the gateway on my card to the IP of our DHCP server on our network. Still can't get out. :cry:
Can you access the local network?

Is the DHCP server also the gateway to the Internet?

[Falstaff]

I have a Toshiba e755 with built in Wi-Fi, but I can't assign the gateway (at least I don't know how). It sees my home's connection, and I have it set to Internet, but it won't connect to the internet. I have had success a few times before, quite randomly, but then it always stops working. I have a Linksys router, it gets an internet connection from a linksys hub which the DSL modem connects to. There are no security features enabled. I know the gateway, subnet mask, and all, but I can't set them. Anyone know how? Thanks

[Dazbot]

I have a Toshiba e755 with built in Wi-Fi, but I can't assign the gateway (at least I don't know how). It sees my home's connection, and I have it set to Internet, but it won't connect to the internet. I have had success a few times before, quite randomly, but then it always stops working. I have a Linksys router, it gets an internet connection from a linksys hub which the DSL modem connects to. There are no security features enabled. I know the gateway, subnet mask, and all, but I can't set them. Anyone know how? Thanks

Have you set the router up for DHCP, if not have you tried using the Linksys IP as the gateway address?

[tmulli]

well, was able to get back on wi -fi at home no problem, but still having problems at work. Must be something to do with our firewall. It will have to wait until I get more time to deal with it.

[Falstaff]

I don't know how to manually set the gateway in PPC. Can you please tell me? I'll check the DHCP.

[tmulli]

to change the gateway, go to copnnections, then click on the name of the card, you can enter it there.

[tregnier]

I think this discussion fully rationalizes many of the points made in Forum>Just Chattin'>Pocket PC's Do Not Make the Grade.

[theon]

This discussion just fuels my belief that Bluetooth is not dead... Sorry couldn't resist. :mrgreen:

My first WiFi post, which is good cause it has taken close to 6 weeks and over 20 posts on differnt forums to get it going.

Back to the topic, I found this site to be the most useful in terms of getting PIE up and running. Hope it helps you like it did me! It's a step by step to how to set-up Internet Connection Sharing, including SCREENSHOTS! It rocks.

http://www.pc-counselor.com/ad-hoc.htm

Here are some of the posts that I had on this site. You could pull some information from here that you might find useful if anything else crops up. I'm betting it does... 0X

http://www.pocketpcthoughts.com/forums/viewtopic.php?t=18580

http://www.pocketpcthoughts.com/forums/viewtopic.php?p=176148&highlight=&sid=9378abd2b94a62a3663648d3e3dfe5d2#176148

http://www.pocketpcthoughts.com/forums/viewtopic.php?p=176092&highlight=&sid=9378abd2b94a62a3663648d3e3dfe5d2#176092

There are a couple more that you can find by searching the forum for "wifi activesync". Good luck!

[CTSLICK]

oh sure Theon now you post this :D BTW this is my 3rd wifi post. I just got mine working last night after 2 very frustrating evenings

I had to bludgeon my setup into submission to get it to work. In the end it was some info on using the Prism driver plus some info on aximsite.com on setting up a static IP that did it.

Honestly this was every bit as hard as trying to set up my bluetooth adapter. Maybe harder.

[theon]

Only 2 nights CTSLICK? You're lucky, mine was more like in the region of weeks cause I had no idea what anyone was talking about.

It frustrated me so much that once I got it working I came back to all the forums I could remember and posted the site that got me running... :)

Better late than never though! 0X

[Jereboam]

I think this discussion fully rationalizes many of the points made in Forum>Just Chattin'>Pocket PC's Do Not Make the Grade.

See? See? I'm not crazy!! :D

Only joking, but this is a long way from zero-config, and to be honest apart from the bubble notifications I'm pretty sure it was much easier to set up my wifi network with the PPC2k2 than with WM2k3 - I seemed to have much more control more easily, if that makes sense.

And does anyone else think that a hardware switch for wifi/bluetooth is desperately needed? Click, you're on, click, you're off.

My own wifi experience was just as bad, anyway. For a long time, it simply did not work while HP got various firmware and driver updates out of their system. Not that it works, albeit it's all a little flaky, it's great. AS is no problem...funnily enough once the wifi was working that's one thing which has always been a piece of cake and totally hitch-free...beats me.

J'bm[/b]

[CCollins]

If you are getting a 169.254.x.x address, then it is correct that you are not talking correctly to the DHCP server and are instead using Automatic Private IP Addressing.

However, setting up the IP address statically won't help unless the problem is with the DHCP server itself, which is almost never the case.

More likely, there is a reason you are not able to talk on the network and thus not talk to the DHCP server.

Two common causes of getting a link connection but not communicating on the network are if the network is using WEP and you don't have the correct key, or if the network is using MAC filtering, and your NIC hasn't been added to the "allow" list. The latter is most likely your problem.

Hope this helps.