Hello,

one of my Active Directory server W2003 Standard R2 SP2 is giving a lot of this errors (id=1058):

Windows no puede obtener acceso al archivo gpt.ini para GPO cn={31B2F340-016D-11D2-945F-00C04FB984F9},cn=policies,cn=system,DC=cpd,DC=com. El archivo debe estar presente en la ubicación <\\cpd.com\sysvol\cpd.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Acceso denegado. ). Se ha anulado el proceso de Directiva de grupo.

That says Windows can't get the file gpt.ini.
But when I test the path from the server, all is OK. I was also checking the security permissions for that cn... and I don't find any strange... I mean, is it necesary an special permission for the cn's?

I also have 2 AD server Windows 2003 Standards else, and they has not problem with it.
May be the problem is the master schema is also a Windows standard 2003 8not R2), and the AD server is R2?

thank you!

Argie -- argie01 ------------------------------------------------------------------------ argie01's Profile: http://forums.techarena.in/members/79963.htm View this thread: http://forums.techarena.in/active-directory/1144018.htmhttp://forums.techarena.in

argie01 <argie01.3pau7b@DoNotSpam.com>, posted the following:
Show quoteHide quoteThis can be atttributed to a classic DNS misconfiguration, domain
controllers having multiple NICs, single lable name DNS AD domain names, and
other issues.

Please post an unedited ipconfig /all from the DC. If you have more than one
DC, please post one of one of your other DCs as well. Also look in DNS, let
us know if the SRV records under 'cpd.com' exist, as well as the
LdapIpAddress, which are the records that are registered by each DC that
look like:
(same as parent)  A  192.168.x.x. (or whatever the IP is)

Hello,

I was looking in DNS of my "master os schema" DC, and there are not SRV records in the root of "cpd.com" as "(same as parent) SRV 192.168.x.x.".
But there are SRV records inside subfolders --> _tcp, which are not "same as parent", but "_kerberos" or "ldap".

And these are the results of "ipconfig /all" in all my DC's:

Master of schema:

Windows IP Configuration

Host Name . . . . . . . . . . . . : servcentmb
Primary Dns Suffix  . . . . . . . : cpd.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cpd.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter (1
0/100)
Physical Address. . . . . . . . . : 00-D0-B7-B8-6F-A1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.11.14
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.11.20
DNS Servers . . . . . . . . . . . : 192.168.11.10
192.168.10.86

DC1:

Windows IP Configuration

Host Name . . . . . . . . . . . . : srvtendit
Primary Dns Suffix  . . . . . . . : cpd.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cpd.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : BCM5703 Gigabit Ethernet
Physical Address. . . . . . . . . : 00-0B-CD-1B-8C-5D
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.15.254
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.15.20
DNS Servers . . . . . . . . . . . : 192.168.15.254
192.168.11.10

DC2

Configuración IP de Windows

Nombre del host . . . . . . . : srvpenteomad
Sufijo DNS principal  . . . . : cpd.com
Tipo de nodo. . . . . . . . . : desconocido
Enrutamiento habilitado . . . : No
Proxy WINS habilitado . . . . : No
Lista de búsqueda sufijo DNS  : cpd.com

Adaptador Ethernet Conexión de área local:

Sufijo conexión específica DNS:
Descripción . . . . . . . . . : Conexión de red PRO/100 VE de Intel(R)
Dirección física. . . . . . . : 00-30-6E-29-93-78
DHCP habilitado . . . . . . . : No
Dirección IP. . . . . . . . . : 192.168.12.254
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . : 192.168.12.7
Servidores DNS. . . . . . . . : 192.168.12.254
192.168.11.10

DC3

Configuración IP de Windows

Nombre del host . . . . . . . : SVC4000
Sufijo DNS principal  . . . . : cpd.com
Tipo de nodo. . . . . . . . . : desconocido
Enrutamiento habilitado . . . : No
Proxy WINS habilitado . . . . : No
Lista de búsqueda sufijo DNS  : cpd.com

Adaptador Ethernet Conexión de área local 2:

