Cannot network ignite server.

[Daniel Simard]

Hi i get an error message when I try to network ignite one of my hp-ux servers. (11.00) I use the gui.

Here is a little information.
Ignite version: B.3.4.115
Client has server in /etc/hosts.
Server has client in /etc/hosts.
Client allows server in in /var/adm/inetd.sec
I've even tried with adding the server in the /home/root/.rhosts's file on the client system but that would only be to execute the command with having to provide a password.

I always get the following error message:

ERROR: siloans is an unknown host.

I've tried from 2 different ignite servers and same error message.

Please help!!!

[Steven E. Protter · Accepted solution]

I can not find your error message.

So here is a possible approach.

Temporarily, remove the inet.sec and see if that clears the problem.

Check inetd.conf and make sure

47 #login stream tcp nowait root /usr/lbin/rlogind rlogind
48 #shell stream tcp nowait root /usr/lbin/remshd remshd
49 #exec stream tcp nowait root /usr/lbin/rexecd rexecd

In my case, lines 47-49 must be uncommented for Ignite towork properly.

save

inetd -c

does nslookup resolve the correct IP address?
does ping and telnet work?

You could temporarily change .rhosts to + and see if that helps.

Also check hosts.equiv if you have one.

Seems quite frustrating. I feel your pain.

SEP

[Daniel Simard]

Thanks for all your help. I've already tried all of the suggestions (sorry I forgot to mention them in my post.)

My collegue finally found the problem although we still don't konw why it was happening.

we had dns configured and also the entries were in /etc/hosts, when you would do a nslookup it would report

checking DNS...
Checking files...
server:
ip etc...

so he switched in the /etc/inetd.conf from files dns to
dns file.

so it checks the FILES first, then the DNS. and that fixed our problem ?@!?!

[Steven E. Protter]

This might break other things. Test omniback and if you are unfortuneate enough to use it, openspool.

SEP