Networking Mac/AE and WinXP/Linksys WMP54G with Airport Extreme base.

[execom_rt]

Here my configuration

- PB17", OS 10.2.6, with Airport Extreme (with latest update)
- A PC, WinXP SP1, with Linkys WMP54G (with latest drivers).
- An Airport Extreme base (Firmware 5.0.4)

Both of the computers find the Airport extreme base but no one want to communicate to each other.

Before I used an ethernet cable and worked fine, I decided to move to airport extreme but now no one want to communicate (even ping doesn't work).

- Tried 'Connect to server' SMB found nothing.
- My PB has a DHCP assigned address set to 10.0.1.2 but the PC (winxp sp1) got 169.xxx.xxx.xxx
- trying to ping to 10.0.1.2 and even trying to ping to the airport base station 10.0.1.1 returns 'timeout' message.
- tryied to enable 'Windows can log in' in account + 'Windows File Sharing'. The Mac suggest an address \\10.0.1.2\myname but using this address under WinXP returns an error that the address is invalid.
- Tried to force the IP address, but didn't do anything.
- I've setup a WEP 40bit because WinXP doesn't seems to support 128bit WEP (Want a 104bit WEP ?).

I've got a printer attached on the airport base extreme, but how do I specify it under WinXP ?

If someone got this configuration or has the same experience !

Searched for tutorial but found nothing that match my case.

Look like the computer can communicate to the Airport Base but does nothing more.

Last thing, after few minutes, the network on WinXP seems to be deconnected (asking to connect again).

[yellow]

you wrote:
the PC (winxp sp1) got 169.xxx.xxx.xxx

Can the PC get out to the world? When I see the address 169.x.x.x, it means that no IP address has been assigned, therefore has no networking capabilities, therefore wouldn't be able to be seen by the Mac.

[hschickel]

When you type the WEP password into the PC you most likely have to use the hex code to do it.

Open the airport admin utility and open the configuration for your airport. On the first configuration page you'll see:

Wireless WEP Key:

followed by a bunch of letters and numbers. This is the hex key. Generally, to input this into a non airport air card you type:

0x[and then the key exactly as written]

the 0x tells the card that the next value is the hex key. Exclude the brackets - they are for illustration.

Hugh

EDIT - note that the 0 in 0x is the number zero.

[execom_rt]

Yes, i've that code, I will try it, but still doesn't understand why the DHCP provide a '169.xxx' address on my PC.

This is provided by the Airport base no ? Else how to tell to WinXP to use the DHCP from the Airport for providing the IP address ?

Is there a tool for admin. the Airport extreme base from Windows ?

I've tried also to force an IP (10.0.1.3) on the PC, but after that, It said that the IP address is invalid (reset to 0.0.0.0).

The WEP key (text password) seems to be accepted by the Windows (I get connection, but after a while, it lost it, telling that new network has been found).

Is anyone had this such of config ?

Also I forced to '801.11 g only' but didn't change anything.

Again it used to work with an ethernet card.

[hschickel]

You won't get a DHCP address from the AEBS until you log into the network with a valid password. Thus the hex key.

Try turning off WEP and see if you can connect that way. If you can you just have to figure out how the PC needs to get the passkey. if you can't connect you have another issue that needs to be worked out.

Hugh

[hschickel]

Another thought...

The WEP key (text password) seems to be accepted by the Windows (I get connection, but after a while, it lost it, telling that new network has been found).

Set the SSID on the pc to your SSID. If you use "ANY" you'll get the one with the strongest signal. There may be another WAP near you that is broadcasting louder.

Also - there is a java configuration tool for the older base stations. I'm not sure if it works with AEBS. Try googling for it.

Hugh

[execom_rt]

Ok, I removed the WEP option.

First, Windows got a 'valid' IP address (10.0.1.2) ! So good sign.

And pinging to the airport base (10.1.1) did work.

Then I re-ordered in MacOS the network settings in order to have airport first (was the modem USB ADSL)
I think this was the main reason of the problem.

Then activate the file sharing.
SMB found my PC, and the PC found the Mac and was able to browse file from each other (coool)

But I lost the internet connection, so I've re-ordered in order to get the ADSL usb back to the first place.

Local networking still worked, but I'm afraid that If i reboot the machines, I will have to put Airport back to the top of the list in order to do some local networking.

Hopefully, I will get that DLink Ethernet ADSL modem found at Apple Store, connect it directly to the airport base :)

Still the problem of the WEP encryption to setup correctly. Maybe I needed to write the hexa key instead.

I will try that later.

But indeed don't try the WEP encryption before it works without it. This is also an important point !