SCOUG-HELP Mailing List Archives
Return to [ 20 |
February |
2008 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
This has been fixed! Looks like a bad cat-5 cable. I experimented with swapping
the cat-5 between the two ports on the mobo, and noticed no change in the lights
on the router. Hmmmm... Used a different port on the router. No change. So I
went out to the garage and grabbed another cable. Bingo!
BUT: I still can't understand why I was getting an IP address of 169.254.24.24
when the machine was configured for DHCP, and the router is set to assign IPs in
the range of 192.168.1.100-150.
Was I operating in the Twilight Zone????
Tom Brown wrote:
> Files zipped & attached. One minor detail... The W10DEX0057.NIF was NOT
[snip]
>
> See results in zip. Why do I get an IP of 169.254.24.24?
[snip]
--
Tom Brown, Catherder
thomabrown at gmail dot com
Member SCOUG, V.O.I.C.E., & SDAA
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 20 |
February |
2008 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|