Remote VBScript issues

1. Install the latest version (5.6.0.8831) of Windows Script 5.6
For Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=887fce82-e3f5-4289-a5e3-6cbb818623aa&DisplayLang=en

For Windows XP and Windows 2000
http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en

2. Check the registry key HKLM\SOFTWARE\Microsoft\Windows Script Host\Settings\Remote, make sure it is 1 and the type is "REG_SZ"

3. Register wscript.exe with DCOM using the command “wscript.exe –regserver”
Restarte the machine and try to execute the script locally in the Win 2003 machine if it works fine try to execute it remotely.

4. Check is there any errors reported in the win 2003 server’s event log

5. Please have a look at this article and implement the steps mentioned in this article. http://support.microsoft.com/default.aspx?scid=kb;en-us;875605#6

If the Windows Firewall in Control Panel is enabled, you need to do the following to make the remote script.

a. On the Exceptions Tab, choose "Add Port", Name is "RPC" and the port is 135
b. On the Exceptions Tab, choose "Add Program", click on "Browse" button and choose "wscript.exe" from c:\windows\system32 or c:\winnt\system32

6. Try to add the following permissions.
a. Add the Specific user (network user who try to execute the script) and Everyone in DCOM Config -> MyComputer -> ComSecurity ->Access Permission and select the Local Access and Remote Access

b. Add the Specific user and Everyone in DCOM Config -> MyComputer -> ComSecurity ->Launch and Activation Permissions and select the Local Launch, Remote Launch, Local Activation and Remote Activation

c. Add the Specific user and Everyone in DCOM Config -> WSHRemote -> Security ->Launch and Activation Permissions and select the Local Launch, Remote Launch, Local Activation and Remote Activation

d. Add the Specific user and Everyone in DCOM Config -> WSHRemote -> Security ->Access Permissions and select the Local Access and Remote Access

e. Add the Specific user and Everyone in DCOM Config -> WSHRemote -> Security ->Configuration Permissions and select Full Control and Read

Restart the machines and try to execute the script.

7. Check is there any Hardware Firewall. The Port 135 should allow two-way communication.