[dba-Tech] Hub problem

There, a reply from someone who KNOW WHAT THEY ARE SAYING on this
subject, Unlike ME. ;-)

No offense to anyone else who replied to this tread of course. Only
referring to myself with that comment.

Thanks Jon.

GK

On Tue, Dec 29, 2009 at 2:22 PM, Jon Tydda <jon at tydda.plus.com> wrote:
> 169.254.x.x is an automatic configuration address - explained here:
> http://ask-leo.com/why_cant_i_connect_with_a_169254xx_ip_address.html
>
> Another site
> (http://www.pctechbytes.com/network/networkdetail.php?Fix-169.254.x.x-IP-Add
> ress-Problem-4) suggests this:
>
> If the computer network was working then quit:
>
> 1. Release and renew the IP Address. Go to Start>Run and type cmd and hit
> OK. At the prompt, type ipconfig /release and then reboot. You could just
> type ipconfig /renew next, but rebooting is more thorough.
> 2. If that doesn't work, release the IP again and shutdown. Next power cycle
> the modem and router.
>
> A third site (http://www.chicagotech.net/troubleshootingipconfig.htm) says:
>
> Why do I get 169.254.x.x IP?
>
> Symptom: The Internet Assigned Numbers Authority (IANA) has reserved
> 169.254.0.0-169.254.255.255 for Automatic Private IP Addressing. If the
> computer can't get ip from DHCP, APIPA provides an address that is
> guaranteed not to conflict with routable addresses.
>
> Resolutions: 1) Make sure you have good connection.
> 2) Check the hardware and settings.
> 3) Make sure the DHCP is working.
> 4) For the test, you can assign static ip. If static ip works, it is
> possible DHCP issue. If static ip doesn't work, check the hardware or
> connection.
> 5) WinSock2 stack may be corrupted and need to repair.
>
> Hope that's of some use!
>
>
> Jon


-- 
Gary Kjos
garykjos at gmail.com