Newsgroup: it.comp.os.win.win2000
Titolo: Active Directory in Windows 2003...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Scusate per il post lungo, spero di non essere OT in questo gruppo ma ho già
postato da altre parti e ancora non ottengo risposta.....
Dopo tre giorni di prove e tentativi mi convinco a scrivere su questo
newsgroup mosso più che altro da tristezza e rassegnazione. Non riesco ad
installare una Active Directory, e quindi un dominio NT, su Windows 2003
Server.
Ma andiamo per gradi, cominciando prima di tutto dalla mia "configurazione
rete", anche se chiamarla rete forse è eccessivo. Sto infatti installando
Windows 2003 su una partizione del mio pc per testarne le potenzialità.
Abbiamo quindi un Server, il mio Pentium 4 con Windows 2003 Server
Enterprise, e un client, un portatile con Windows XP Professional. La
connessione avviene per via di 1394 Net Adapter "Fireware".
Primo tentativo: installo Windows 2003 sulla partizione creata apposta per
lui. Ad installazione avvenuta lancio il "Configure Your Server Wizard" e
seleziono la configurazione di default prevista, si installano nell'ordine
il server DHCP, il DNS e l'Active Directory (da ora in poi AD per
abbreviare). Il dominio è "mylan.local". Si riavvia il computer. All'atto
del login dopo un paio di minuti da quando è comparsa la schermata
"Preparing network connection", prima ancora che possa quindi effettuare il
login (nella fase di caricamento dei servizi) compare un messaggio di errore
in merito ad un non meglio noto servizio che non si è avviato e vengo
invitato a consultare l'event viewer per saperne di più. Premo OK e dopo 10
minuti di orologio (su P4 2.4 GHz, 512 Mb di RAM, raid array, ecc, e non
faccio esagerazioni sui tempi!) finalmente mi fa fare il login. Inserisco
"Administrator" e la password, e vado a vedere in che stato stanno i vari
servizi. Intanto il wizard mi diceva che non era riuscito ad impostare un ip
statico all'adattore di rete, che non era riuscito ad "autorizzare" il DHCP
server e a, riporto fedelmente, "set up an application naming context in AD
on this domain controller for use by TAPI client applications"
Apro lo snap in di amministrazione del server DNS e sembra funzionare senza
problemi.
Se apro i tre snap in dell'Active Directory invece che mi dice che non c'è
nessun dominio e che non riesce a identificare il domain controller, che è
il server stesso.
Nello snap in del DHCP server trovo il servizio non in funzione e una
scritta che mi avverte di dover autorizzare il DHCP per l'Active Directory,
consigliandomi anche la procedura da seguire. La seguo (tasto destro ->
Authorize) e non cambia niente, se non che adesso al posto di Authorize ho
Unauthorize.... come se mi stesse prendendo in giro. Refresho più volte, non
cambia niente. Ci torno dopo un quarto d'ora (c'è scritto che
l'autorizzazione potrebbe richiedere tempo), ancora niente.
Mi dico "probabilmente ho sbagliato qualcosa", sebbene non abbia fatto altro
che seguire le più semplici funzionalità proposte dal wizard. Al che
*secondo tentativo*:
Spiano la partizione e reinstallo Windows 2003 (al quinto tentativo, vedendo
come andavano le cose, ho pensato bene fosse il caso di fare un'immagine
ghost di un'installazione pulita: ho ancora il disco di ghost nel floppy e
sarà al ventesimo tentativo, se non qualcosa di più...). Vado per passi.
Configuro TCP/IP con un IP statico (192.168.0.1) specificando come DNS il
server stesso (il DNS lo installo successivamente). Installo il DHCP server,
utilizzando come scope gli ip da 192.168.0.2 a 192.168.0.10. Il DHCP
funziona, al client viene assegnato senza problemi l'ip 192.168.0.2 e i due
pc cominciano a dialogare senza problemi.
Passo alla configurazione del DNS. Definisco la zona per "lan.local",
Primary Zone, ecc. Forwarder sarà il dns di Wind, ISP che uso per la
connessione ad internet. Il client risolve senza problemi gli indirizzi
locali (suo e del server) e quelli internet. Il DNS sembra funzionare.
Configuro il routing: il client riesce a navigare quando il server è
connesso ad internet.
Riprovo a resinstallare l'Active Directory: stessi risultati di prima, il
DHCP non funziona più perchè è da autorizzare e non c'è modo di farlo (lo
fai, ma non si autorizza), ci mette 15 minuti prima che ti fa fare il logon,
errore all'inizio. Vado a vedere l'Event Viewer del DNS server ci sono i
seguenti warning ed errors:
Event Type:       Warning
Event Source:   DNS
Event Category: None
Event ID:           4013
Date:                28/06/2003
Time:                23.37.57
User:                N/A
Computer:         DANIELENET
Description:
The DNS server was unable to open the Active Directory.  This DNS server is
configured to use directory service information and can not operate without
access to the directory.  The DNS server will wait for the directory to
start.  If the DNS server is started but the appropriate event has not been
logged, then the DNS server is still waiting for the directory to start.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp
.
Data:
0000: 2a 23 00 00               *#..
Event Type:       Error
Event Source:   DNS
Event Category: None
Event ID:           4000
Date:                28/06/2003
Time:                23.37.57
User:                N/A
Computer:         DANIELENET
Description:
The DNS server was unable to open Active Directory.  This DNS server is
configured to obtain and use information from the directory for this zone
and is unable to load the zone without it.  Check that the Active Directory
is functioning properly and reload the zone. The event data is the error
code.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp
.
Data:
0000: 2a 23 00 00               *#..
Seguono alcuni tentativi. Cerco in internet, mi imbatto in thread su usenet
di persone che hanno avuto i miei stessi problemi se non simili con Windows
2000 Server (qualcuno anche con Windows 2003) ma con mio rammarico constato
che la maggior parte dei thread si perdono nel nulla e che non riesco ad
attingere alcuna soluzione al problema che mi affligge. La documentazione in
rete è dispersiva, il sito Microsoft non parla di niente se non di usare il
wizard e di seguire 2-3 passi, che poi sono quelli del wizard. Non una
configurazione manuale: al me il wizard non va! Da quello che ho potuto
capire è un problema di DNS, o meglio, di integrazione DNS/Active
Directory.... forse il DNS configurato male (lo configura automaticamente il
wizard, come si configura manualmente?)
Non vi voglio angustiare con i miei n tentativi, mi limito solo a fornirvi
altre informazioni che penso possano essere utile per capire qual è la
problematica.
In questa condizione, l'avere un'active directory che di fatto non funziona
(il client vede il dominio in rete ma non si puo' joinare perchè non riesce
a determinare il domain controller, da cui penso sia un problema di DNS),
succedono anche queste cose "bizzarre":
Se provo ad aprire i tre snap in di configurazione dell'Active Directory mi
dice che non non c'è alcun dominio o che non riesce a capire dove è (il
messaggio non è proprio questo, ma il significato è pressochè lo stesso).
Qualche volta invece gli snap in si aprono e ci sono gli oggetti dell'AD. In
questo caso, per esempio, se provo ad aggiungere un utente alla cartella
User ottengo il messaggio di errore che riporto fedelmente: "Windows cannot
verify that the user name is unique bacause the following error occurred
while contacting the global catalog; the service is not operational"
Nella configurazione DNS, se provo a creare una "default application
directory partition" (a tentativi, tanto per fare qualcosa) mi dice "would
you like to create a single partition that stores DNS zone data and
replicates that data to all DNS server in the AD domain (null)?" Confermo
(anche se mi chiedo per cosa sta quel null.... che forse non trova l'AD o il
DC?) ed ho "The partition to replicate zone data to all DNS servers in the
AD domain was not created. The data is invalid"
Se provo a "passare" il "tipo di DNS" (concedetemi la terminologia spiccia,
è mezzanotte inoltrata...) da Primary ad AD-Integrated ottengo il seguente
messaggio di errore: "The data on the primary zone failed to set. The AD
service is not avaible" e ancora "the specified directory partition does not
exists". Se provo cancellare la forward zone lookup e a ricrearla come AD-
integrated mi dice che non ho privilegi di "enterprise admin". Ma come sono
admin del pc? Aggiungo Administrator al gruppo di enterprise admin e non
cambia niente.
Veramente non so più dove sbattere la testa, ora stacco che sto abbastanza
fuso. Spero che mi rispondiate e che mi possiate aiutare. Soprattutto spero
che qualcuno mi dica cosa verificare manualmente per essere sicuri che AD
funzioni e che il DNS sia configurato correttamente.
Vi ringrazio anticipatamente in ogni modo,
Aggiungo, sperando che possano servire a qualcosa, i log di netdiag, nella
versione normale che verbose, dopo aver fissato alcuni problemi sul DNS con
l'opzione /fix della stessa utility
A quanto pare sembra che il problema sia proprio sull'AD e in particolare
nel localizzare il DC. Ma come fare per cercare di sistemare il problema?
L'AD la installa il Wizard, se apro gli snap in, dopo aver fixato i problemi
sul DNS (il DNS viene configurato anch'esso dal Wizard) io vedo il dominio e
il DC, che è lo stesso pc..... Sinceramente non capisco....
Netdiag LOG ===========================
..................................
    Computer Name: DANIELENET
    DNS Host Name: danielenet.lan.local
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
    List of installed hotfixes :
        Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
    Adapter : 1394 Connection
        Netcard queries test . . . : Passed
        Host Name. . . . . . . . . : danielenet
        IP Address . . . . . . . . : 192.168.0.1
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.0.1
        Dns Servers. . . . . . . . : 192.168.0.1
        AutoConfiguration results. . . . . . : Passed
        Default gateway test . . . : Passed
        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.
            No remote names have been found.
        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Failed
    [WARNING] Ths system volume has not been completely replicated to the
local machine. This machine is not working properly as a DC.
NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}
    1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
    PASS - All the DNS entries for DC are registered on DNS server
