Connecting to internet/new installed software

Question

I have been trouble free with a mac mini using airport express (from a dsl connection) ..
24 hours ago I did a software update for the mac, it was a security topic.. using the preinstalled software update dialogue box.
Since the download, I the computer can not see/search/find the connection to the network.
I switched off the dsl router, and retried after 10 minutes, still nothing.
I have a PC (same house) using the same wireless, and it is fine. (no issues connecting)
Any help? Interesting, prior if I did an update similar to this, a dialogue box usually appeared asking to change my keychain, but this time it has not, perhaps related?

Answer 1

I just picked up a new Core Duo which was maxed out with 2GB RAM. I’m in the process of testing everything else, but I can say with absolute certainty that my network signal is much lower than it ever was using any other computer in my home (and plenty have come and gone).
In the menu, it hovers between one to three ‘bars’.
Fortunately, network access seems to have been consistent so far.
Here is the ping result:
64 bytes from 10.0.1.1: icmp_seq=0 ttl=64 time=3.469 ms
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=1.154 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=1.746 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=2.182 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=1.148 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=1.253 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=2.188 ms
64 bytes from 10.0.1.1: icmp_seq=7 ttl=64 time=1.146 ms
64 bytes from 10.0.1.1: icmp_seq=8 ttl=64 time=1.130 ms
64 bytes from 10.0.1.1: icmp_seq=9 ttl=64 time=1.406 ms
64 bytes from 10.0.1.1: icmp_seq=10 ttl=64 time=2.346 ms
64 bytes from 10.0.1.1: icmp_seq=11 ttl=64 time=1.894 ms
64 bytes from 10.0.1.1: icmp_seq=12 ttl=64 time=2.519 ms
64 bytes from 10.0.1.1: icmp_seq=13 ttl=64 time=1.917 ms
64 bytes from 10.0.1.1: icmp_seq=14 ttl=64 time=3.346 ms
64 bytes from 10.0.1.1: icmp_seq=15 ttl=64 time=2.759 ms
64 bytes from 10.0.1.1: icmp_seq=16 ttl=64 time=3.940 ms
64 bytes from 10.0.1.1: icmp_seq=17 ttl=64 time=3.537 ms
64 bytes from 10.0.1.1: icmp_seq=18 ttl=64 time=1.079 ms
64 bytes from 10.0.1.1: icmp_seq=19 ttl=64 time=173.775 ms
64 bytes from 10.0.1.1: icmp_seq=20 ttl=64 time=2.272 ms
64 bytes from 10.0.1.1: icmp_seq=21 ttl=64 time=122.410 ms
64 bytes from 10.0.1.1: icmp_seq=22 ttl=64 time=1.144 ms
64 bytes from 10.0.1.1: icmp_seq=23 ttl=64 time=166.676 ms
64 bytes from 10.0.1.1: icmp_seq=24 ttl=64 time=2.193 ms
64 bytes from 10.0.1.1: icmp_seq=25 ttl=64 time=113.743 ms
64 bytes from 10.0.1.1: icmp_seq=26 ttl=64 time=3.540 ms
64 bytes from 10.0.1.1: icmp_seq=27 ttl=64 time=162.004 ms
64 bytes from 10.0.1.1: icmp_seq=28 ttl=64 time=1.243 ms
64 bytes from 10.0.1.1: icmp_seq=29 ttl=64 time=1.347 ms
As you can see, toward the end there is some delay in various pings. It isn’t as bad as some samples posted in this thread. A previous ping showed a few more bad results. Firefox (using beta Universal Binary) actually seems to run faster than Safari (believe it or not). Camino runs with blinding speed.
I switched to ‘g’ compatibility only, and tried to disable Bluetooth. Neither ‘solution’ fixed the network strength. It seems reasonable in my eyes that, at this point, it is either a hardware limitation of the Mac Mini, a driver issue, or a combination of both. With such regular issues, I’d be pretty surprised if half are working and half are not. There may be compatibility variance with different routers (I’m using a Linksys).
Back to testing everything else.
Just thought I’d share this tidbit.