Solaris 8: NIC Loses IP Address On Reboot

I have a box with a fresh installation of Solaris 8; the installation completed succesfully but I'm having a problem getting the network card to "remember" its IP address.  I have tried editing the network configuration files manually as well as using 'ifconfig' all with the same result: the NIC will initially take the 9.43.239.31 address that I give it and allow traffic in both directions with no errors until reboot, whereupon it will default back to 9.43.239.1 and stop working.

'ifconfig -a' shows 9.43.239.1 after reboot even though '/etc/hostname.hme0' and '/etc/hosts' both are both always set for 9.43.239.31 - if I run 'ifconfig hme0 9.43.239.31' the correct address will show up for 'ifconfig -a' and the NIC will function nomrally until reboot.

How can I get the NIC to "remember" its IP address?
Rishi ChopraSoftware EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NukfrorCommented:
Can you do the following and return the output:

ls -la /etc/hostname.hme*
cat /etc/hostname.hme0
cat /etc/hosts
0
NopiusCommented:
Check if  /etc/hostname.hme0
has leadind '\n' after 9.43.239.31:

---[cut]---
9.43.239.31

---[cut]---
This may help.
Also grep all occasions of 9.43.239.1 in /etc/ and /etc/rc*/*
previous admin might left something there
0
yuzhCommented:
Make sure that your /etc/hosts file looks like:


127.0.0.1       localhost
9.43.239.1 mybox.mydomain mybox     loghost

and

/etc/hostname.hme0 file

looks like:
 mybox.mydomain

or just
mybox

and
/etc/nodename file looks like

mybox


PS: you need to replace "mybox" and "mydomain" with the real hostname and domainname of your box
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

NopiusCommented:
yuzh:

/etc/hostname.hme0:
9.43.239.31

with a single IP without hostname in /etc/hosts, should also work.

0
CadburyKatCommented:
You may need to modify  /etc/netmasks with an entry which looks something like this:

9.43.239.31      255.0.0.0
0
Rishi ChopraSoftware EngineerAuthor Commented:
I believe the reason for the error was one of two things:

(1) the '/etc/hosts' file which had an entry like:

9.43.239.31 roswell loghost

rather than

9.43.239.31 roswell.something.somethingelse.com roswell loghost

(2) the '/etc/netmasks' has an entry like:

9.43.236.0  255.255.252.0

rather than

9.43.239.31 255.255.252.0

The only change I made was this file; once I made the change and rebooted the correct IP stuck.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.