|
|||||||
 |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
07-06-2005, 02:39 PM
|
#1 |
|
Member (9 bit)
Join Date: Feb 2002
Location: Phx, AZ
Posts: 317
 |
Windows can't read 168.yyy???
I've heard that there is certain networking addressess windows just can't read? [It was on a test I toolk, don't know the specifics]
Like 168.***.***.*** or 169.****.****? ? Anyone hear anything about this? |
|
|
|
07-06-2005, 02:46 PM
|
#2 |
|
Professional gadfly
Join Date: Jan 2002
Location: Minneapolis, MN
Posts: 6,364
 |
If Windows tries to get an IP address via DHCP but fails, it will revert to an address starting with 169. This generally means there is a problem with your network. Perhaps that is what the test question was referring to.
|
|
|
|
|
07-06-2005, 03:17 PM
|
#3 |
|
Member (9 bit)
Join Date: Feb 2002
Location: Phx, AZ
Posts: 317
|
That sounds right, thanks.
|
|
|
|
|
07-06-2005, 05:40 PM
|
#4 |
|
Member (9 bit)
Join Date: Feb 2002
Location: Phx, AZ
Posts: 317
|
I remembered more of the question... is was "What does 169.124.24 [they gave a speivc number starting with 169.
The chocices It means 1. It is a home networking system 2. There is two network cards in the computer 3. Iti is a home network 4. none of the above any ideas? and do specific home network IP numbers exist? |
|
|
|
|
07-10-2005, 03:50 PM
|
#5 |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 37,786
|
|
|
|
|
|
07-11-2005, 01:37 PM
|
#6 |
|
Member (9 bit)
Join Date: Feb 2002
Location: Phx, AZ
Posts: 317
|
Thats it! Thanks for the link there.
|
|
|
|
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Linear Mode