Sufijo conexión específica DNS:
Descripción . . . . . . . . . : Adaptador de LAN PCI HP NetServer 10/100TX
Dirección física. . . . . . . : 00-30-6E-07-60-07
DHCP habilitado . . . . . . . : No
Dirección IP. . . . . . . . . : 192.168.10.86
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . : 192.168.10.1
Servidores DNS. . . . . . . . : 192.168.10.86
192.168.11.10

DC4

Windows IP Configuration

Host Name . . . . . . . . . . . . : nxdgmexcashub01
Primary Dns Suffix  . . . . . . . : cpd.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cpd.com

Ethernet adapter VLAN/VLAN 900:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : BASP Virtual Adapter
Physical Address. . . . . . . . . : 00-19-B9-F6-86-14
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.2.1.170
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :

Ethernet adapter VLAN DGM:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Broadcom BCM5708S NetXtreme II GigE (NDIS
VBD Client) #2
Physical Address. . . . . . . . . : 00-19-B9-F6-86-16
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.220.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.100

DC5

Windows IP Configuration

Host Name . . . . . . . . . . . . : nxdgmexcashub02
Primary Dns Suffix  . . . . . . . : cpd.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cpd.com

Ethernet adapter VLAN/VLAN 900:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : BASP Virtual Adapter
Physical Address. . . . . . . . . : 00-19-B9-F6-76-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.2.1.171
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :

Ethernet adapter VLAN DGM:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Broadcom BCM5708S NetXtreme II GigE (NDIS
VBD Client) #2
Physical Address. . . . . . . . . : 00-19-B9-F6-76-3A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.220.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.101


Thank you,

Argie -- argie01 ------------------------------------------------------------------------ argie01's Profile: http://forums.techarena.in/members/79963.htm View this thread: http://forums.techarena.in/active-directory/1144018.htmhttp://forums.techarena.in

argie01 <argie01.3pcdrd@DoNotSpam.com>, posted the following:
Show quoteHide quoteHello,

Thanks for posting the requested info.

It appears DC4 and DC5 are multihomed. That is a major cause of numerous
problems with DCs and AD communications.Is there anyway you can make them
single NIC?

Ace

No, I can't do anything about Dc4 and Dc5, because they are on the installations of our ISP. So, they need to have 2 IPs.

In fact, DC4 and DC5 has not this problem with AD. The problem is only in servcentmb and in svc4001.

But in the last times we had problem with all the servers hosted on our ISP: sometimes there can't get the computers in the network, when I try to explore the network using the File Explorer. But they can get the computers when I use the IP to get in there...

I think all these problems are connected.

But, could you give some track or link to understand why DNS can cause this head?
When I check my dns I find all is OK... at least until I can understand...

Thank you Ace!

Argie -- argie01 ------------------------------------------------------------------------ argie01's Profile: http://forums.techarena.in/members/79963.htm View this thread: http://forums.techarena.in/active-directory/1144018.htmhttp://forums.techarena.in

argie01 <argie01.3pe8fd@DoNotSpam.com>, posted the following:
Show quoteHide quoteHi Argie,

The reason why you can get to it by IP and not by FQDN (DNS name) is because
of the DNS records being registered by the multiple IP addresses. Do you
have Sites configured? That will control which servers are being used for
logon and authentication by your users in each location. Also, if you find
any Event log errors on any of the DCs, please post the EventID# please.

Is the cpd.com zone AD Integrated? If so, what replication scope is it set
to?

Your DNS settings on each DC are confusing. There are IP addresses that I do
not know what they belong to. When I look at DCs and a DNS infrastructure, I
try to find a coorelation with the DCs and their DNS addresses and how they
are interelated. However in this infrastructure, I do not see an
inter-relationshiop, rather a bit of confusion. If you only have 5 DCs, then
I do not understand what the following addresses belong to? They do not
appear to be DCs.
192.168.11.14
192.168.11.10

As for the two DCs at your ISP, why are DCs at an ISP? Is it for your users
to authenticate to? The multihomed issue is very problematic, too.

Here are some questions concerning your DC/DNS setup:

=============
1. What are these two DNS servers that DC1 (servcentmb - 192.168.11.14) are
using? The do not appear to be domain controllers:
IP Address. . . . . . . . . . . . : 192.168.15.254
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.15.20
DNS Servers . . . . . . . . . . . : 192.168.15.254
..                                             192.168.11.10

