RE: Shares Read-Only (NT4 -> 2003/AD Migration)

From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 02/06/04 

Date: Fri, 06 Feb 2004 10:16:42 GMT

Hello Michael,

Thank you for your post.

Could you let me know more information regarding the issue?

1. How many servers are affected by this problem?

2. As I understand it, only the file shares have been changed to Read-Only
and other folders are OK. Am I correct?

3. The previous system policy will be kept during the upgrade. Could you
let me know how you set the system policy?

Thanks!

Regards,
Joe Wu
Product Support Services
Microsoft Corporation

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
|Content-Class: urn:content-classes:message
|From: "Michael Sloan" <anonymous@discussions.microsoft.com>
|Sender: "Michael Sloan" <anonymous@discussions.microsoft.com>
|Subject: Shares Read-Only (NT4 -> 2003/AD Migration)
|Date: Thu, 5 Feb 2004 20:00:05 -0800
|Lines: 14
|Message-ID: <006d01c3ec65$b3f955e0$3a01280a@phx.gbl>
|MIME-Version: 1.0
|Content-Type: text/plain;
| charset="iso-8859-1"
|Content-Transfer-Encoding: 7bit
|X-Newsreader: Microsoft CDO for Windows 2000
|X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
|Thread-Index: AcPsZbP5PpYMi6Z2SUGMfk19jkARNQ==
|Newsgroups: microsoft.public.windows.server.migration
|Path: cpmsftngxa07.phx.gbl
|Xref: cpmsftngxa07.phx.gbl microsoft.public.windows.server.migration:7579
|NNTP-Posting-Host: tk2msftngxa07.phx.gbl 10.40.1.58
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|Good evening,
|
|For some reason, we are having issues with read-only
|shares. This only happened on servers that
|were "migrated" vs. a new install of 2003. At first, I
|though the global security policy for "authenticated
|users" was the culprit <set to read-only>. A change
|didn't seem to help <changed back>. The clients in
|question are pre-2000 clients (95 & NT workstations). We
|did reduce the security per MS technote (SMB/secure
|channel) to support these clients and added the
|NT4Emulator=1 DWORD in the registry of all DCs. Any
|ideas? Needless to say, our users are complaining!
|Thanks...
|

Relevant Pages

  • Shares Read-Only (NT4 -> 2003/AD Migration)
    ... This only happened on servers that ... were "migrated" vs. a new install of 2003. ... though the global security policy for "authenticated ... question are pre-2000 clients. ...
    (microsoft.public.windows.server.migration)
  • Re: Help with setting up Sites.
    ... Site A - respresenting physical site B ... servers is increasing by the day. ... Do you have any DCs at SiteB? ... clients servers in the relevant sites to authenticate against them. ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding machine to domain with NATed IPs
    ... sounds that the DCs are not reaching the>> clients ... can the servers pint the clients by IP and Name? ... we specified these IPs as DNS server within ...
    (microsoft.public.windows.server.active_directory)
  • Re: Computer Browsing Service - anyone want to contribute for a good conversation?
    ... Do you have all client machines and servers ... Browse lists are built and exchanged by the computer browser service. ... It doesn't matter which subnet your clients are in. ... The most common cause of master browser failures is multihomed ...
    (microsoft.public.windows.server.networking)
  • Re: adding machine to domain with NATed IPs
    ... Can you ping back the clients and servers? ... can the servers pint the clients by IP and Name? ... there are five DCs for three sites. ... > Type: SRV (Service location) ...
    (microsoft.public.windows.server.active_directory)