'192.168.0.1'.
Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}
    The redir is bound to 1 NetBt transport.
    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}
    The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Failed
        [FATAL] Cannot find DC in domain 'LAN'. [ERROR_NO_SUCH_DOMAIN]
DC list test . . . . . . . . . . . : Failed
        'LAN': Cannot find DC to get DC list from [test skipped].
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Skipped
        'LAN': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
    Cannot find DC to run LDAP tests on. The error occurred was: The
specified domain either does not exist or could not be contacted.
        [WARNING] Cannot find DC in domain 'LAN'. [ERROR_NO_SUCH_DOMAIN]
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
    No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
    Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
Netdiag Verbose LOG =====================
    Gathering IPX configuration information.
    Querying status of the Netcard drivers... Passed
    Testing Domain membership... Passed
    Gathering NetBT configuration information.
    Testing for autoconfiguration... Passed
    Testing IP loopback ping... Passed
    Testing default gateways... Passed
    Enumerating local and remote NetBT name cache... Passed
    Testing the WINS server
        1394 Connection
            There is no primary WINS server defined for this adapter.
            There is no secondary WINS server defined for this adapter.
    Gathering Winsock information.
    Testing DNS
    PASS - All the DNS entries for DC are registered on DNS server
'192.168.0.1'.
    Testing redirector and browser... Passed
    Testing DC discovery.
        Looking for a DC
    Gathering the list of Domain Controllers for domain 'LAN'
    Testing trust relationships... Skipped
    Testing Kerberos authentication... Failed
    Testing LDAP servers in Domain LAN ...
    Gathering routing information
    Gathering network statistics information.
    Gathering configuration of bindings.
    Gathering RAS connection information
    Gathering Modem information
    Gathering Netware information
    Gathering IP Security information
    Tests complete.
    Computer Name: DANIELENET
    DNS Host Name: danielenet.lan.local
    DNS Domain Name: lan.local
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
    Hotfixes :
        Installed?      Name
           Yes          Q147222
