Airport Problems : All Intel Models Affected.

[tivoboy]

in this case

Hmmm

Machine at home that was plpaying up has the same settings as the one that works ( 0x168C, 0x86 version.. )

Only difference is this one uses channel 11 and has a BT keyboard and mouse ( and a fresh install of OSX from the supplied disks )

Will remove the BT and change channels..

Pete

in this case, turning off the BT has been known to help reduce interferance. As well, turning off IPSEC6 and also turning off, AUTOMATICALLY CONNECT TO NETWORKS.

 

[coot]

in this case, turning off the BT has been known to help reduce interferance. As well, turning off IPSEC6 and also turning off, AUTOMATICALLY CONNECT TO NETWORKS.

Ideally BT needs to be on, that mini is used as a media centre downstairs.
Just about to test the new mini on the home network.

Thanks,

Pete.

 

[Bunsen Burner]

Sigh...

Here are some pings:

To my router:

Ping has started ...

PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=1.712 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.056 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.369 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.053 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.204 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=1.090 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=1.046 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=1.055 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=1.016 ms
64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=1.028 ms

--- 192.168.2.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.016/1.163/1.712/0.210 ms

To Google:

Ping has started ...

PING google.com (64.233.187.99): 56 data bytes
64 bytes from 64.233.187.99: icmp_seq=0 ttl=243 time=24.678 ms
64 bytes from 64.233.187.99: icmp_seq=1 ttl=243 time=24.240 ms
64 bytes from 64.233.187.99: icmp_seq=2 ttl=243 time=26.358 ms
64 bytes from 64.233.187.99: icmp_seq=3 ttl=243 time=24.506 ms
64 bytes from 64.233.187.99: icmp_seq=4 ttl=243 time=24.028 ms
64 bytes from 64.233.187.99: icmp_seq=5 ttl=243 time=25.485 ms
64 bytes from 64.233.187.99: icmp_seq=6 ttl=243 time=24.903 ms
64 bytes from 64.233.187.99: icmp_seq=7 ttl=243 time=23.766 ms
64 bytes from 64.233.187.99: icmp_seq=8 ttl=243 time=29.307 ms
64 bytes from 64.233.187.99: icmp_seq=9 ttl=243 time=24.063 ms

--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 23.766/25.133/29.307/1.573 ms

To Vonage:

Ping has started ...

PING vonage.com (216.115.22.200): 56 data bytes
64 bytes from 216.115.22.200: icmp_seq=0 ttl=115 time=35.923 ms
64 bytes from 216.115.22.200: icmp_seq=1 ttl=115 time=38.584 ms
64 bytes from 216.115.22.200: icmp_seq=2 ttl=115 time=38.111 ms
64 bytes from 216.115.22.200: icmp_seq=3 ttl=115 time=36.960 ms
64 bytes from 216.115.22.200: icmp_seq=4 ttl=115 time=37.051 ms
64 bytes from 216.115.22.200: icmp_seq=5 ttl=115 time=36.448 ms
64 bytes from 216.115.22.200: icmp_seq=6 ttl=115 time=35.437 ms
64 bytes from 216.115.22.200: icmp_seq=7 ttl=115 time=37.551 ms
64 bytes from 216.115.22.200: icmp_seq=8 ttl=115 time=36.650 ms
64 bytes from 216.115.22.200: icmp_seq=9 ttl=115 time=35.857 ms

--- vonage.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 35.437/36.857/38.584/0.958 ms


To BBC (bbc.uk.com):

Ping has started ...

PING bbc.uk.com (212.58.228.154): 56 data bytes
64 bytes from 212.58.228.154: icmp_seq=0 ttl=241 time=102.090 ms
64 bytes from 212.58.228.154: icmp_seq=1 ttl=241 time=104.738 ms
64 bytes from 212.58.228.154: icmp_seq=2 ttl=241 time=104.263 ms
64 bytes from 212.58.228.154: icmp_seq=3 ttl=241 time=104.432 ms
64 bytes from 212.58.228.154: icmp_seq=4 ttl=241 time=104.685 ms
64 bytes from 212.58.228.154: icmp_seq=5 ttl=241 time=103.643 ms
64 bytes from 212.58.228.154: icmp_seq=6 ttl=241 time=103.161 ms
64 bytes from 212.58.228.154: icmp_seq=7 ttl=241 time=103.814 ms
64 bytes from 212.58.228.154: icmp_seq=8 ttl=241 time=102.127 ms
64 bytes from 212.58.228.154: icmp_seq=9 ttl=241 time=104.820 ms

--- bbc.uk.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 102.090/103.777/104.820/0.973 ms

