Re: net use z: \\FQDN\share issue
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Tue, 29 Nov 2005 23:11:16 -0500
In news:3AA85205-A5B4-463D-BE4C-5AA0E094D475@xxxxxxxxxxxxx,
agcastle2000 <agcastle2000@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which
I then commented about below:
>> Good to hear, Archie.
>>
>> Did you see my other post about pinging the name
> Thanks for your continued support this far.
> Yes. I saw your other post but I first tried what you suggested
> earlier - just to put the DNS Servers on the client's own site. So
> far, there were no disconnections since Saturday but we only have it
> on all IT staff which are all XP machines. Most likely, it had fixed
> the issue but until it's tried and running on NT and 2000s, it's
> still too premature to conclude at this stage.
>
> I will surely keep you posted.
>
> Another quick question, what needs to be done if I need to reinstall
> 2003 DC (AD Integrated DNS) on a machine which is hosting the zone for
> fabricorp.costoso.com? This was the NT PDC prior to the upgrade but
> the operations master role (PDC) was already moved to another DC.
>
> Have a good day!
You want to reinstall Windows 2003 on a current 2003 machine? Why? Is there
something wrong with the OS?
If so, I would use a service pack integrated source i386 cdrom and choose to
upgrade it. THe zone will still be intact, as well as all other settings and
the machine's configuration.
The PDC Emulator role has really nothing to do with the zone or the zone
type (where it;s stored, which is all that AD Integrated means, meaning the
zone will be stored in one of three different locations in the AD database,
depending on what replication scope you set the AD Integrated zone to be).
The role of the PDC Emulator has changed much since what a "PDC" did in an
NT4 domain. In NT4, that guy was the ONLY writable copy of the directory
service database, and the BDCs only had a read-only copy of it. In AD, the
PDC Emulator "acts" as a PDC for an NT4 BDC (if there are any left in the
domain). It also acts (whether there are NT4 BDCs or not and no matter what
functional level the domain or forest is in), as the time sync source for
ALL machines in a domain, the password synchronizer for all legacy (NT4
workstations and Win9x machines) and also the DC that one would create/edit
a GPO (which can be changed). Time sync is EXTREMELY important for Kerberos
to function. All machines must be within the 5 minute time skewed allowed by
Kerberos (adjustable but recommended to leave it alone).
Just as a reminder, which I'm sure you are probably already aware of, there
are no such things as a PDC or BDC with Win2000 or 2003. All DCs are
replicas and are all writable.
Ace
.
- References:
- Re: net use z: \\FQDN\share issue
- From: Ace Fekay [MVP]
- Re: net use z: \\FQDN\share issue
- From: Ace Fekay [MVP]
- Re: net use z: \\FQDN\share issue
- From: Ace Fekay [MVP]
- Re: net use z: \\FQDN\share issue
- From: Ace Fekay [MVP]
- Re: net use z: \\FQDN\share issue
- Prev by Date: Re: Cannot contact the DNS server, 2003 server
- Next by Date: Re: Cannot contact the DNS server, 2003 server
- Previous by thread: Re: net use z: \\FQDN\share issue
- Next by thread: Re: net use z: \\FQDN\share issue
- Index(es):
Relevant Pages
|