Can "see" SCO server but can't ping in or out

[drose1940]

Long story...

First the facts. SCO Open Server v.5.04, 3COM, 3c905-tx NIC. The SCO server app is accessed by FacetWin apps on the Win desktops. This has worked well for several years.

This is primarily a Win environment with a legacy SCO server supporting the original filePro data app until it can be re-written in a Win-friendly DB app. Then the UNIX box will be turned off. (Don't get me started, this is a good example of non-technical administrators making technical decisions.)

We had a lightning strike and while the UNIX box was protected by a hefty UPS, the network apparently did not have supression and the SCO server NIC was damaged. In the process of replacing the NIC with another 3c905-tx, the configuration files were "messed up" (pardon the technical jargon).

I've worked through the configuration files by hand and am able to link a kernal without errors and get an error-free boot with tcp and rpc services running. Ifconfig -a reports lo0 and net1 and the "dataserv" SCO server is displayed in the Win2k network. However, I cannot ping in either direction. Pinging localhost and both the ip address and the server name is successful.

Since I'm soooo rusty at configuring a system, I'm sure that I'm missing something (obviously).

Suggestions will be appreciated.

 

[pcunix]

I'm wondering if the new card has a different ROM and therefor you need the newer driver (available at ftp://ftp.sco.com/pub/drivers/OSR504/network/e3H/)



Tony Lawrence
Linux/Unix/Mac OS X Resources

http://aplawrence.com

 

[drose1940]

The Lucent chip on both are the same number, 40-0336-004. The "bad" card was a rev-B and the replacement card was a rev-A. I will try a driver install. Can't hurt, and at this point I'm willing to try almost anything.

My hair is sparse and I can't afford to lose any more.

 

[drose1940]

New problem now.

I started to remove the old 3Com driver via Scoadmin/Network Manager. I selected the 3Com hardware and then "remove hardware". The remove process failed with a message "/usr/lib/netconfig/remove/sco_tcp: Unknown operator 192.100.0.1"

That IP address was on the system long ago but has not been used for several years. I checked S85tcp in the startup directory /etc/rc2.d. I found a line referencing the offending IP commented out but nothing else. Apparently the IP address exists in a configuration file somewhere on the machine but I've not been able to locate it.

Suggestions??

Thanks

 

[drose1940]

Oh, an addendum to the previous. This was the the way the reinstall problem began. The remove process fails leaving the card partially removed and config files in a mess. Then the re-install "succeeds" and it looks like we have two NICs and redundant function calls in /etc/strcf.d/10tcp and the link_unix fails. Messy blooming thing.

It seems that my "cleanup" was not a success as I had thought. Grrrrr.

I hate to go to a fresh install, but if I can't resolve this by Monday, I'm starting over. This system, while old, is still the main data system until the "new improved" data system is done and tested. There are 25-35 users at any given time during a work day. The natives are beginning to grumble now and there's talk of gathering filrwood for some purpose or other.

Pfui!!

 

[stanhubble]

here is a link that may be helpful. it is from an earlier version of openserver but may still be applicable.

it deals with extra net0 definitions in /etc/strcf and /etc/strcf.d/10tcp.

http://wdb1.sco.com/kb/showta?taid=107625&qid=226608577&sid=1292147414&pgnum=1

 

[drose1940]

Stan,

You are exactly correct. I didn't find this article in SCO's knowledgebase but came to the same conclusion. /etc/rc2.d/S85tcp had excess "net1" entries which had to be edited out as well. Of course replacing a bad NIC with a bad NIC didn't help my stress level either.

The network finally come back on line when I determined to replace everything from the motherboard slot forward, different 3C905-tx NIC, cable, different port on the switch. Now relink, reboot and Eh Voila!! It works... . WoooHooo and now back to the job I'm supposed to be doing.

Thanks all who responded.

Dan