Netcard queries test . . . . . . . : Passed
    Information of Netcard drivers:
    ------------------------------------------------------------------------
- ---
    Description: 1394 Net Adapter
    Device: \DEVICE\{75F800B9-BA73-423D-BCBB-CED65CCAB943}
    Media State:                     Connected
    Device State:                    Connected
    Connect Time:                    00:17:40
    Media Speed:                     400 Mbps
    Packets Sent:                    435
    Bytes Sent (Optional):           0
    Packets Received:                28
    Directed Pkts Recd (Optional):   451
    Bytes Received (Optional):       0
    Directed Bytes Recd (Optional):  0
    ------------------------------------------------------------------------
- ---
    [PASS] - At least one netcard is in the 'Connected' state.
Per interface results:
    Adapter : 1394 Connection
        Adapter ID . . . . . . . . : {75F800B9-BA73-423D-BCBB-CED65CCAB943}
        Netcard queries test . . . : Passed
        Adapter type . . . . . . . : Unknown
        Host Name. . . . . . . . . : danielenet
        Description. . . . . . . . : NIC1394
        Physical Address . . . . . : 12-db-3d-c4-ea-55
        Dhcp Enabled . . . . . . . : No
        DHCP ClassID . . . . . . . :
        Autoconfiguration Enabled. : Yes
        IP Address . . . . . . . . : 192.168.0.1
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.0.1
        Dns Servers. . . . . . . . : 192.168.0.1
        IpConfig results . . . . . : Passed
        AutoConfiguration results. . . . . . : Passed
            AutoConfiguration is not in use.
        Default gateway test . . . : Passed
            Pinging gateway 192.168.0.1 - reachable
            At least one gateway reachable for this adapter.
        NetBT name test. . . . . . : Passed
            NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}
            DANIELENET     <00>  UNIQUE      REGISTERED
            LAN            <00>  GROUP       REGISTERED
            LAN            <1C>  GROUP       REGISTERED
            DANIELENET     <20>  UNIQUE      REGISTERED
            LAN            <1B>  UNIQUE      REGISTERED
            LAN            <1E>  GROUP       REGISTERED
            LAN            <1D>  UNIQUE      REGISTERED
            ..__MSBROWSE__.<01>  GROUP       REGISTERED
        [WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.
            NetBios Resolution : via DHCP
            No remote names have been found.
        WINS service test. . . . . : Skipped
            There is no primary WINS server defined for this adapter.
            There is no secondary WINS server defined for this adapter.
            There are no WINS servers configured for this interface.
        IPX test : IPX is not installed on this machine.
Global results:
IP General configuration
    LMHOSTS Enabled. . . . . . . . : Yes
    DNS for WINS resolution. . . . : Enabled
    Node Type. . . . . . . . . . . : Broadcast
    NBT Scope ID . . . . . . . . . :
    Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled . . . . . . : No
    DNS resolution for NETBIOS . . : No
Domain membership test . . . . . . : Failed
    [WARNING] Ths system volume has not been completely replicated to the
local machine. This machine is not working properly as a DC.
    Machine is a . . . . . . . . . : Primary Domain Controller Emulator
    Netbios Domain name. . . . . . : LAN
    Dns domain name. . . . . . . . : lan.local
    Dns forest name. . . . . . . . : lan.local
    Domain Guid. . . . . . . . . . : {0B924573-EE37-41F4-8515-54050C4196BD}
    Domain Sid . . . . . . . . . . : S-1-5-21-730196737-481394977-3174805795
    Logon User . . . . . . . . . . : Administrator
    Logon Domain . . . . . . . . . : LAN
NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}
    1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
    PASS - you have at least one non-autoconfigured IP address
