Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote access problem with WSH5.7

Status
Not open for further replies.

xwb

Programmer
Jul 11, 2002
6,828
GB
I've got a W2K installation where I'm trying to use wshremote. Basically the old machine died so I've reinstalled W2K on a new one. Decided to go for the latest of all the other stuff. Did the mods for wshremote as I've done countless times in the past but it just doesn't work.

The test runs a remote script which launches notepad on the remote machine. The basic test is that if launched on 127.0.0.1, notepad should appear on the console. I got an unknown error on line 0, char 0.

Uninstalled 5.7, installed 5.6 and it magically works.

1) Has some security feature gone into 5.7 that MS didn't advertize?

2) Could it be something to do with signing? How do I get the script signed?
 
After 5.6.6626 there was a security lockdown applied. It is hard to imagine that the fix was not applied to your Win2K machine. Are you avoiding service packs and Windows Update?

In any case this might not be the issue at all. However it is probably worth looking into:

WshRemote Object
Note:

In WSH version 5.6.6626, which ships with Internet Explorer 6 and Windows XP, a remote script is copied to memory in the remote machine and run from there. In later versions of WSH, such as the one provided by Windows Server 2003, a remote script is copied to the temporary directory of the account that accesses the remote machine. The script is run with the security settings for the remote machine and the temporary directory.
 
I've got all the service packs installed, up to SP4 and including the roll up.

Question is why 5.7 doesn't work when it is running locally. I've changed all the security settings giving everyone launch permission. I'll check the settings of the temporary directory. Maybe that has something strange.
 
If memory serves me correctly, that change was actually part of SP3 or SP4.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
Yes, it was a change in SP3. All you need to do to reverse the change is to allow launch and access permissions. It works with 5.6 but not with 5.7. I have the same settings and everything works beautifully on 5.6. Switch to 5.7 and nothing works.

I've checked the logs: nothing is logged so I can't quite figure out how to find out why it is being blocked. Windows error messages are pretty crap when it comes to this: just unspecified error.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top