=============
2. What is the 192.168.11.10 DNS address that DC2
(srvpenteomad -192.168.12.254) is using? Is that a domain controller (same
question as above)?
Dirección IP. . . . . . . . . : 192.168.12.254
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . : 192.168.12.7
Servidores DNS. . . . . . . . : 192.168.12.254
..                                           192.168.11.10

=============
3. DC3 (SVC4000 - 192.168.10.86) DNS settings also use 192.168.11.10. What
is that server?
Dirección IP. . . . . . . . . : 192.168.10.86
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . : 192.168.10.1
Servidores DNS. . . . . . . . : 192.168.10.86
..                                          192.168.11.10

=============
4. DC4 (nxdgmexcashub01 - 10.2.1.170 & 192.168.220.100) has no DNS address
on the 10.2.1.170 interface. Why?
Why is it multihomed?
You should add minmally 192.168.220.100 as the DNS address.

IP Address. . . . . . . . . . . . : 10.2.1.170
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : (no DNS address ????)

IP Address. . . . . . . . . . . . : 192.168.220.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.100

=============
5. DC5 (nxdgmexcashub02 - 10.2.1.171 & 192.168.220.101), has no DNS address
on the 10.2.1.171 interface. Why?
Why is it multihomed?
You should add minmally 192.168.220.101 as the DNS address.

IP Address. . . . . . . . . . . . : 10.2.1.171
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : (no DNS address ????)

IP Address. . . . . . . . . . . . : 192.168.220.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.101
=============


Multihoming is extremely problematic for domain controllers.Numerous issues
will occur due to the multiple NICs & IPs and the DNS registration of the
additional records that occur. The additional records also place the DC as
part of two Sites, which can cause issues, too. There are too many issues to
list. It can be forced to work properly, if you like, which I will provide
instructions on how to do that below.

The following is a little background on multihomed DCs and instructions on
making it work correctly, if you feel you need to keep them multihomed. I
hpe the tutorial and instructions are helpful.

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



Multihomed DCs, DNS, RRAS servers.
By Ace Fekay, Directory Services MVP
+++++++++++++++++++++++++++++++++++++++++++++++++++++++


Multihomed DCs WILL cause numerous issues. It's highly recommended to single
home all DCs and use a non-DC for the multihoming purposes. If it is the
internet gateway, it is recommended to purchase an inexpensive, or cable/DLS
router, or even better, a Cisco or similar firewall to perform the task.

To explain why will require a little background on AD and DNS:

First, just to get this out of the way, if you have your ISP's DNS addresses
in your IP configuration (DCs and clients), they need to be REMOVED. If the
ISP's DNS is in there, this will cause additional problems. I usually see
errors (GPOs not working, can't find the domain, RPC issues, etc), when the
ISP's DNS servers are listed on a client, DCs and/or member servers, or with
multihomed DCs. If you have an ISP's (or some other outside DNS server or
even using your router as a DNS server) DNS addresses in your IP
configuration (all DCs, member servers and clients), they need to be REMOVED
and ONLY use the internal DNS server(s). This can be very problematic.

Basically, AD requires DNS. DNS stores AD's resource and service locations
in the form of SRV records, hence how everything that is part of the domain
will find resources in the domain. If the ISP's DNS is configured in the any
of the internal AD member machines' IP properties, (including all client
machines and DCs), the machines will be asking the ISP's DNS 'where is the
domain controller for my domain?", whenever it needs to perform a function,
(such as a logon request, replication request, querying and applying GPOs,
etc). Unfortunately, the ISP's DNS does not have that info and they reply
with an "I dunno know", and things just fail. Unfortunately, the ISP's (or
your router as a DNS server) DNS doesn't have information or records about
your internal private AD domain, and they shouldn't have that sort of
information.

Also, AD registers certain records in DNS in the form of SRV records that
signify AD's resource and service locations. When there are multiple NICs,
each NIC registers. IF a client, or another DC queries DNS for this DC, it
may get the wrong record. One factor controlling this is Round Robin. If a
DC or client on another subnet that the DC is not configured on queries for
it, Round Robin will kick in offering one or the other. If the wrong one
gets offered, it may not have a route to it. On the other hand, Subnetmask
Priortization will ensure a querying client will get an IP that corresponds
to the subnet it's on, which will work. To insure everything works, stick
with one NIC.

