Please accept my apologies for cross-posting, but I have a Linux
networking problem that could be caused by a problem related to my
Mandrake 9.1 or VMware 4.0 configuration!
Environment:
- Host: VMware 4.0 (build 4460), Win2k SP2, Pentium III 750Mhz, 256Mb
RAM, network=NAT (IP=172.16.138.1)
- Guest: Mandrake 9.1, 80Mb RAM, boot from sda1 (4Gb), network=eth0
(driver=pcnet32, IP=172.16.138.3 allocated using Mandrake Control
Center)
Symptoms:
- nmbd fails to start at boot with 'No local interfaces' error.
- ping 172.16.138.3 gives 'Network is unreachable' error.
- eth0 can be allocated IP=172.16.138.3 manually using ifconfig, but
loses the IP address on reboot.
Comments:
- I know VMware 4.0 does not support Mandrake 9.1, but I have recompiled
VMware Tools with the correct kernel headers, and the GUI interface
works fine.
- When IP address is manually allocated using ifconfig I can see the
Samba shares from the Win2k host, after I restart smbd and nmbd, so the
networking does work.
Request:
- Why is the IP address not getting set at boot?
- Is this a problem with Mandrake Control Center in 9.1?
- Where should the ifconfig IP allocation command be written to be
picked up correctly at boot? I don't want to have to run ifconfig by
hand every time I want to connect my Linux guest to my Win2k host.
Thanks in advance........Phil Holland
--
--------------------------------------------------------
Holland Numerics Ltd
94 Green Drift, Royston, Herts SG8 5BT, UK
mobile : +44-(0)7714-279085
email : <(E-Mail Removed)>
URL :
http://www.hollandnumerics.com/
--------------------------------------------------------