IP loopback ping test. . . . . . . : Passed
    PASS - pinging IP loopback address was successful.
    Your IP stack is most probably OK.
Default gateway test . . . . . . . : Passed
    PASS - you have at least one reachable gateway.
NetBT name test. . . . . . . . . . : Passed
   No NetBT scope defined
    [WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
    The number of protocols which have been reported : 10
        Description: MSAFD Tcpip [TCP/IP]
            Provider Version   :2
            Max message size  : Stream Oriented
        Description: MSAFD Tcpip [UDP/IP]
            Provider Version   :2
        Description: RSVP UDP Service Provider
            Provider Version   :6
        Description: RSVP TCP Service Provider
            Provider Version   :6
            Max message size  : Stream Oriented
        Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}] SEQPACKET 0
            Provider Version   :2
        Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}] DATAGRAM 0
            Provider Version   :2
        Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BC3C4E92-66F8-4AB3-839E-F6D316FD3D9A}] SEQPACKET 1
            Provider Version   :2
        Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BC3C4E92-66F8-4AB3-839E-F6D316FD3D9A}] DATAGRAM 1
            Provider Version   :2
        Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{4061D22B-26CF-406C-8C92-7EC2B391C124}] SEQPACKET 2
            Provider Version   :2
        Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{4061D22B-26CF-406C-8C92-7EC2B391C124}] DATAGRAM 2
            Provider Version   :2
    Max UDP size : 65507 bytes
DNS test . . . . . . . . . . . . . : Passed
      Interface {75F800B9-BA73-423D-BCBB-CED65CCAB943}
        DNS Domain:
        DNS Servers: 192.168.0.1
        IP Address:         Expected registration with PDN (primary DNS
domain name):
          Hostname: danielenet.lan.local.
          Authoritative zone: lan.local.
          Primary DNS server: danielenet.lan.local 192.168.0.1
          Authoritative NS:192.168.0.1
