Things are now getting interesting with the current problem. To start with, I sincerely thank those of you who have offered advice thus far.
I decided to take the bull by the horns and opened the NBX box to check what is inside. Surprising enough, the ribbon cable to the hard drive was not connected. I went ahead and physically attached it to the hard drive. There was so much excitement that I had solved the problem. After I turned on power to the unit, the NCP LED's (S1, S2, S3) went through the blinking motions as per manual. Following a complete boot process, the new status of the LED's now became as folows:
S1=ON, S2=OFF, S3=Blinking
This is precisely what the manual says should happen.
With this condition, an attempt was made to establish connectivity with the NBX 100 from a client desktop using Internet Explorer and also using the VT100 Terminal Emulator. No connection could be established. I tried pinging the NBX 100 from the DOS prompt using the default IP Address (192.168.1.190). The response was negative (Host unreachable). Now my morale was in check.
Like a Mandingo warrior, I decided to take another chance. This time I run a Sniffer program on the subnet to ascertain
the NBX IP address. Sniffer was returning this information.
IPaddress=0.0.0.0 and Subnetmask=255.255.255.255.
On the premise of my troubleshooting adventure, the conclusion I have come to is that there is certainly something wrong with the NCP board. What it is, I got no clue.
Another observation noted is that using fusion of intelligence and in particular the sense of hearing, the Western Digital Hard Drive in the NBX is generating a continuous noise (That of Read/Write/Seek) on the mechanism. This also is an indication that the drive's life time is about to expire.
Till next time, I will end here.
Willy Cox Chanda.firstname.lastname@example.org