User Not Trusted
Anyone know why I would start getting these messages in the online.log? listener-thread: err = -956: oserr = 0: errstr = (informix@3282.mbf-law.com): Client host or user (informix@3282.mbf-law.com) is not trusted by the server. As near as I can tell, a custom program we use from Wilson Technology is causing this error to pop up, but I want to know why it's "not trusted". Informix Dynamic Server Version 7.30.TC7 on an NT Server. Thanks. ----------------------------------------------------------- Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com
Like I'd trust any of my users... ;-) ~Meee * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network * The fastest and easiest way to search and participate in Usenet - Free!
wyn441 wrote: > > Anyone know why I would start getting these messages in the > online.log? > > listener-thread: err = -956: oserr = 0: errstr = > (informix@3282.mbf-law.com): Client host or user > (informix@3282.mbf-law.com) is not trusted by the server. > As near as I can tell, a custom program we use from Wilson > Technology is causing this error to pop up, but I want to know > why it's "not trusted". > > Informix Dynamic Server Version 7.30.TC7 on an NT Server. Because the client is not listed on the server as a trusted client. Art S. Kagel
Well, I don't trust them lusers either, but here's a little more information. First "informix" user is in the domain admin group and I believe is considered the equivalent of root in the Unix shell. Trusts are normally something established between domains not servers or workstations (at least in the NT world). The computer itself, 3282 belongs to a person who always logs in as dmb (with no mistrust error messages). It uses the Client for Microsoft Network and logins into the mbf-law domain. And finally, the 3282 computer is a 95ws and all tcp/ip addresses are dynamically assigned with a lease expiration of 30 days. My memory sucks (worse than my math) and I don't think I could remember to go change the hosts file every 30 days if this were the fix. Just a note here, when a user logs in incorrectly the error message is: listener-thread: err = -951: oserr = 0: errstr = wcl: Incorrect password or user wcl is not known on the database server. What I was able to determine is that she uses one particular program written by Wilson Technologies and everytime she executes a process the error messages spits out (the program uses persistent connections). I'm assuming the programmer has hardcoded the informix user id and will not substitute dmb. Since the processes succeed, I'm assuming that the login informix@3282.mbf-law.com is connecting (with the correct password) just not "trusted". ----------------------------------------------------------- Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com