Check the DNS registration for DCs entries on DNS server '192.168.0.1'
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
The Record is correct on DNS server '192.168.0.1'.
    PASS - All the DNS entries for DC are registered on DNS server
'192.168.0.1'.
Redir and Browser test . . . . . . : Passed
    List of transports currently bound to the Redir
        NetbiosSmb
        NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}
    The redir is bound to 1 NetBt transport.
    List of transports currently bound to the browser
        NetBT_Tcpip_{75F800B9-BA73-423D-BCBB-CED65CCAB943}
    The browser is bound to 1 NetBt transport.
    Mailslot test for LAN* passed.
DC discovery test. . . . . . . . . : Failed
    Find DC in domain 'LAN':
        [FATAL] Cannot find DC in domain 'LAN'. [ERROR_NO_SUCH_DOMAIN]
DC list test . . . . . . . . . . . : Failed
        'LAN': Cannot find DC to get DC list from [test skipped].
    List of DCs in Domain 'LAN':
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Skipped
        'LAN': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
    Cannot find DC to run LDAP tests on. The error occurred was: The
specified domain either does not exist or could not be contacted.
    Find DC in domain 'LAN':
        [WARNING] Cannot find DC in domain 'LAN'. [ERROR_NO_SUCH_DOMAIN]
Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination        Netmask           Gateway         Interface
Metric
         0.0.0.0           0.0.0.0       192.168.0.1       192.168.0.1
10
       127.0.0.0         255.0.0.0         127.0.0.1         127.0.0.1
1
     192.168.0.0     255.255.255.0       192.168.0.1       192.168.0.1
10
     192.168.0.1   255.255.255.255         127.0.0.1         127.0.0.1
10
   192.168.0.255   255.255.255.255       192.168.0.1       192.168.0.1
10
       224.0.0.0         240.0.0.0       192.168.0.1       192.168.0.1
10
 255.255.255.255   255.255.255.255       192.168.0.1       192.168.0.1
1
No persistent route entries.
Netstat information test . . . . . : Passed
    Interface Statistics
                                    Received             Sent
    Unicast Packets                   772754           770904
    Non-unicast packets                  311              456
    Discards                               0                0
    Errors                                 0                0
    Unknown protocols                      0           458284
    Interface index         =  1
    Description             =  MS TCP Loopback interface
    Type                    =  24
    MTU                     =  1520
    Speed                   =  10000000
    Physical Address        =  00-00-00-00-00-00
    Administrative Status   =  1
    Operational Status      =  1
    Last Changed            =  
3123691478
    Output Queue Length     =  0
    Interface index         =  65539
    Description             =  NIC1394
    Type                    =  144
    MTU                     =  1504
    Speed                   =  400000000
    Physical Address        =  12-DB-3D-C4-EA-55
    Administrative Status   =  1
    Operational Status      =  1
    Last Changed            =  
3123691480
    Output Queue Length     =  0
    Active Connections
  Proto Local Address         Foreign Address
State
    TCP   danielenet:domain     danielenet.lan.local:24764
LISTENING
    TCP   danielenet:epmap      danielenet.lan.local:63542
LISTENING
    TCP   danielenet:ldap       danielenet.lan.local:55324
LISTENING
    TCP   danielenet:microsoft-ds  danielenet.lan.local:53442
LISTENING
    TCP   danielenet:593        danielenet.lan.local:43054
LISTENING
    TCP   danielenet:ldaps      danielenet.lan.local:30972
LISTENING
    TCP   danielenet:1025       danielenet.lan.local:28902
LISTENING
    TCP   danielenet:1026       danielenet.lan.local:10474
LISTENING
    TCP   danielenet:1028       danielenet.lan.local:37085
LISTENING
    TCP   danielenet:1038       danielenet.lan.local:59639
LISTENING
    TCP   danielenet:1106       danielenet.lan.local:34
LISTENING
    TCP   danielenet:3268       danielenet.lan.local:43230
LISTENING
    TCP   danielenet:3269       danielenet.lan.local:51365
LISTENING
    TCP   danielenet:ldap       danielenet.lan.local:1033
ESTABLISHED
    TCP   danielenet:ldap       danielenet.lan.local:1034
ESTABLISHED
    TCP   danielenet:ldap       danielenet.lan.local:1035
ESTABLISHED
    TCP   danielenet:ldap       danielenet.lan.local:1529
TIME_WAIT
    TCP   danielenet:1033       danielenet.lan.local:ldap
