Quote:
Originally Posted by Bender
please read up on this. APIPA addresses are private addresses on a specific subnet. only APIPA adresses can talk to APIPA adresses. the reason the machine is using one of these is because it is set to determine it's IP from a DHCP server or distributer. the internet will not distribute the machine with an IP. the ISP will give the modem an IP which then allows the internal network to connect to the net through it. A DHCP server will distribute any IP specified in its scope. It will not necessarily be a class C address.
The ,machine cannot contact a DHCP server, but is configured to do so. that is the problem. the cause of the issue could be a cable, DNS server configuration locally, DNS cache locally, DHCP server itself, a router, a switch...
Guess you're learning why you do need a tech!!!!  |
Quote:
Originally Posted by whydoIneedatech
If its : 169.xxx.xxx.xxx = PC issue. Could be USB / NIC drivers, or TCP/IP corruption
|
So I said that above, which is along the the lines of what is now in bold and you say no to that and now you say yes, very strange.
I have read up on APIPA addresses and they do follow what you say but also that it can be as I said, I just had a look at a few different articles, which were very interesting and food for thought, thanks.