RE: Executing a program on a Windows 2003 server

The RMTLOCNAME parameter should point to your Domain name.  Our DNS
server resolves that across all of our Win2003 Servers (we have many)
and that's really all we need, other than, of course, an entry in the
iSeries Host Table (CFGTCP Option 10).

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Fisher, Don
Sent: Thursday, October 26, 2006 1:03 PM
To: Midrange Systems Technical Discussion
Subject: RE: Executing a program on a Windows 2003 server

No, the Visual Basic program is not being executed.  I think it has
something to do with using Active Directories, but I'm not really sure.
So far, my Windows Server expert is stumped.  He thinks the lack of a
domain parameter on the RUNRMTCMD is causing an authentication problem.


Donald R. Fisher, III
Project Manager
RoomStore, Inc.
(804) 784-7600 ext. 2124
dfisher@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Shannon O'Donnell
Sent: Thursday, October 26, 2006 1:55 PM
To: Midrange Systems Technical Discussion
Subject: RE: Executing a program on a Windows 2003 server


 

The RUNRMTCMD is passing a user id and password to W2003 yes? 

And it's the actual VB program that is being called via RUNRMTCMD that
is failing?  That is, you're not calling the VB app from RUNRMTCMD and
it's calling another process and it's this other process that is
failing?

We have no problems using RUNRMTCMD with Win2003 Server as long as the
profile we are using to logon with has enough authority to the files,
directories and commands we want to access.
<clip>