RE: Executing a program on a Windows 2003 server

One last thing Don... is this VB app using any Win32 APIs within itself
to do something? If so, you might have a problem there.  Some of the
Win32 APIs, I've found recently, either do not work the way you think
they should on Win2003 Server, or else they don't work at all.  You have
to really check the MSDN documentation for each, specifically the
Remarks section of the doc, to find out.   

I got bit on that just last week with the CreateProcessWithLogonW API.

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

I'm getting event i.d.s 680 and 529, but that's without the local user
i.d.  If I add the local user i.d. back, I get nothing.  The application
isn't executed and there's nothing in the event logs to indicate a
problem.

Have I mentioned that if I execute this application using "RUN" on the
server itself I while logged in as the user i.d. in question I have no
problems?  

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

<clip>
Nope, it works fine w/AD, I'm doing it. 

Don, are you getting a eventid 680? That's actually not an error (well
it is, but not fatal) as it simply records that W2K3 backed down to NTLM
instead of Kerberos. I'm able to run commands w/domain users as the
authenticating user. I am, however, _not_ sending down a domain name. 

Eg: 

rexec -p <Secret> -u techsoftwareinc\waldenl ws1 'dir'  <-- Does NOT
work 
rexec -p <Secret> -u waldenl ws1 'dir'  <-- Works

But WaldenL _is_ a domain user account and ws1 is _not_ a DC. WS1 is a
W2K3 server and the domain is W2K3 as well.

-Walden
<clip>