Windows 2008 server Active directory problem

Hi, I'm not all an expert an I have a big problem on my Windows 2008 server. I will put all the errors together, hope someone can help me.

ACTIVE DIRECTORY DOMAIN SERVICES

/// information
Active Directory Domain Services has located a global catalog in the following site.
 
Global catalog:
\\FILESERVER.mydomain.com
Site:
Default-First-Site-Name

/// warning
Active Directory Domain Services attempted to communicate with the following global catalog and the attempts were unsuccessful.
 
Global catalog:
\\FILESERVER.mydomain.com
 
The operation in progress might be unable to continue. Active Directory Domain Services will use the domain controller locator to try to find an available global catalog server.
 
Additional Data
Error value:
1722 The RPC server is unavailable.

/// error
Active Directory Domain Services was unable to establish a connection with the global catalog.
 
Additional Data
Error value:
8430 The directory service encountered an internal failure.
Internal ID:
3200db0

DNS SERVER

/// error - dns event id 406

The DNS server could not create a User Datagram Protocol (UDP) socket. The event data is the error code. Restart the DNS server or reboot your computer.

/// error - dns event 408

The DNS server could not open socket for address ::1.
Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)
 
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.

/// error - dns event id 406

The DNS server could not create a User Datagram Protocol (UDP) socket. The event data is the error code. Restart the DNS server or reboot your computer.

/// error dns event id 408

The DNS server could not open socket for address 127.0.0.1.
Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)
 
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.

/// information

The DNS server has shut down.

DFS REPLICATION

/// error
The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
 
Additional Information:
Error: 160 (One or more arguments are not correct.)
proefAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Peter HutchisonSenior Network Systems SpecialistCommented:
Lets start with TCP/IP configuration:
How many Network cards are configured on the server? Only one should be configured, the rest disabled.
Is the network card configured with a static IP address? Do not use DHCP addresses on DC,DNS servers.
Is the network card configured with correct netmask and gateway?
Is the server's IP address listed first in the DNS address list? ISP DNS IP addresses should be configured in the Forward lookup list on DNS console.
Do you have a Reverse Lookup zone configured on DNS?
1
proefAuthor Commented:
Hi Peter, as I said I'm not an expert, so I will try to answer the questions:

ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : FILESERVER
   Primary Dns Suffix  . . . . . . . : mydomain.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : mydomain.com

Ethernet adapter Local Area Connection 4:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #4
   Physical Address. . . . . . . . . : 9C-8E-99-4C-3F-69
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #3
   Physical Address. . . . . . . . . : 9C-8E-99-4C-3F-68
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #2
   Physical Address. . . . . . . . . : 9C-8E-99-4C-3F-67
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter
   Physical Address. . . . . . . . . : 9C-8E-99-4C-3F-66
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.254.5(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.254.254
   NetBIOS over Tcpip. . . . . . . . : Enabled


When I use nslookup I get

Default Server: unknown
Address: 127.0.0.1

> fileserver.mydomain.com
Server: unknown
Address: 127.0.0.1

*** Unknown can't find fileserver.mydomain.com: no response from server
0
Peter HutchisonSenior Network Systems SpecialistCommented:
Hum, the ipconfig should have a line like this:

DNS Servers . . . . . 192.168.254.5

To fix it;
1. Open Control Panel, Network and Sharing Center
2. Click on Local Area Connection
3. Select Properties
4. Select  Internet Protocol Version 4 (TCP/IPv4)
5. Properties
6. Select 'Use the following DNS server addresses'
7. Enter 192.168.254.5
8. Click OK, OK, Close.
1
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

proefAuthor Commented:
thanks, I tried this solution and restarted the server. Still no internet connection and the same problems. Diagnose of internet connection: DNS Server isn't responding

When I look at the event log from the startup I see  the following

Critical
Task Scheduler service has encountered RPC initialization error in "RpcServerUseProtseq:ncacn_ip_tcp". Additional Data: Error Value: 1721.
0
Peter HutchisonSenior Network Systems SpecialistCommented:
Open Services.msc and check if DNS Server service is running.
Open Event Viewer, check the DNS specific DNS log for errors are warnings.
Open DNS console, check if the following dns records have registered:

Name Server (NS) for FILESERVER.mydomain.com
Host (A) for FILESERVER.mydomain.com
_Kerberos SRV record
_ldap SRV record
_gc SRV record
_kpasswd SRV record
which will occur in _msdcs, dc, domains, gc and pdc, _tcp folders.
 
You can recreate records using IPConfig /RegisterDNS command.

Also run DCDIAG /s:FILESERVER /test:dns to see if that brings up any errors.
0
proefAuthor Commented:
DNS Server is not started (should have been because Startup type Automatic)

/// Error 406
The DNS server could not create a User Datagram Protocol (UDP) socket. The event data is the error code. Restart the DNS server or reboot your computer.

/// Error 408
The DNS server could not open socket for address ::1.
Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)
 
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.

/// Error 406
The DNS server could not create a User Datagram Protocol (UDP) socket. The event data is the error code. Restart the DNS server or reboot your computer.

/// Error 408
The DNS server could not open socket for address 127.0.0.1.
Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)
 
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.

/// Information
The DNS server has shut down.

If I run dcdiag I get


Directory Server Diagnosis

Performing initial setup:

   [fileserver] LDAP connection failed with error 0,

   The operation completed successfully..
   An error occurred during DNS host lookup, that the program could not recover
   from.

   [fileserver] Unrecoverable LDAP Error 89:
0
proefAuthor Commented:
found a solution netsh winsock reset
Thank you very much for asking me the right questions
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Peter HutchisonSenior Network Systems SpecialistCommented:
Glad to help.
0
proefAuthor Commented:
I'm very happy that Peter Hutchison helped me. I don't want any points, but it's important that everybody knows the solution that worked in this case.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.