Re: Preparing Network Connections... forever

From the new domain controller:

C:\Temp>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Client-1DC
Primary Dns Suffix . . . . . . . : client-1.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : client-1.local

Ethernet adapter VMnet3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0C-29-0E-AA-2B
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.6.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.6.1
DNS Servers . . . . . . . . . . . : 127.0.0.1

C:\Temp>


And from the first DC in the forest:

C:\Temp>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DEVDC
Primary Dns Suffix . . . . . . . : vmdev.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : vmdev.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-C8-72-18
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.5.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.5.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled

The differences are:

1- The NIC emulation in VMWare not the same. In the new DC, I told VMware to emulate an Intel E1000
card while the other guest is using the default NIC (AMD)

2- After it had been created (months ago), I turned NetBIOS off (TCP/IP advanced properties) on the
DC for the forest original domain (vmdev.local).

Another tidbit. At the time of the original post, the new domain (client-1.local) DC was not
configured as a Global Catalog in "AD Sites and Services". Since then, I enabled Client-1DC as a GC
and waited an hour to make sure the replication occurred after which, I restarted "Client-1DC".

As usual, I got the same "Preparing network Connections...' screen for 5 minutes and the
"Replication Services" event log contained the same error as originally posted.

I do not know whether it is significant but the System event log also contain these warning events:

=================
The Security System detected an authentication error for the server ldap/Client-1DC.client-1.local.
The failure code from authentication protocol Kerberos was "There are currently no logon servers
available to service the logon request.
(0xc000005e)".
=================
The Security System detected an authentication error for the server LDAP/CLIENT-1DC. The failure
code from authentication protocol Kerberos was "There are currently no logon servers available to
service the logon request.
(0xc000005e)".
=================

I have no other anomalous event in any of the other event logs. The other weird thing is that from
"Client-1DC.client-1.local", I can logon using the Administrator account of the 'vmdev.local"
domain. But from "devdc.vmdev.local", when I try to logon using Administrator of "client-1.local", I
get a message indicating that the local policy do not allow me to logon interactively.

Gaetan.
.

Relevant Pages

  • Re: Preparing Network Connections... forever
    ... Windows IP Configuration ... "Replication Services" event log contained the same error as originally posted. ... The Security System detected an authentication error for the server ldap/Client-1DC.client-1.local. ... The failure code from authentication protocol Kerberos was "There are currently no logon servers ...
    (microsoft.public.windows.server.active_directory)
  • Re: Preparing Network Connections... forever
    ... Windows IP Configuration ... "Replication Services" event log contained the same error as originally posted. ... The Security System detected an authentication error for the server ldap/Client-1DC.client-1.local. ... The failure code from authentication protocol Kerberos was "There are currently no logon servers ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange problem after server crash
    ... get rid of the second DNS entry on the server. ... Are there any other errors in the event log? ... > configuration information. ... > Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server 2008 Folder Redirection
    ... Directory Server Diagnosis ... (Event String (event log = System) ... "Meinolf Weber" wrote: ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.general)
  • Re: Server 2008 Folder Redirection
    ... Home Server = server ... (Event String (event log = System) ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.general)