Nearly there, but not quite…

I did write:

Very easy to configure, I plugged it into the power then plugged the supplied ethernet cable into my iMac, reconfigured the ethernet settings in System Preferences, turned off the Airport on the iMac. Then went to a browser, typed in the 1.1.1.1 address, entered the username and password. Added my Airport network details. Very pleased to see that my 802.11n 5GHz network was recognised, remembered to use WPA2-AES (as that is what the Airport Extreme uses). Click configure,update. Job done!

However life is never that simple…

Once I placed the Buffalo Nfiniti Wireless-N Dual Band Ethernet Converter under my TV, it didn’t seem to work. I in the main purchased the Buffalo device so that I could connect my new LG BD370 Blu-ray Player to the internet. The LG Blu-Ray Player can also play YouTube videos, but has to be connected to the internet to do so.

The LG Blu-Ray Player intially could not connect to the network, which indicated to me that the problem was with the Ethernet Converter. In the end I did a full reset and reconfigured. Checking the web based advanced menu, I worked out that it had retained the default 1.1.1.1 IP address.

In that menu I changed the Unit IP Address from Manual Setup to dynamic and to acquire an IP Address automatically.

At this point the LG Blu-Ray Player could now connect to the network and the internet, but still wouldn’t play YouTube videos. Of course now I was connected to the internet I could download updated firmware for the LG Blu-Ray Player. Once downloaded and installed the LG Blu-Ray Player could now play YouTube videos.

Buffalo Nfiniti Wireless-N Dual Band Ethernet Converter, Done!

Well that was simple.

I ordered the Buffalo Nfiniti Wireless-N Dual Band Ethernet Converter from Amazon on the 1st January. I used the Super Saver Delivery option, I was in no hurry and why pay extra for postage (especially over New Year). Really surprised to see the parcel arrive this morning! Excellent service Amazon, well impressed.

It’s smaller than the picture makes it look.

Very easy to configure, I plugged it into the power then plugged the supplied ethernet cable into my iMac, reconfigured the ethernet settings in System Preferences, turned off the Airport on the iMac. Then went to a browser, typed in the 1.1.1.1 address, entered the username and password. Added my Airport network details. Very pleased to see that my 802.11n 5GHz network was recognised, remembered to use WPA2-AES (as that is what the Airport Extreme uses). Click configure,update. Job done!

The reason the Buffalo device appeals, is that it comes with four ethernet ports, which means I can connect four devices to the network.

Now to test it out under the TV!

Now here’s a good reason for securing your wireless network…

I have mentioned wireless security on the blog before and I am talking about real security not “feel good” security; at the very least you should be using WPA and preferably WPA2.

The Register reports on the consequences that have happened to a poor American expatriate living in India who just so happened to run an open unsecured wireless network.

Indian police raided the Mumbai home of an American expatriate after someone used his open wireless network to send an email that took responsibility for a bomb blast that killed at least 42 people.

Kenneth Haywood, whose internet-protocol address was included on an email sent just prior to the blasts, spent much of Thursday answering questions by the Maharashtra Anti-Terrorism Squad officials. Police seized his three computers, as well as the machines of several neighbors, and are examining them as part of an investigation.

This story demonstrates a rare but real risk of running an open wireless network.

Use WPA to protect your wireless network.

This video from the BBC’s Real Hustle gives you an idea why you should be using WPA to protect your wireless network.

A gang using easily available software break into a WEP protected wireless network and find out what a surfer has been up to as well as having access to his computer and his internet connection.

Though they have used a fair amount of dramatic licence, what they do (rather than how) is possible.

MacBook Pro issue resolved totally now I hope

In a previous blog posting I mentioned the problems here and here, I was having with my 802.11n WPA2 encrypted network and a MacBook Pro.

In the end what seemed to help was ensuring that Airport was at the top of the network configurations.

However even with that it still took the MacBook Pro some time after sleep to re-connect to my 802.11n Airport wireless network. Even then sometimes it failed to re-connect so I had to turn the Airport on the MacBook Pro off and back on again.

The MacBook Pro has now been upgraded to Leopard 10.5.2 and this does seem to have resolved the issue fully, with the MacBook Pro re-connecting to the wireless network immediately rather than after a minute or so.

Hopefully it will remain resolved and not happen again.

MacBook Pro Airport issue resolved, possibly…

I think I may have resolved my MacBook Pro Airport re-connection issues.

I ensured that Airport is at the top of the network configurations and this seems to have solved my re-connection issue when running a pure 802.11n wireless network.

I find it strange that something as simple as moving a network configuration to the top should solve this issue with an 802.11n network. However it is not an issue when running in b/g compatible mode!

Well it’s working for me now.

MacBook Pro Airport Issues Continue…

Since I upgraded my Airport Extreme network to a pure WPA2 802.11n 5GHz wireless network, my MacBook Pro has consistently failed to re-connect to the network after waking from sleep.

It does this in both 10.4.10 and 11.5.1 and when connected to an Airport Express running 802.11g WPA/WPA2 no problems, will re-connect every time.

My iMac which is connected to the 802.11n network does not have this issue.

If I move back to 802.11n/b/g on the 2.4GHz radio mode the problem disppears.

I have followed the advice given by Apple here and another piece of advice which  said ensure the Airport is at the top of the network configurations, but alas no luck.

Once or twice the MacBook Pro has reconnected, but 99% of the time no re-connection and the only solution is to either join the 802.11g network or re-boot.

Annoying.

MacBook Pro Airport Sleep Issues

My MacBook Pro has stopped re-connecting to my Airport network after sleep. I am sure this is down to the fact that I have started to use it on a WPA2 802.11n wireless network.

Checked my settings, but nothing there that seemed out of order.

A quick Google search and up comes through this site the following Apple KB article which has a solution, will try it and see what happens.