Hey Davida,
The problem appears to be that someone hardcoded their IP addr instead
of letting DHCP assign it. This becomes problematic if DynIP's are
shuffled quite often. If you can, make sure that everyone is using DHCP
not going into TCP/IP properties and setting their addr. The main reason
p
The bogus ethernet address is probably a known problem with the eepro100
driver, which is fixed in the newset driver, which you can find at
http://cesdis.gsfc.nasa.gov/linux/drivers/. After you get rid of the hw
address problem, dhcp will probably work.
[EMAIL PROTECTED] http://
Howdy,
Strange thing is happening when I am installing 6.1 on (work) Pentium III's.
During install, I choose dhcp (using Tier 1 NIC with eepro100.o Module).
When the install is finished and the PC reboots...dhcp gives it an address
that is static for another PC. ifconfig shows a bogus Ethernet a