As I said, no problems whatsoever with the wireless in this laptop, no "issues revealed".

BB

 

[tivoboy]

of course

Ideally BT needs to be on, that mini is used as a media centre downstairs.
Just about to test the new mini on the home network.

Thanks,

Pete.

certainly, we want ALL the functionality to work. hopefully, apple will solve this in a future update.

As for the BT on the min, being a MC downstairs, what are you using the BT connection for that is so important.?

 

[NeuronBasher]

Keep posting in folks. Apple support it watching this newsgroup THREAD and the more info we can provide, the sooner identification of the problem and solution to those with it can be resolved.....

My MBP:

Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: USA
Wireless Card Firmware Version: 0.1.12
Current Wireless Network: BLACKBIRD
Wireless Channel: 6

Working flawlessly, excellent throughput.

 

[MRU]

Ran similar test as Bunsun Burner. You can clearly see the fluctuation and the poor performace I'm suffering...

------------


Ping my Apple Base Station

Ping has started ...

PING 10.0.1.1 (10.0.1.1): 56 data bytes
64 bytes from 10.0.1.1: icmp_seq=0 ttl=64 time=0.820 ms
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.826 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=92.869 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=44.737 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=1.722 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=266.741 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=219.035 ms
64 bytes from 10.0.1.1: icmp_seq=7 ttl=64 time=172.265 ms
64 bytes from 10.0.1.1: icmp_seq=8 ttl=64 time=123.960 ms
64 bytes from 10.0.1.1: icmp_seq=9 ttl=64 time=76.701 ms

--- 10.0.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.820/99.968/266.741/89.859 ms

-------
Ping http://www.google.com

Ping has started ...

PING http://www.l.google.com (66.102.9.104): 56 data bytes
64 bytes from 66.102.9.104: icmp_seq=0 ttl=243 time=55.189 ms
64 bytes from 66.102.9.104: icmp_seq=1 ttl=244 time=77.023 ms
64 bytes from 66.102.9.104: icmp_seq=2 ttl=243 time=395.813 ms
64 bytes from 66.102.9.104: icmp_seq=3 ttl=244 time=72.353 ms
64 bytes from 66.102.9.104: icmp_seq=4 ttl=243 time=299.285 ms
64 bytes from 66.102.9.104: icmp_seq=5 ttl=243 time=568.328 ms
64 bytes from 66.102.9.104: icmp_seq=6 ttl=244 time=519.955 ms
64 bytes from 66.102.9.104: icmp_seq=8 ttl=243 time=424.620 ms
64 bytes from 66.102.9.104: icmp_seq=9 ttl=243 time=55.004 ms

--- http://www.l.google.com ping statistics ---
10 packets transmitted, 9 packets received, 10% packet loss
round-trip min/avg/max/stddev = 55.004/274.174/568.328/200.163 ms


-----------
Ping BBC.co.uk

Ping has started ...

PING http://www.bbc.net.uk (212.58.224.89): 56 data bytes
64 bytes from 212.58.224.89: icmp_seq=0 ttl=250 time=37.163 ms
64 bytes from 212.58.224.89: icmp_seq=1 ttl=250 time=297.821 ms
64 bytes from 212.58.224.89: icmp_seq=2 ttl=250 time=30.097 ms
64 bytes from 212.58.224.89: icmp_seq=3 ttl=250 time=29.366 ms
64 bytes from 212.58.224.89: icmp_seq=4 ttl=250 time=71.278 ms
64 bytes from 212.58.224.89: icmp_seq=5 ttl=250 time=273.884 ms
64 bytes from 212.58.224.89: icmp_seq=6 ttl=250 time=225.885 ms
64 bytes from 212.58.224.89: icmp_seq=7 ttl=250 time=177.883 ms
64 bytes from 212.58.224.89: icmp_seq=8 ttl=250 time=129.143 ms
64 bytes from 212.58.224.89: icmp_seq=9 ttl=250 time=81.925 ms

--- http://www.bbc.net.uk ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 29.366/135.445/297.821/97.233 ms


---------------------
Ping Apple.com

Ping has started ...

PING http://www.apple.com.akadns.net (17.112.152.32): 56 data bytes
64 bytes from 17.112.152.32: icmp_seq=0 ttl=245 time=316.533 ms
64 bytes from 17.112.152.32: icmp_seq=1 ttl=245 time=585.896 ms
64 bytes from 17.112.152.32: icmp_seq=3 ttl=245 time=175.254 ms
64 bytes from 17.112.152.32: icmp_seq=4 ttl=245 time=173.103 ms
64 bytes from 17.112.152.32: icmp_seq=5 ttl=245 time=509.693 ms
64 bytes from 17.112.152.32: icmp_seq=6 ttl=245 time=461.767 ms
64 bytes from 17.112.152.32: icmp_seq=7 ttl=245 time=413.812 ms
64 bytes from 17.112.152.32: icmp_seq=8 ttl=245 time=365.460 ms
64 bytes from 17.112.152.32: icmp_seq=9 ttl=245 time=316.939 ms