Since this DC is multi-homed, it requires additional configuration to
prevent the public interface addresses from being registered in DNS. This
creates a problem for internal clients locating AD to authenticate and find
other services and resources such as the Global Catalog, file sharing  and
the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be
logged, authenticating to shares and printers, logging on takes forever,
among numerous other issues.

But if you like, there are some registry changes to eliminate the
registration of the external NIC or simply use the internal networking
routing to allow access. Here's the whole list of manual steps to follow.

Another problem is the DC now becomes part of two Sites. This is another
issue that can be problematic.

But believe me, it's much easier to just get a separate NAT device or
multihome a non-DC then having to alter the DC. If the both NICs are
internal, I would suggest to pick a subnet, team the NICs and allow your
internal routers handle the traffic between subnets - Good luck!

1. Insure that all the NICS only point to your internal DNS server(s) only
and none others, such as your ISP's DNS servers' IP addresses.

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
move the internal NIC (the network that AD is on) to the top of the binding
order (top of the list).

3. Disable the ability for the outer NIC to register. The procedure, as
mentioned, involves identifying the outer NIC's GUID number. This link will
show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804

4. Disable NetBIOS on the outside NIC. That is performed by choosing to
disable NetBIOS in IP Properties, Advanced, and you will find that under the
"WINS" tab. You may want to look at step #3 in the article to show you how
to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Note: A standard Windows service, called the "Browser service", provides the
list of machines, workgroup and domain names that you see in "My Network
Places" (or the legacy term "Network Neighborhood"). The Browser service
relies on the NetBIOS service. One major requirement of NetBIOS service is a
machine can only have one name to one IP address. It's sort of a
fingerprint. You can't have two brothers named Darrell. A multihomed machine
will cause duplicate name errors on itself because Windows sees itself with
the same name in the Browse List (My Network Places), but with different
IPs. You can only have one, hence the error generated.

5. Disable the "File and Print Service" and disable the "MS Client Service"
on the outer NIC. That is done in NIC properties by unchecking the
respective service under the general properties page. If you need these
services on the outside NIC (which is unlikely), which allow other machines
to connect to your machine for accessing resource on your machine (shared
folders, printers, etc.), then you will probably need to keep them enabled.

6. Uncheck "Register this connection" under IP properties, Advanced
settings, "DNS" tab.

7. Delete the outer NIC IP address, disable Netlogon registration, and
manually create the required records

     a. In DNS under the zone name, (your DNS domain name), delete the outer
NIC's IP references for the "LdapIpAddress".  If this is a GC, you will need
to delete the GC IP record as well (the "GcIpAddress"). To do that, in the
DNS console, under the zone name, you will see the _msdcs folder.

Under that, you will see the _gc folder. To the right, you will see the IP
address referencing the GC address. That is called the GcIpAddress. Delete
the IP addresses referencing the outer NIC.
          i. To stop these two records from registering that information,
use the steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in DNS
http://support.microsoft.com/?id=295328

          ii. The one section of the article that disables these records is
done with this registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
            GcIpAddress

iii. Here is more information on these and other Netlogon Service records:
Restrict the DNS SRV resource records updated by the Netlogon service
[including GC]:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_dns_pro_no_rr_in_ad.asp

     b. Then you will need to manually create these two records in DNS with
the IP addresses that you need for the DC. To create the LdapIpAddress,
create a new host under the domain, but leave the "hostname" field blank,
and provide the internal IP of the DC, which results in a record that looks
like:
(same as parent) A 192.168.5.200   (192.168.5.200 is used for illustrative
purposes)

          i. You need to also manually create the GcIpAddress as well, if
this is a GC. That would be under the _msdcs._gc SRV record under the zone.
It is created in the same fashion as the LdapIpAddress mentioned above.

8. In the DNS console, right click the server name, choose properties, then
under the "Interfaces" tab, force it only to listen to the internal NIC's IP
address, and not the IP address of the outer NIC.

