Can't telnet - no namelist

[Gavin Davies]

Hi,

I recently had to recover my HP machine using the Core OS disk (replacing the existing kernel). Everything seems fine, but I can't Telnet to it. X-Windows works, and so does FTP. When you issue - netstat -an | grep you get the message - no namelist. I also get this message when I try to do anything to the kernel through SAM or X-Windows. When I issue dmesg, I also get the message - can't get kernel namelist.

I have checked: /var/adm/inetd.sec
/etc/services
/etc/inetd.conf
and everything seems OK.

I think that the problem is because of the kernel. I only have a a few files in the /stand directory - ioconfig and vmunix. Where system_prep doesn't work in extracting the system file.

Help!!!!!

[melvyn burnard]

This normally occurs when th ekernel in memory does NOT match the kernel that the system booted from.
After recovering your vmunix file, did you reboot the box?
I assume the file vmunix is in /stand

[Gavin Davies]

Yep. Rebooted it, and vmunix is in the /stand directory.

[KapilRaj]

Hi,

When you recover from Core-OS CD or a support CD ,the kernel recreated is just a basic kernel , i mean all the drivers what you had in the old kernel will not be there. So add it to your kernel either manualy or through sam.

Check up whether your lan dirver is loaded into the kernel or not.

best of luck

kaps

[Gavin Davies]

I can't do anything to the kernel through SAM for some reason. How do you add the drivers to the kernel manually?

Cheers

[KapilRaj]

hi,

cp /stand/system /stand/system.bak
cp /stand/vmunix /stand/vmunix.bak
vi /etc/system
insert the driver name in it
:wq! (save & come out)
mk_kernel /stand/system
This command will create a kernel named vmunix_test
mv /stand/vmunix_test /stand/vmunix
reboot

Which one should i proceed the same post or the other one which hv already started ?.

Good luck

kaps

[Gavin Davies]

Stick to this one. Cheers.

When you say insert the driver name, what will this be to get Telnet to work?

Thanks

[KAILASH PRABHU]

Best way is to restore the system file from the backup (if you have one) then use that to rebuild the kernel

[R Madhavan]

Have you overwritten /usr/conf or any other directories?. since your system is bootable now, it will be better you restore all your system files from your backup (/stand, /etc, /usr atleast)

[dhanish]

Hi,
Try craeting the files again using insf -e.

thnks

[KapilRaj]

hi sorry for the late reply,

You just hv to insert a line called lan2 in system file. If lan2 is the driver . lan2 is used in 735 workstation so it should be the same. So that your network will start functioning so telnet ftp etc etc.

best of luck

kaps

[Gavin Davies]

Problem solved now by doing the following:

Because my kernel was only a basic one from the core OS disk it didn't contain any drivers. Instead of reinstalling everything (patches) I copied a kernel over from a similiar machine. However I still couldn't use SAM to configure the kernel, so I extracted the system file from vmunix using:
/usr/lbin/sysadm/system_grep -s system
I had to add the following line to this file:
ntty 400
and also the following line to the inetconf.sec file in /var/adm:
telnet allow
I then rebuilt the kernel using mk_kernel, rebooted, and everything worked.

Thanks for all the help everyone.