Resolving The Problem

When using RUNRMTCMD, IBM recommends using an account that is local to the PC rather than a domain account. Because IBM code does very little during the PC log-in process, IBM cannot guarantee log-on consistency between Microsoft Windows versions or service packs. The RUNRMTCMD behavior seems to be consistent among releases when a local account is used.

IBM has done some limited testing using domain accounts. The following are observations from that testing.

The RUNRMTCMD command and the Incoming Remote Command function were not originally designed for Domain Logon Support. In a limited way, the domain can be explicitly specified. This would be in the form of domain\user. RUNRMTCMD only allows 10 characters for the user, so this string must be 10 characters long or less.

If the user does not exist on the PC but does exist on the Domain and the domain is not specified in the RUNRMTCMD command, log-in with the domain account is not guaranteed.

If the user exists as both a local PC account and a domain account and the domain is not listed in the RUNRMTCMD command, the local account will usually be used (but not always).

If the user exists only on the PC and no domain is listed in the RUNRMTCMD, the command should work.

Examples:

RUNRMTCMD CMD('dir C:\') RMTLOCNAME('1.1.1.1' *IP) RMTUSER('domain\gsingh') RMTPWD('password')

If the user gsingh exists on the PC, but does not on the domain, this command will not work.
If the user gsingh exists on the PC and domain, this command will work (at last testing) and will use the domain account.
If the user gsingh does not exist on the PC, but does exist on the domain, this command will work (at last testing) and will use the domain account.

RUNRMTCMD CMD('dir C:\') RMTLOCNAME('1.1.1.1' *IP) RMTUSER('gsingh') RMTPWD('password')

If the user gsingh exists on the PC, but does not exist on the domain, this command will work and will use the PC account.
If the user gsingh exists on the PC and domain, this command will work; however, it might use the PC account (usually) or the domain account (rarely).
If the user gsingh does not exist on the PC, but does exist on the domain, this command might or might not work (at last testing); it will use the domain account if it does work.