2008 r2 std dhcp sorunu

Merhaba

Tüm bilgisayarlarda gözlemlenen bir sorun değil ve dhcp üzerinde scope dolmadı ise makine bazlı bir soruna benziyor, hangi makinelerde bu sorunu yaşıyorsunuz acaba ? Yani işletim sistemi, bulunduğu kat, kullandığı switch vb bir ortak yanı var mı ?

Ayrıca wireshark gibi bir program kurup ipconfig /release , renew yaparak paketleri incelermisiniz dhcp paketlerini görebiliyormusunuz ? eksik olan paket hangisi

aşağıdaki gibi 4 paketi görebiliyormusunuz

Logları'da kontrol etmenizi öneririm.

hocam programı kurdum da nasıl kullanacağımı çözemedim

Merhaba,

Şu linki inceleyebilirsiniz.

http://wiki.wireshark.org/DHCP

Kolay gelsin.

bu program haricinde başka yöntem yokmu dhcp ile ilgili yeni pc bağladığımızdada ip almıyor otomatik

Merhaba,

Sorununuz konusunda neler yaptınız?Dhcp servislerinin durumu ne?Servisi restart etmeyi denediniz mi?Loglarda  bir uyarı varmı?

 Bazı makinalar alıyor bazıları almıyor. loglarda aşağıdakini buldum sadece . servislerden restart ettim makinayı restart ettim . 

 dhcp loglarında 

The DHCP service failed to see a directory server for authorization.

dns loglarında ise

The DNS server could not open socket for address 192.168.16.2 

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. 

For more information, see "DNS server log reference" in the online Help. 

The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 192.168.16.2.  The event data is the error code.  An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. 

Restart the DNS server or reboot the computer. 

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

Ortamda ip dağıtımı yapan bir cihaz aktif felen adildimi 2008 bu şekilde olur ise ip vermeyi kesiyor dhcp duruyor.Dhcp üzerinde sağ tıklatıp autorize kısmını tıklayıp denermisiniz tekrar.

Merhaba ,

DHCP rezervasyon  kullanıyormusunuz ? ortamda  sizden başka  dhcp varmı?, Modem yada  firewall'un DHCPsi açık olabilir kontrol edermisiniz rezervasyonlar da  sorun yaşayabilirsiniz.

başka dhcp dağıtan cihaz yok kontrolu yaptık. server uzeirnde birde şu log gorunuyor

Active Directory Domain Services could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory Domain Services from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources. 

Source domain controller: 

 xxxxxxx

Failing DNS host name: 

 a78761b7-8b80-4e47-ad31-f32c434e287b._msdcs.xxxx.local 

NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur.  To log all individual failure events, set the following diagnostics registry value to 1: 

Registry Path: 

HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client 

User Action: 

 1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498. 

 2) Confirm that the source domain controller is running Active Directory Domain Services and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>". 

 3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns 

  dcdiag /test:dns 

 4) Verify that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows: 

  dcdiag /test:dns 

 5) For further analysis of DNS error failures see KB 824449: 

    http://support.microsoft.com/?kbid=824449 

Additional Data 

Error value: 

 11004 The requested name is valid, but no data of the requested type was found.