Worthless Admins

[Jay Laury]

Admins mean nothing - no, not the human ones...

I'm having a permissions problem on my home network. I'm running
three (3) Windows 2000 Pro workstations and one W2K Advanced Server.
The Advanced Server is not a PDC; it's just part of a peer
configuration. I recently made changes to the server, and somewhere
along the way, the user accounts on the workstations could no longer
modify/write to the primary data share, which is a secondary
(physical) drive on the Server. The user accounts in question are all
part of the Administrators group on all 4 systems, and have been for
many months.

The changes I made included installing Visual Studio .NET 2003 (with
the .Net Framework - v1.1.4322.573), and updating Windows and SQL
Server 2000 to the latest and greatest service packs. Furthermore, I
attempted to install SQL Server Reporting Services which would not
allow me to complete the installation because I didn't have the
rights, although I was logged-in with the local
administrator(account). Now this could be a Reporting Services
problem, but I thought it was worth noting anyway.

I guess I was wondering if anyone has experienced weird/similiar
rights issues after installing .Net Framework/ Visual Studio .Net 2003
and/or Service Packs - before I try to reinstall everything from
scratch.

Any help would be appreciated.

JL

 

[Jay Laury]

One more related weird behavior...

If I disconnect the drive letter mapping to the server share, then
reconnect using the UNC$ method (\\servername\G$) then I have full
rights to the files, etc. It's noteworthy that I was not prompted for
a u/p, so it appears to be using the account I've logged into on the
workstation.

To make sure my problem wasn't a corrupted mapping, I disconnected,
then reconnected to the share itself, but this put me back to
read-only status.

Ideas?

JL