9. Since this is also a DNS server, the IPs from all NICs will register,
even if you tell it not to in the NIC properties. See this to show you how
to stop that behavior (this procedure is for Windows 2000, but will also
work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address:
http://support.microsoft.com/?id=275554

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
not sure which DNS to forward to until you've got the DNS address of your
ISP.
How to set a forwarder? Good question. Depending on your operating
system,choose one of the following articles:

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
(How to configure a forwarder):
http://support.microsoft.com/d/id?=323380

Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294


<==***  Some additional reading  ***==>
More links to read up and understand what is going on:

292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering]:
http://support.microsoft.com/?id=292822

Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294

246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
Server 2003
http://support.microsoft.com/?id=246804

295328 - Private Network Interfaces on a Domain Controller Are Registered in
DNS [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg
sameasparent private IP]:
http://support.microsoft.com/?id=295328

306602 - How to Optimize the Location of a DC or GC That Resides Outside of
a Client's Site [Includes info LdapIpAddress and GcIpAddress information and
the SRV mnemonic values]:
http://support.microsoft.com/?id=306602

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003 (including how-to configure a forwarder):
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/?id=291382

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Rid Pool Errors and other multihomed DC errors, and how to configure a
multihomed DC, Ace Fekay, 24 Feb 2006
http://www.ureader.com/message/3244572.aspx

257623 257623 Domain Controller's Domain Name System Suffix Does Not Match
Domain Name
http://support.microsoft.com/?id=257623


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



Ace Fekay

thank you very much for all that information!!!

I will try to explain my infrastructure, so you will understand why in each DC I have different DNS:

I have 4 offices conected (one of them is my ISP), in the same domain.
Every office has its own DC, and they also are DHCP and DNS.
Two of those offices have only one DC (DC1 and DC2), without any specific role. But my ISP has 2 DCs (DC4 and DC5) that are Schema owner and Domain role owner.  And the other office has 3 DC.
2 of those DCs (DC3 and DC6) on this last office have not roles, but the other one (servcentmb) has the PDC role, RID pool manager, and Infrastructure owner.

And for all that, every DC is using itself as first DNS, and then point to another one on the network.
Except by the DCs on my ISP (DC4 and DC5): they use itself as DNS, and they are not using another DNS on the network.

The configuration of DC6 is:

Configuración IP de Windows

Nombre del host . . . . . . . : svc4001
Sufijo DNS principal  . . . . : cpd.com
Tipo de nodo. . . . . . . . . : desconocido
Enrutamiento habilitado . . . : No
Proxy de WINS habilitado. . . : Sí
Lista de búsqueda sufijo DNS  : cpd.com

Adaptador Ethernet Conexión de área local 2:

Sufijo conexión específica DNS:
Descripción . . . . . . . . . : BCM5703 Gigabit Ethernet
Dirección física. . . . . . . : 00-0B-CD-6A-85-7F
DHCP habilitado . . . . . . . : No
Dirección IP. . . . . . . . . : 192.168.11.10
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . : 192.168.11.20
Servidores DNS. . . . . . . . : 192.168.11.10
192.168.10.86

So, I hope you can understand my english :)

Thank you again!!

Argie -- argie01 ------------------------------------------------------------------------ argie01's Profile: http://forums.techarena.in/members/79963.htm View this thread: http://forums.techarena.in/active-directory/1144018.htmhttp://forums.techarena.in

Show quote Hide quote Thanks, Argie for elaborating. And your English is fine. :-)

My concerns then are based on the multihomed DCs that may be causing the
problem. They are DC4 and DC5. Multihomed DCs can cause NUMEROUS problems.
It is well documented, and highly recommended to not multihome a DC. It
causes DNS registration conflicts, and also places a DC in multiple Sites,
which causes further issues.

If you can eliiminate the additional interfaces on those machine, that would
be good for starters.

I hope that helps.

Ace

Kerberos Tickets Renewal
Infrastructure FSMO role owner attibute not correct in root domain
What am I doing wrong? (Want to use Server 2003 R2 for Domain Cont
offline KB 810859
Roamin Profiles
Error message: During a logon attempt, the user's security context
servers loooking for group policy on dead server
How to Switch domains without having admin rights?
problem with NIS and AD user attributes
Problem After Defining Static RPC Port