Can't edit shared files over network... just locally

I just had to replace a Windows Server 2003 Domain Controller that died hard
(could not be demoted).
After some work, it is now synchronizing AD & DNS properly and everything on
that end seems to be perfect.
It is a member of a couple DFS replication groups, but they appear to be
replicating fine.

However, I can't add or edit any files via a network path, even as
Administrator. It's as if I don't have the rights, but I can do it locally
just fine, and I am the Admin.
If I try and create a file through a shared path, it says 'Access Denied'.
If I try and make a change to an existing file and then save as over top of
that file, it says "Cannot Access this file. Check Security Privileges over
the network".
I log in through RDC and create files, but then connect to that file via UNC
\\server\share and can't edit them.

I'm using file / folder NT permissions, and have the exact same setup on 3
other servers without this problem.
I know this is something dumb that's going to irritate me when I find the
answer, but for now I'm stumped.

Can anyone help?

Thanks
Tim

It sounds like your share permissions are configured as read only. Check
your share permissions and adjust as required. Domain Users > Full
Control??

--
Take care,

David
http://dcraige27.blogspot.com

"Tim Miller" <> wrote in message
news:...
> I just had to replace a Windows Server 2003 Domain Controller that died
> hard (could not be demoted).
> After some work, it is now synchronizing AD & DNS properly and everything
> on that end seems to be perfect.
> It is a member of a couple DFS replication groups, but they appear to be
> replicating fine.
>
> However, I can't add or edit any files via a network path, even as
> Administrator. It's as if I don't have the rights, but I can do it
> locally just fine, and I am the Admin.
> If I try and create a file through a shared path, it says 'Access Denied'.
> If I try and make a change to an existing file and then save as over top
> of that file, it says "Cannot Access this file. Check Security Privileges
> over the network".
> I log in through RDC and create files, but then connect to that file via
> UNC \\server\share and can't edit them.
>
> I'm using file / folder NT permissions, and have the exact same setup on 3
> other servers without this problem.
> I know this is something dumb that's going to irritate me when I find the
> answer, but for now I'm stumped.
>
> Can anyone help?
>
> Thanks
> Tim
>

Sigh... I knew it would **** me off. I don't deal with these things too
often, but could have sworn I compared that on both servers. Anyway, right
you are. I'm not even going to say how long I messed with that. Thank you
David!


"David" <dcraige27**@**verizon**dot**net> wrote in message
news:CA079CA9-E5ED-43BD-ABE6-...
> It sounds like your share permissions are configured as read only. Check
> your share permissions and adjust as required. Domain Users > Full
> Control??
>
> --
> Take care,
>
> David
> http://dcraige27.blogspot.com
>
> "Tim Miller" <> wrote in message
> news:...
>> I just had to replace a Windows Server 2003 Domain Controller that died
>> hard (could not be demoted).
>> After some work, it is now synchronizing AD & DNS properly and everything
>> on that end seems to be perfect.
>> It is a member of a couple DFS replication groups, but they appear to be
>> replicating fine.
>>
>> However, I can't add or edit any files via a network path, even as
>> Administrator. It's as if I don't have the rights, but I can do it
>> locally just fine, and I am the Admin.
>> If I try and create a file through a shared path, it says 'Access
>> Denied'. If I try and make a change to an existing file and then save as
>> over top of that file, it says "Cannot Access this file. Check Security
>> Privileges over the network".
>> I log in through RDC and create files, but then connect to that file via
>> UNC \\server\share and can't edit them.
>>
>> I'm using file / folder NT permissions, and have the exact same setup on
>> 3 other servers without this problem.
>> I know this is something dumb that's going to irritate me when I find the
>> answer, but for now I'm stumped.
>>
>> Can anyone help?
>>
>> Thanks
>> Tim
>>