FW: SRT071224815417:pro/fpp/cg/Windows Svr 2000 EN

FYI

 

---

From: Leon Chen [mailto:@microsoft.com]
Sent: Monday, December 24, 2007 5:22 PM
To: Hecny Group IT - Eric Poon
Cc: Xue-Song Wang
Subject: RE: SRT071224815417:pro/fpp/cg/Windows Svr 2000 EN/User cannot connect to Svr. share folder

 

Dear Eric,

 

Greetings!

 

The following is a summary of the action done in the live-meeting , for your reference.

 

 

1.  The shared folders can be displayed by “net share” on the server, which means the server service (lanmanserver) works well.

2.  It’s OK to access share folders locally.

3.  When the clients access the shared folder, it will pop out confidential dialog but can not pass the authentication.

4. Succeed to telnet 139 and 445.

5. Lot of events reporting failing to locate GC.

 

6. Find both DCs in this domain do not share the sysvol out and the sysvolready registry value is 0x0. So the DCs do not consider themselves as functioning DC (also GC). This is the direct cause that leads to GC locating failure.

7. We find on both DCs, the sysvol contents are moved into “pre-existing” folder, which is the symbol of (non)Authoritative sysvol replication.

8. We further check FRS event logs on both DCs and find the following process:

a)     On 12/15 morning, szxpdc executed D4 (authoritative sysvol rebuild) action. This made it to remove the sysvol share and move the sysvol contents into “pre-existing” folder at first.

b)     The whole rebuild process was not finished and szxpdc executed another D2 (non-authoritative sysvol rebuild) action. At that time, the sysvol was empty. SZXPDC reported warning indicating rebuild structure error once per day since then. SZXCOM could still run well at that time.

c)     On 12/19 morning, SZXCOM executed D2 action (non-authoritative sysvol rebuild). So it removed its sysvol share and moved sysvol contents into “pre-existing” folder and wait for replicating from SZXPDC. However, as SZXPDC did not rebuild its own sysvol structure, SZXCOM could not get replication from SZXPDC.

d)     From then on, both DCs did not share sysvol out and did not running correctly as DCs.

9. After determining the root cause, we take the following actions to solve the problem:

e)     On SZXCOM, move the previous sysvol contents back to the correct place under %windir%\sysvol\sysvol\.

f)       On SZXCOM, take D4 action to rebuild its sysvol:

Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup\BurFlags = D4

Restart File Replication service. Wait for some time and SZXCOM finishes D4 action and shares the sysvol out.

g)     On SZXPDC, take D2 action to replicate from SZXCOM:

Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup\BurFlags = D2

Restart File Replication service. Wait for some time and SZXPDC finishes D2 action and shares the sysvol out.

 

10. You will test to access the shared folder and let us know the result.

 

 

Thanks and have a nice day!

 

Best regards,

Leon Chen

 

From: Leon Chen
Sent: Monday, December 24, 2007 1:38 PM
To: 'ny.com'
Subject: RE: SRT071224815417:pro/fpp/cg/Windows Svr 2000 EN/User cannot connect to Svr. share folder

 

Dear Eric,

 

Good afternoon!

 

Please login the live-meeting by click .

 

Thanks and have a nice day!

 

Best regards,

Leon Chen

 

From: Leon Chen
Sent: Monday, December 24, 2007 12:00 PM
To:
Subject: SRT071224815417:pro/fpp/cg/Windows Svr 2000 EN/User cannot connect to Svr. share folder

 

Dear Eric,

 

Thanks for contacting Microsoft. My name is Leon Chen. It's my pleasure to work with you on this case.

 

Based on our discussion, we will manage a live-meeting to check the problem together at 2PM this afternoon. I will send a link to you before that time.

 

By the way, shared folder is served by server service (lanmanserver), we can use ‘net share’ to check if the shard folders are still there?  

 

Thanks for your time and efforts. Please feel free to let me know if you have any questions or concerns.

 

Best regards,

Leon Chen

Platform Support Group

Global Technical Support Center, Greater China Region

 

MAIL:

TEL:   [phone] X 6436

FAX :  [phone]

 

My working hours are from 9:00 AM (GMT+8) to 6:00 PM (GMT+8), Monday through Friday.

 

Delighting our customers is our #1 priority.  We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to email our Managers at . You can also contact my manager, Michael Yuan at 86-21-6469-1188X4233 or by emailing to .

 

=================================================

Microsoft Security Advice: Have you installed the latest patch according to Microsoft Security Bulletin?  If not Microsoft strongly advises you to review the information at the following link http://www.microsoft.com/security/security_bulletins and visit Windows Update at to install the latest patch.  Running the SCAN program from the Windows Update site will help to insure you are current with all security patches.

=================================================

 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit
______________________________________________________________________