--- http://www.apple.com.akadns.net ping statistics ---
10 packets transmitted, 9 packets received, 10% packet loss
round-trip min/avg/max/stddev = 173.103/368.717/585.896/132.849 ms


-------------
Ping macrumors.com

Ping has started ...

PING macrumors.com (64.62.137.66): 56 data bytes
64 bytes from 64.62.137.66: icmp_seq=0 ttl=52 time=316.630 ms
64 bytes from 64.62.137.66: icmp_seq=1 ttl=52 time=585.630 ms
64 bytes from 64.62.137.66: icmp_seq=2 ttl=52 time=537.443 ms
64 bytes from 64.62.137.66: icmp_seq=3 ttl=52 time=489.755 ms
64 bytes from 64.62.137.66: icmp_seq=4 ttl=52 time=441.173 ms
64 bytes from 64.62.137.66: icmp_seq=5 ttl=52 time=393.901 ms
64 bytes from 64.62.137.66: icmp_seq=6 ttl=52 time=208.310 ms
64 bytes from 64.62.137.66: icmp_seq=7 ttl=52 time=179.155 ms
64 bytes from 64.62.137.66: icmp_seq=8 ttl=52 time=177.621 ms
64 bytes from 64.62.137.66: icmp_seq=9 ttl=52 time=372.727 ms

--- macrumors.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 177.621/370.235/585.630/140.336 ms

--------


Compare those results to my iBook G4 and the problem is apparent...


Router

Ping has started ...

PING 10.0.1.1 (10.0.1.1): 56 data bytes
64 bytes from 10.0.1.1: icmp_seq=0 ttl=64 time=1.044 ms
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=1.088 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=2.010 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=1.026 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=1.028 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=0.950 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=1.017 ms
64 bytes from 10.0.1.1: icmp_seq=7 ttl=64 time=1.015 ms
64 bytes from 10.0.1.1: icmp_seq=8 ttl=64 time=1.006 ms
64 bytes from 10.0.1.1: icmp_seq=9 ttl=64 time=0.999 ms

--- 10.0.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.950/1.118/2.010/0.299 ms


-----


http://www.bbc.co.uk

Ping has started ...

PING http://www.bbc.net.uk (212.58.224.121): 56 data bytes
64 bytes from 212.58.224.121: icmp_seq=0 ttl=248 time=33.146 ms
64 bytes from 212.58.224.121: icmp_seq=1 ttl=248 time=32.132 ms
64 bytes from 212.58.224.121: icmp_seq=2 ttl=248 time=35.319 ms
64 bytes from 212.58.224.121: icmp_seq=3 ttl=248 time=33.498 ms
64 bytes from 212.58.224.121: icmp_seq=4 ttl=248 time=31.241 ms
64 bytes from 212.58.224.121: icmp_seq=5 ttl=248 time=33.311 ms
64 bytes from 212.58.224.121: icmp_seq=6 ttl=248 time=31.080 ms
64 bytes from 212.58.224.121: icmp_seq=7 ttl=248 time=32.059 ms
64 bytes from 212.58.224.121: icmp_seq=8 ttl=248 time=30.585 ms
64 bytes from 212.58.224.121: icmp_seq=9 ttl=248 time=29.258 ms

--- http://www.bbc.net.uk ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 29.258/32.163/35.319/1.643 ms

-------


http://www.google.com

Ping has started ...

PING http://www.l.google.com (66.102.9.147): 56 data bytes
64 bytes from 66.102.9.147: icmp_seq=0 ttl=243 time=63.716 ms
64 bytes from 66.102.9.147: icmp_seq=1 ttl=243 time=52.197 ms
64 bytes from 66.102.9.147: icmp_seq=2 ttl=244 time=43.861 ms
64 bytes from 66.102.9.147: icmp_seq=3 ttl=243 time=52.639 ms
64 bytes from 66.102.9.147: icmp_seq=4 ttl=244 time=42.870 ms
64 bytes from 66.102.9.147: icmp_seq=5 ttl=243 time=64.058 ms
64 bytes from 66.102.9.147: icmp_seq=6 ttl=243 time=61.280 ms
64 bytes from 66.102.9.147: icmp_seq=7 ttl=243 time=65.412 ms
64 bytes from 66.102.9.147: icmp_seq=8 ttl=243 time=85.754 ms
64 bytes from 66.102.9.147: icmp_seq=9 ttl=243 time=61.837 ms

