That's it... No reverse name lookup zone was ever established!!!! Looks good now. So no entry in /etc/hosts is required. I like that!!!
Thanks for all your help Rob ----- Original Message ----- From: "Post, Mark K" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 03, 2002 6:18 PM Subject: Re: REXEC hang > Rob, > > When you do the reverse lookup, i.e., "nslookup 123.45.67.89" for X, Y, and > Z, do you get the hostname back? > > Mark Post > > -----Original Message----- > From: Rob Schwartz [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 03, 2002 6:11 PM > To: [EMAIL PROTECTED] > Subject: Re: REXEC hang > > > I ran into the same thing recently. I have entries in my /etc/hosts file > for a number of clients(X , Y and Z). This now works!!! > > You suggested that "DNS would have worked fine too". I have my Linux > machine pointing to a WINS/DNS server on NT. I can resolve the host names > for machines X, Y and Z but still needed to add X, Y and Z to /etc/hosts. > Am I missing something? I also tried /etc/hosts.allow with " rexecd: ALL > " but it didn't work. > > I think adding host names to /etc/hosts could easily become cumbersome. I > hope there would be an easier solution. What does everyone else think? > > Rob > > ---- Original Message ----- > From: "Rich Smrcina" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, June 03, 2002 5:35 PM > Subject: Re: REXEC hang > > > > Argghhh... > > > > OK. I seem to have solved my own problem. Actually Jeff Barnard solved > it > > for me this morning, but after he gave me the solution I switched the > machine > > I was testing on and completely forgot to implement his solution on the > new > > machine... duh! > > > > The solution was to add the host name of the client machine to the hosts > file > > (DNS would have worked fine too). > > > > > > On Monday 03 June 2002 04:11 pm, you wrote: > > > I am trying to set up REXEC to run on a Linux for S/390 machine. I'll > > > stipulate to all of the commentary about security... It seems that any > > > client that tries to connect is getting hung. I tried from Linux on > Intel > > > and Windows NT, they both just sit after entering the password. > > > > > > In the /var/log/messages file on the 390 I get: > > > Jun 3 16:04:16 webdev inetd[185]: pid 660: exit status 1 > > > > > > And in /var/log/secure: > > > Jun 3 16:04:16 webdev in.rexecd[660]: connect from 172.17.1.100 > > > > > > This seems to indicate to me that the connection is being accepted, but > > > that for some reason the command itself is failing. I'm using very > simple > > > commands (eg: df, ls -al). > > > > > > inetd.conf was modified to uncomment the exec service and hosts.allow wa > s > > > modified to allow in.rexecd from local machines. > > > > > > This is Turbolinux with kernel 2.2.19. > > > > -- > > Rich Smrcina > > Sytek Services, Inc. > > Milwaukee, WI > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > Catch the WAVV! Stay for Requirements and the Free for All! > > Update your S/390 skills in 4 days for a very reasonable price. > > WAVV 2003 in Winston-Salem, NC. > > April 25-29, 2003 > > For details see http://www.wavv.org