ESTABLISHED
    TCP   danielenet:1034       danielenet.lan.local:ldap
ESTABLISHED
    TCP   danielenet:1035       danielenet.lan.local:ldap
ESTABLISHED
    TCP   danielenet:1530       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:1534       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:1535       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:1536       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:1537       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:1541       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:1542       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:1568       danielenet.lan.local:ldap
TIME_WAIT
    TCP   danielenet:epmap      danielenet.lan.local:1234
ESTABLISHED
    TCP   danielenet:epmap      danielenet.lan.local:1569
ESTABLISHED
    TCP   danielenet:netbios-ssn  danielenet.lan.local:24757
LISTENING
    TCP   danielenet:ldap       danielenet.lan.local:1465
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1466
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1467
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1468
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1469
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1470
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1471
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1472
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1473
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1474
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1475
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1476
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1477
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1478
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1479
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1480
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1481
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1482
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1483
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1484
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1485
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1486
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1487
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1488
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1489
TIME_WAIT
    TCP   danielenet:ldap       danielenet.lan.local:1490
TIME_WAIT
    TCP   danielenet:1234       danielenet.lan.local:epmap
ESTABLISHED
    TCP   danielenet:1492       danielenet.lan.local:epmap
TIME_WAIT
    TCP   danielenet:1493       danielenet.lan.local:1025
TIME_WAIT
    TCP   danielenet:1514       danielenet.lan.local:1025
TIME_WAIT
    TCP   danielenet:1521       danielenet.lan.local:epmap
TIME_WAIT
    TCP   danielenet:1522       danielenet.lan.local:1025
TIME_WAIT
    TCP   danielenet:1531       danielenet.lan.local:1025
TIME_WAIT
    TCP   danielenet:1538       danielenet.lan.local:1025
TIME_WAIT
    TCP   danielenet:1561       danielenet.lan.local:1025
TIME_WAIT
    TCP   danielenet:1569       danielenet.lan.local:epmap
ESTABLISHED
    TCP   danielenet:1570       danielenet.lan.local:1025
TIME_WAIT
    TCP   danielenet:1578       danielenet.lan.local:1025
TIME_WAIT
    UDP  danielenet:microsoft-ds  *:*
    UDP  danielenet:isakmp     *:*
    UDP  danielenet:1030       *:*
    UDP  danielenet:1032       *:*
    UDP  danielenet:1037       *:*
    UDP  danielenet:1039       *:*
    UDP  danielenet:1041       *:*
    UDP  danielenet:1044       *:*
    UDP  danielenet:1045       *:*
    UDP  danielenet:1047       *:*
    UDP  danielenet:1119       *:*
    UDP  danielenet:4500       *:*
    UDP  danielenet:domain     *:*
    UDP  danielenet:ntp        *:*
    UDP  danielenet:1036       *:*
    UDP  danielenet:1577       *:*
    UDP  danielenet:domain     *:*
    UDP  danielenet:ntp        *:*
    UDP  danielenet:netbios-ns  *:*
    UDP  danielenet:netbios-dgm  *:*
    UDP  danielenet:389        *:*
    IP  Statistics
    Packets Received              =   5.180
    Received Header Errors        =   0
    Received Address Errors       =   0
    Datagrams Forwarded           =   0
    Unknown Protocols Received    =   0
    Received Packets Discarded    =   0
    Received Packets Delivered    =   5.180
    Output Requests               =   5.179
    Routing Discards              =   0
    Discarded Output Packets      =   0
    Output Packet No Route        =   0
    Reassembly  Required          =   0
    Reassembly Successful         =   0
    Reassembly Failures           =   0
    Datagrams successfully fragmented  =   0
    Datagrams failing fragmentation    =   0
    Fragments Created                  =   0
    Forwarding                        =    2
    Default TTL                       =    128
    Reassembly  timeout               =    60
    TCP Statistics
    Active Opens               =    234
    Passive Opens              =    234
    Failed Connection Attempts =    0
    Reset Connections          =    4
    Current Connections        =    10
    Received Segments          =    4.042
    Segment Sent               =    4.042
    Segment Retransmitted      =    0
    Retransmission Timeout Algorithm  =   vanj
    Minimum Retransmission Timeout  = 300
    Maximum Retransmission Timeout  = 120.000
    Maximum Number of Connections   = -1
    UDP Statistics
    Datagrams Received    =   1.000
    No Ports              =   67
    Receive Errors        =   0
    Datagrams Sent        =   1.003
    ICMP Statistics
                              Received           Sent
    Messages                       134            134
    Errors                           0              0
    Destination  Unreachable         4              4
    Time    Exceeded                 0              0
    Parameter Problems               0              0
    Source Quenchs                   0              0
    Redirects                        0              0
    Echos                           71             71
    Echo Replies                    59             59
    Timestamps                       0              0
    Timestamp Replies                0              0
    Address Masks                    0              0
    Address Mask Replies             0              0
