Hi Scott,
That's the ticket. I will research the dns issue (actually will have the pc
network guys do it).
Thanks all for your help.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, January 17, 2011 4:10 PM
To: Midrange Systems Technical Discussion
Subject: Re: strqsh rexec command question
hi Tim,
The error "host cannot be found" *usually* means that a DNS lookup
failed. (And yes, I know you're using an IP address. But AFIAK, the
rexec() protocol doesn't normally support them, so I bet it's looking up
the host name from the address in order to use the host name instead!)
What happens if you do an nslookup on the IP address of those that do
work vs. those that do not?
NSLOOKUP HOSTNAME('xxx.xxx.xxx.xxx')
Do you get the same results with those that work vs. those that do not?
What happens if you add the hosts do your host table? (NOTE: I do not
recommend this as a solution -- only as a test for diagnostic purposes.)
ADDTCPHTE INTNETADR(XXX.XXX.XXX.XXX) HOSTNAME((XXX.EXAMPLE.COM))
Then try the rexec again.
If that solves the problem, it means you have a DNS issue. In that
case, I'd get the DNS fixed, and remove the host table entries, and it
should then work without them. (CFGTCP option 10 is an easy way to
find/remove them.)
I doubt very highly that this is related to whether the rexec daemon is
running. If rexec wasn't running, you'd get "A remote host refused an
attempted connect operation."
Let us know what you find...
On 1/17/2011 10:20 AM, tim wrote:
I am using the following command to several pc's on my network.
strqsh cmd('rexec -u usernm -p password xxx.xxx.xxx.xxx dir')
I replace xxx with the ip address of the computer. Some computers list the
directory, while others display the error :
rexec: 001-2246 Host xxx.xxx.xxx.xxx cannot be found.
When I try to ping the computers that give me that error, it finds it.
midrange.com
