pormapper on server (server IP) is not responding 2

[krytez]

We have a SCO 5.0.5 server. We recently had a power failure, After restarting the server, it no longer could contact the network.

I work primarily on Windows Operating systems so please forgive me if my understanding is a little off.

I believe some networking components may have been deleted. After the server restarted these changes took hold.

The following is the error that is generated in the logs.

WARNING: pormapper on server (server ip) is not responding.

I have tried restarting the portmapper via the "nfs stop", "nfs start" command. When I attempt the "ifconfig -a" the following is displayed.

lo0; flags=4049 <UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
perf.params:recv size:57344;send size:57344;full-size frames:1

at10:flags=404a<BROADCAST<LOOPBACK<RUNNING<MULTICAST> mtu 8232
inet 0.0.0.0 netmask ff000000
perf.params:recv size:4096;send size:8192;full-size frames:1

This I believe is the default loopback adapter, not the network card.

I then checked the host file and found that it was as expected

127.0.0.1 localhost
(My Server ip) (My server name)

When I attempt to use the netconfig command the following is displayed

sh: /etc/netconfig : not found
press RETURN to continue

When I attempt to display the networking components in the gui (the Network Configuration Manager) it does not open the window.

I assume that these are OS files and will need to be recreated, what is my best course of action? Will making a new package for the network card also install the missing networking compoments?

Thanks

 

[motoslide]

Does your /etc/hosts file contain any additional lines besides the ones you list?
What is the output of the "hostname" command?
The /etc/netconfig should actually be a symbolic link to the real utility buried in /opt/K/SCO/lli/(etc).
Here's one of mine, from a slightly older release (so actual pathname will vary from yours):
lrwxrwxrwx 1 root root 36 Nov 26 1997 netconfig -> /opt/K/SCO/ll
i/5.0.4d/ncfg/netconfig


Using "nfs stop" and "nfs start" wouldn't likely resolve anything if the portmapper has failed. Your system should have additional symptoms than those you list. Have you examined /usr/adm/syslog and /usr/adm/messages? How about /etc/rc2.d/messages?

Back to the /etc/hosts file. If your system name is listed twice, and with differing IP addresses, portmapper will fail on a reboot.

 

[PHV]

And does hwconfig -h list your NIC driver ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[motoslide]

On that same idea (as posted by PHV), examine your /usr/adm/messages to see where the network adapter had been found in the past. Any change of IRQ would render it unuseable without reconfiguring the kernel to match. I've had a few systems which would re-allocate IRQ's if the mouse wasn't plugged in, then have problems finding other hardware devices.

 

[krytez]

Thanks to all who responded.

A number of files had been deleted in an attempt to save space (including a number of files in the etc directory). These were restored from a backup.

The network card driver was reinstalled and the system is functional once more.