Bindings test. . . . . . . . . . . : Passed
    Component Name : NDIS Usermode I/O Protocol
    Bind Name: Ndisuio
    Binding Paths:
    Component Name : Point to Point Protocol Over Ethernet
    Bind Name: RasPppoe
    Binding Paths:
    Component Name : Point to Point Tunneling Protocol
    Bind Name: mspptp
    Binding Paths:
    Component Name : Layer 2 Tunneling Protocol
    Bind Name: msl2tp
    Binding Paths:
    Component Name : Remote Access NDIS WAN Driver
    Bind Name: NdisWan
    Binding Paths:
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: Direct Parallel
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (PPPOE)
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (PPTP)
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (L2TP)
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanasync
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: RAS Async Adapter
    Component Name : Message-oriented TCP/IP Protocol (SMB session)
    Bind Name: NetbiosSmb
    Binding Paths:
    Component Name : WINS Client(TCP/IP) Protocol
    Bind Name: NetBT
    Binding Paths:
        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis1394
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: 1394 Net Adapter
        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)
    Component Name : Internet Protocol (TCP/IP)
    Bind Name: Tcpip
    Binding Paths:
        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis1394
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: 1394 Net Adapter
        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)
    Component Name : Client for Microsoft Networks
    Bind Name: LanmanWorkstation
    Binding Paths:
        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: Client for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)
        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis1394
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: 1394 Net Adapter
        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)
    Component Name : WebClient
    Bind Name: WebClient
    Binding Paths:
    Component Name : Wireless Configuration
    Bind Name: wzcsvc
    Binding Paths:
    Component Name : Network Load Balancing
    Bind Name: Wlbs
    Binding Paths:
    Component Name : Steelhead
    Bind Name: RemoteAccess
    Binding Paths:
    Component Name : Dial-Up Server
    Bind Name: msrassrv
    Binding Paths:
    Component Name : Remote Access Connection Manager
    Bind Name: RasMan
    Binding Paths:
    Component Name : Dial-Up Client
    Bind Name: msrascli
    Binding Paths:
    Component Name : File and Printer Sharing for Microsoft Networks
    Bind Name: LanmanServer
    Binding Paths:
        Owner of the binding path : File and Printer Sharing for Microsoft
Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)
        Owner of the binding path : File and Printer Sharing for Microsoft
Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis1394
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: 1394 Net Adapter
        Owner of the binding path : File and Printer Sharing for Microsoft
Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)
    Component Name : NetBIOS Interface
    Bind Name: NetBIOS
    Binding Paths:
        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis1394
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: 1394 Net Adapter
        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)
    Component Name : Generic Packet Classifier
    Bind Name: Gpc
    Binding Paths:
    Component Name : Application Layer Gateway
    Bind Name: ALG
    Binding Paths:
    Component Name : WAN Miniport (IP)
    Bind Name: NdisWanIp
    Binding Paths:
    Component Name : Direct Parallel
    Bind Name: {B750377D-0879-440C-92AB-BC88EE728206}
    Binding Paths:
    Component Name : WAN Miniport (PPPOE)
    Bind Name: {DDC1135E-8354-4B2D-9AF3-66896DDB1F7D}
    Binding Paths:
    Component Name : WAN Miniport (PPTP)
    Bind Name: {EF59FC9F-E7B9-430D-8553-38E14ABCCCF1}
    Binding Paths:
    Component Name : WAN Miniport (L2TP)
    Bind Name: {853822EF-B16C-45AC-96E4-59A7D1D0879B}
    Binding Paths:
    Component Name : RAS Async Adapter
    Bind Name: {4B7A7E66-B549-4D58-9D78-EF13CDEC5445}
    Binding Paths:
    Component Name : 1394 Net Adapter
    Bind Name: {75F800B9-BA73-423D-BCBB-CED65CCAB943}
    Binding Paths:
WAN configuration test . . . . . . : Skipped
    No active remote access connections.
