Re: NT4 -> Win2K3 question

3. For your description: Those 6 PCs *CAN* list DC1 & DC2 NetLogon or
Sysvol directory even I logon as domain Administrator. It said Access
denied. I'm confused. Please check the symptoms you listed and let me
know
if there are any incorrect.

Sorry, typo error. It should be "Those 6 PCs *CANNOT* list DC1 & DC2
NetLogon or Sysvol directory even I logon as domain Administrator. It said
Access denied. I'm confused. Please check the symptoms you listed and let
me know if there are any incorrect."

5. Try to dis-join one client out of domain and rejoin it to see the
results.
Tried. One of the PC dis-join the domain (change to join a workgroup, named
"WORKGROUP"), then I try to re-join the domain. But it should cannot find
the domain.



"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:C$oyBqlmGHA.4528@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I have following suggestions:

1. Change the dynamic update to nosecure & secure.

2. Verify if PDC emulator is working or you can install dsclient on the
NT4
client.

http://support.microsoft.com/default.aspx?scid=kb;en-us;288358

3. For your description: Those 6 PCs *CAN* list DC1 & DC2 NetLogon or
Sysvol directory even I logon as domain Administrator. It said Access
denied. I'm confused. Please check the symptoms you listed and let me
know
if there are any incorrect.

4. Try: ipconfig /flushdns
ipconfig /registerdns

5. Try to dis-join one client out of domain and rejoin it to see the
results.

thanks.



Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
From: "tony@i-cable" <tony@xxxxxxxxxxxx>
Subject: NT4 -> Win2K3 question
Date: Tue, 27 Jun 2006 17:14:12 +0800
Lines: 37
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <uqW0VocmGHA.1576@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 59.188.32.186
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24253
X-Tomcat-NG: microsoft.public.windows.server.migration

I fail in my last migration due to some of the computers (Windows NT
workstation /w SP6) fail to access Windows 2003 server. Do you have any
idea why? Thanks.

Background
==========
We have total 50 PCs most of them are Windows NT Workstation and the
rest
is
Windows 2000 in the network. All of them get IP and TCP/IP setting from
DC1
DHCP server

We have 2 Win2003 standard edition DCs. DC1 installed DNS integrated
with
AD and secure DDNS, WINS and DHCP. DC2 installed DNS integrated with AD
and
secure DDNS, WINS and printer server.

We has 6 Windows NT Workstation PCs has problem.

Symptoms
=========
1. Those 6 PCs can get IP from DC1 DHCP server.

2. Those 6 PCs can logon to the domain

3. Those 6 PCs can ping DC1 and DC2.

4. Those 6 PCs can list DC1 & DC2 NetLogon or Sysvol directory even I
logon
as domain Administrator. It said Access denied.

5. Those 6 PCs do not run the logon script. I believe it is because
those
PCs cannot access DC1/DC2 NetLogon directory

6. After change DNS integrated with AD and secure DDNS, only few PCs
name
and IP address show in the zone under Forward Lookup Zone.









.

Relevant Pages

  • Re: NT4 -> Win2K3 question
    ... NetLogon or Sysvol directory even I logon as domain Administrator. ... Change the dynamic update to nosecure & secure. ... I fail in my last migration due to some of the computers (Windows NT ... We has 6 Windows NT Workstation PCs has problem. ...
    (microsoft.public.windows.server.migration)
  • Re: NT4 -> Win2K3 question
    ... I suspect it can be a name resolution issue and I suggest you check the ... NetLogon or Sysvol directory even I logon as domain Administrator. ... Change the dynamic update to nosecure & secure. ... We has 6 Windows NT Workstation PCs has problem. ...
    (microsoft.public.windows.server.migration)
  • Re: Prohibit Administrator rights on remote PCs
    ... have to be members of local Administrators group at the logon time ... (otherwise, the logon script, running in their security context would not be ... The second option would not prevent users from connecting to other PCs via ... Remote Desktop (while there are ways to somewhat remediate this, ...
    (microsoft.public.windows.group_policy)
  • Prohibit Administrator rights on remote PCs
    ... There is no issue if they logon interactively on any PC in the domain with admin rights - only accessing PCs remotely is a concern. ... I guess the first option is more safer but I feel the second option is better as I can easily manage the group membership in active directory. ...
    (microsoft.public.windows.group_policy)
  • Unable to log on directly to domain
    ... domain administrator user name and psword. ... I can now only logon unto the machine ... logon through local administrator profile. ... to the domain with use of domain username and psword. ...
    (microsoft.public.windowsxp.network_web)
Loading