--- http://www.l.google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 42.870/59.362/85.754/11.802 ms


-----

http://www.apple.com

Ping has started ...

PING http://www.apple.com.akadns.net (17.112.152.32): 56 data bytes
64 bytes from 17.112.152.32: icmp_seq=0 ttl=245 time=180.734 ms
64 bytes from 17.112.152.32: icmp_seq=1 ttl=245 time=177.892 ms
64 bytes from 17.112.152.32: icmp_seq=2 ttl=245 time=174.279 ms
64 bytes from 17.112.152.32: icmp_seq=3 ttl=245 time=175.264 ms
64 bytes from 17.112.152.32: icmp_seq=4 ttl=245 time=179.024 ms
64 bytes from 17.112.152.32: icmp_seq=5 ttl=245 time=175.174 ms
64 bytes from 17.112.152.32: icmp_seq=6 ttl=245 time=174.870 ms
64 bytes from 17.112.152.32: icmp_seq=7 ttl=245 time=179.000 ms
64 bytes from 17.112.152.32: icmp_seq=8 ttl=245 time=176.152 ms
64 bytes from 17.112.152.32: icmp_seq=9 ttl=245 time=174.859 ms

--- http://www.apple.com.akadns.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 174.279/176.725/180.734/2.137 ms

 

[XIII]

AirPort Card Information:

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 101.3 (3.120.28.3)
Current Wireless Network: linksys
Wireless Channel: 11

I have the issues.

 

[lonepilgrim]

Ran similar test as Bunsun Burner. You can clearly see the fluctuation and the poor performace I'm suffering...

Could you tell me how to ping and I'll try it to see what happens as I appear to have the 'problematic' firmware version.

There's about a 300kbps difference in download speed between ethernet and wireless connection to my router (wireless: c. 5800kbps, ethernet: c.6100kbps).

And this is my info:

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 101.3 (3.120.28.3)
Current Wireless Network: BeBox
Wireless Channel: 1

 

[MRU]

Could you tell me how to ping and I'll try it to see what happens as I appear to have the 'problematic' firmware version.

There's about a 300kbps difference in download speed between ethernet and wireless connection to my router (wireless: c. 5800kbps, ethernet: c.6100kbps).

And this is my info:

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 101.3 (3.120.28.3)
Current Wireless Network: BeBox
Wireless Channel: 1

I see, so XIII & LonePilgrim all have same info and software as me, and all share the problem.....


To ping your machine, go into Utilities in the application folder. In there is a utility called 'NETWORK UTILITY'
open that and in one of the tabs you will see 'PING'... select that tab and in the box put in the ip address of your router. mine was 10.0.1.1 and then press the big blue PING button To ping websites, simply put in the web address.

 

[coot]

Hi all,

Putting my new machine on the home network ( ch 11, WPA ) i got a poor signal and download speed on speakeasy.net ( 200-300 on the download )

Changing the network to channel 6, WEP security got me a good signal and 900 on the download test.

Still doing some tests but would be happy if that stayed constant.

Now changing the old machine to get on this network.

Pete.

 

[XIII]

I see, so XIII & LonePilgrim all have same info and software as me, and all share the problem.....

B*llocks.

Lets get a software update soon.. And hope its not hardware.

 

[lonepilgrim]

This is the result of pinging my router wirelessly:

Ping has started ...