Modem diagnostics test . . . . . . : Passed
    Name . . . . . . . . . . . . . : Standard Modem
        DeviceID . . . . . . . . . : 0
        Port . . . . . . . . . . . : COM1
        Negotiated Speed . . . . . : 0
        Compression. . . . . . . . : Off
        Error control. . . . . . . : Off
        Forced error control . . . : Off
        Cellular . . . . . . . . . : Off
        Flowcontrol hard . . . . . : Off
        Flowcontrol soft . . . . . : Off
        CCITT override . . . . . . : Off
        Speed adjust . . . . . . . : Off
        Tone dial. . . . . . . . . : Off
        Blind dial . . . . . . . . : Off
        V23 override . . . . . . . : Off
IP Security test . . . . . . . . . : Skipped
    Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
Daniele.
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
iQA/AwUBPv7O1Vv68KkERaiGEQKGiwCgrw76WE1P3+ouc8A3yrcmPl7cZr4An2kF
bOffThK/koj4Hy6HBuN8dQgC
=c+bP
-----END PGP SIGNATURE-----

 2003 Server.
Scusa, ma perché ti ostini ad installare DNS e DHCP *prima* di Active
Directory, quando sono servizi che si appoggiano *sopra* AD ?
La sequenza corretta di installazione è: installi Windows, assegni un
indirizzo IP *statico* alla scheda di rete, installi AD (e qui ci pensa
l'installazione a metterti su il DNS) e *poi*, dopo che è tutto a posto,
installi il DHCP, se è necessario. Il tutto su un server pulito dove non hai
ancora installato nient'altro. È molto importante il fatto di *non*
installare il DNS prima di AD, in quanto così facendo ci pensa
l'installazione di AD a creare le giuste zone e i giusti record nel server,
oltre a creare per default zone integrate nella directory.
Un'altra cosa: per creare il dominio, lascia perdere tutti quegli stupidi
wizard. Apri un prompt dei comandi e scrivi "DCPROMO".
Massimo

 wizard. Apri un prompt dei comandi e scrivi "DCPROMO".
Ti ringrazio per la risposta.
Tra gli n tentativi ho anche installato solo AD, che, come tu giustamente mi
fai notare, si carica il DNS. I log che ho postato riguardano questa
situazione, e come tu stesso puoi vedere il DNS non era impostato affatto
bene (mancano le impostazioni per l'AD), ho dovuto fixare con "netdiag /fix"
altrimenti nemmeno risolveva l'indirizzo del DC all'apertura degli snap in
dell'AD. digitando "dcpromo" mi si apre il wizard per l'installazione
dell'AD di cui ho già esposto.
Faccio anche notare (visto che forse sono stato poco chiaro) che il DNS
installato e configurato dal wizard (dcpromo) dell'AD non è un AD-Integrated
ma un "Primary" e che non riesco in alcun modo a portarlo a "AD-Integrated"
(errori tipo "non sei un enterprise admin", oppure "il dominio non esiste" o
ancora "impossibile trovare il DC".
Daniele.
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
iQA/AwUBPv729Fv68KkERaiGEQLg3ACgorXBrBjSAqHrh0Ng1qpX2ZouzGIAoNfJ
QHrn76SlTxbDj8h1q+eMlkc3
=9IjX
-----END PGP SIGNATURE-----

 Directory, quando sono servizi che si appoggiano *sopra* AD ?
Da quando in qua il DNS si appoggia su Active Directory? Direi anzi che e'
AD che fa largo uso del DNS tanto e' vero che _SE_ il DNS non e' installato
(o comunque raggiungibile) lanciando dcpromo te l'ho fa installare.
Ciao
Federico

 ancora "impossibile trovare il DC".
Una domanda: stai lavorando con la versione definitiva e non con una beta,
vero ?
Massimo

 (o comunque raggiungibile) lanciando dcpromo te l'ho fa installare.
In realtà il rapporto tra DNS e AD è un po' più intricato di così (le zone
DNS possono essere memorizzate nella directory, e la gestione dei permessi
si basa sull'autenticazione di Windows). In questo caso comunque mi sono
espresso abbastanza male, intendevo dire che se si esegue DCPROMO e si fa
installare a lui il DNS, si ha la certezza che questo venga installato e
configurato in maniera ottimale per supportare AD, e questo può rendere le
cose più semplici in una situazione dove c'è un solo server e chi lo
installa non sa che pesci prendere :-)
Massimo