Re: Newbie : Trust a PC in the domain
I suppose as in other UNIX'es the file is: /etc/hosts.equiv Try setting a + line in this file (not sure it will work on RH). But I think your problem is not in 'host trusting'. You just have to configure correctly the client side, so users can specify their login name and password while connecting. Just go to SetNet utility and configure in the Hosts tab to "Ask password at runtime" (this in case you are using ODBC). For some versions of Informix CLI (Informix Net) when you are connecting through a Borland Datababase Engine Informix native driver (SQL Links as I remember) you have to specify "No Password" in SetNet hosts configuration. Hope this helps, Octav Bart.Haezeleer.NO@SPAM.pobox.com wrote: > On Thu, 6 May 1999 15:19:03 -0700, "Chris Dornsife" > <chris_dornsife@yahoo.com> wrote: > > >.rhosts in the informixdir > > > >like this: > > > >[host username] > >chris.triport.com informix > > > > > I tried to make the .rhosts file in the $INFORMIXDIR but that doesn't > work. > I made then the .rhosts file in the homedirectory of the user I tried > with the ilogin demo and then I works. > Is there no general solutions so I can Trust all users on all machines > in our local LAN. There are no security issues. Everything for the > Internet is denied. > > >Bart.Haezeleer.NO@SPAM.pobox.com wrote in message > ><373207c6.6247661@news.pandora.be>... > >>I've currently installed Informix SE 7.25 UC5 on a Linux Red Hat 5.2 . > >>On the server everythings works. Dbaccess > >>On W98 I installed the SDK 2.02 TC2 > >>If I try to connect with ODBC I get an error -956. Machine or user not > >>trusted. > >>How can I trust all the PCs in out local domain ? Or a least one PC. > >>In the explanation with finderr they speak of a file hosts.equiv > >>What is the equivalent of this file under RH 5.2 ? I didn't find > >>anything in the man pages. > >> > >>Any suggetions are welcome. > >>Please reply with email because I can't always read this newsgroup. > >>Problems at the ISP side. > >> > >>P.S. : replace NO@SPAM with a @ > > > >