Software application development
This blog is intended to provoke discussion and exchange between like minded software application developers, engineers, architects, project managers - and keen hobbyists too.
Wednesday 2 January 2008, 6:59 PM
169.IP address issues
I actually started the thought process for this blog while holidaying in a beachside cabana in Bermuda. Hugely impressed by the fact that the main hotel reception’s wireless signal could just about reach out as far as it did I began sending snaps home and watching the football results online with some glee.
Foolishly – however, after two days of connected bliss - instead of just closing up my Mac PowerBook G4 and putting it to sleep. I opted to shut down and turn it off completely. Upon restart, could I get the machine to talk to the wireless signal as strong as it was? I could not.
Now, I may not be a networking specialist, but I have travelled far and wide with this machine and reset AIRPORT and NETWORK PREFERENCES a billion times and always managed to get re-connected. As a cold sweat warmed up and my case of cyber dependency took hold I played and played with the settings getting an IP address assigned to me with no problem, but it would not allow me to connect the dots and complete the picture.
Back home now, Mr Mac decides that my home signal is fine and all is peachy. Thinking back, I may have come unstuck like this once before. As I understand it, this situation may be down to a 169.IP address being assigned by the DHCP server. In a public area where I could not simply ask the hotel to reboot their router for me as one guest among many I was stuck. I could not find a way to manually override things from my end, so if anyone knows more than I do I’d love to hear about it.