PING bebox.config (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=1.180 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.886 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.911 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.890 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=0.900 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=0.869 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=0.881 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=0.980 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=0.989 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=0.949 ms

--- bebox.config ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.869/0.944/1.180/0.088 ms


This is pinging over ethernet:

Ping has started ...

PING bebox.config (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=0.922 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.601 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.948 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.688 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=0.659 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=0.673 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=0.662 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=0.636 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=0.639 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=0.641 ms

--- bebox.config ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.601/0.707/0.948/0.116 ms


So there's a little difference. Is this the iMac at fault, though, or the fault of an speed difference inherent to the router?


Speakeasy speed test: (to NY server)

Ethernet:
Download Speed: 6081 kbps (760.1 KB/sec transfer rate)
Upload Speed: 863 kbps (107.9 KB/sec transfer rate)

Wireless:
Download Speed: 5703 kbps (712.9 KB/sec transfer rate)
Upload Speed: 879 kbps (109.9 KB/sec transfer rate)

 

[Peace]

This problem seems to be pretty weird..

I havent experienced it..

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 102.1 (3.120.28.3)
Current Wireless Network: *******
Wireless Channel: 9

17" iMac core duo..

 

[thestaton]

I gave up on using wireless on my 20" Duo. It was so flakey - speeds where awful - and when you wake the computer up for sleep you had to go back and reconnect to your network. Hopefully we can get a fix asap!

Not to mention it has been confirmed that it will not work with Verizons popular wireless dsl modem / router westell 327.

 

[lonepilgrim]

This problem seems to be pretty weird..

I havent experienced it..

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 102.1 (3.120.28.3)
Current Wireless Network: *******
Wireless Channel: 9

17" iMac core duo..

What's the significance of the 'wireless channel'?

The only real issue I'm experiencing with Airport is that it doesn't reconnect on waking from sleep.

 

[coot]

Small update...

The 2nd machine was running fine downstairs, on a monitor next to the TV ( where the 1st mini lives )
I played around with few positions, under the tv, at the side, and the signal was still good.

I then shutdown the 1st mini and used the BT keyboard and mouse from this machine on the new one.

After a couple of reboots ( system froze connecting to the mouse the first time ) I managed to connect back to the network but had varying pings ( 100/200 upto 1400 at one point ) to the router and never acheived a stable connection.

Moving the machine to the office and back with usb keyboard/mouse and its running well, good connection and the same download speeds as the iMac G5 sat next to it.

The 1st mini when tried with USB didnt play too well either, so thats back to the "Belkin Method"

I'll give up for a few days

 

[Peace]

What's the significance of the 'wireless channel'?

The only real issue I'm experiencing with Airport is that it doesn't reconnect on waking from sleep.

The wireless channel is real important if you have a portable 2.4ghz phone and a wireless LAN in your home.Or if your iMac/MacbookPro is connecting through any wireless router.
Airport cards need to be on a different channel than your portable phone to minimize interference.
Or for that matter any other device that uses 2.4ghz ranges..

Make sure your Airport network is using a different channel.

 

[Zaty]

My Card:

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 101.3 (3.120.28.3)

And of course, it's not working! Oh dear, I was so confident it was a software problem but now I'm not sure anymore. On the other hand, so far everyone having the 0x14E4, 0x89 card seems to have problems. So, either the entire batch of the above mentioned version is faulty or Apple just needs to add another driver.

 

[MRU]

Small update...

The 2nd machine was running fine downstairs, on a monitor next to the TV ( where the 1st mini lives )
I played around with few positions, under the tv, at the side, and the signal was still good.

I then shutdown the 1st mini and used the BT keyboard and mouse from this machine on the new one.

After a couple of reboots ( system froze connecting to the mouse the first time ) I managed to connect back to the network but had varying pings ( 100/200 upto 1400 at one point ) to the router and never acheived a stable connection.

Moving the machine to the office and back with usb keyboard/mouse and its running well, good connection and the same download speeds as the iMac G5 sat next to it.

The 1st mini when tried with USB didnt play too well either, so thats back to the "Belkin Method"

I'll give up for a few days

That's the problem. We think were getting somewhere when were not.

 

[Zaty]

This problem seems to be pretty weird..

I havent experienced it..

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 102.1 (3.120.28.3)

Current Wireless Network: *******
Wireless Channel: 9

17" iMac core duo..

Now, that's interesting. Same type but different firmware [102.1 (3.120.28.3) vs. 101.3 (3.120.28.3)] How about a firmware update, Apple?

 

[Peace]

Now, that's interesting. Same type but different firmware [102.1 (3.120.28.3) vs. 101.3 (3.120.28.3)] How about a firmware update, Apple?

Maybe one's on the way

 

[MRU]

What could be good is if someone with a good imac, lets someone with a bad one do a fresh install from their cd's.. That will let us know if its software

 

[XIII]

Maybe one's on the way

Better be.

I have just changed wireless channel to 1, reinstalled router firmware, added TKIP WEP security, all to try and stop my regular drop outs. So far, not working.

 

[Zaty]

What could be good is if someone with a good imac, lets someone with a bad one do a fresh install from their cd's.. That will let us know if its software

Would a fresh install change any firmware on the Mac?

 

[MRU]

Would a fresh install change any firmware on the Mac?

If it's a driver issue, then the OSX re-install disc have all the drivers for the components for that mac.

I'm sure firmware/driver is the same thing on the airport (or maybe not )

Come on peep's more firmware version listings please! and don't forget to mentio what machine you are using.
This thread is now getting referenced on the Apple discussions site, added to the fact it's being monitored by Apple Tech's - (I'm currently doing packet test's with an app they sent me to help as well....)