Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 418
  • Last Modified:

I cannot edit remote scripts (e.g. .bat, .cmd, .js) from Win 2003 R2 even when I have Full permissions

I have just added a Win 2003 R2 server as a second DC in a domain which previously had just a single DC running Win 2003 (not R2).

When I attempt to edit a remote file with a script extension (e.g. .cmd) I get an error box saying "Windows cannot access the specified device, path or file.  You may not have the appropriate permissions to access the item."  I first noticed this when attempting to edit a logon script within the Group Policy Editor, but it happens with any remote file, whether I use a UNC path or a mapped drive to access it.  I can create, delete and rename script files, and when I change the extension to .txt I can edit them and then rename them back to their previous extension.

I am doing all the above with the domain administrator account on the server running R2.  If I log in to the non-R2 server with the same account I can edit script files (both local and remote, including ones physically held on the R2 server).  I can also edit the same files remotely when logged in (with the same account) to a Windows XP client.

I will try to check here for answers as often as possible, but please be patient if I don't get straight back to you since I only work part-time on this network.
0
atfis52
Asked:
atfis52
  • 2
  • 2
1 Solution
 
KCTSCommented:
Check that your anti-virus allows you to access remote files of the sepcified file type - I had a similar problem and tracked it down to the fact the Mcafee AV was set to prevent remote access to such files.
0
 
atfis52Author Commented:
No anti-virus is installed on any of the three machines I have used (the R2 server, the non-R2 server and the XP client).
0
 
atfis52Author Commented:
I have fixed the problem: when, on the server which couldn't edit scripts, I moved the server hosting the files into the Intranet zone I became able to edit.  I have no idea which security setting in Internet Options was doing it, but R2 must lock things down even tighter than 2003 did by default.

Many thanks to netman66 whose answer to http://www.experts-exchange.com/Hardware/Servers/Q_22138144.html put me on the right track, and many thanks to Copernic Agent basic (http://www.copernic.com/) which found that solution when neither Google nor the EE search had done so.
0
 
KCTSCommented:
Ok at least its solved now
0
 
modus_operandiCommented:
Closed, 250 points refunded.
modus_operandi
EE Moderator
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now