{"id":268,"title":"Domain\u2019e join olma i\u015flemi s\u0131ras\u0131nda ortaya \u00e7\u0131kan sorunu \u00e7\u00f6zmek i\u00e7in yap\u0131lacak i\u015flemler","content":"<p>Domain\u2019e join olmadaki sorunu \u00e7\u00f6zmek i\u00e7in \u015fu ad\u0131mlar\u0131 takip edelim:<\/p><ol><li>\u0130lk olarak ping testi yapal\u0131m:<\/li><\/ol><ul><li>\u0130lk olarak ping testi yapal\u0131m:<\/li><\/ul><p>ping domain.com<\/p><p>ipconfig \/all<\/p><p>2. DNS \u00e7\u00f6z\u00fcmlemesini kontrol edelim:<br><br>nslookup domain.com<\/p><p>3. Domain Controller\u2019a direkt ba\u011flant\u0131y\u0131 test edelim:<br><br>nltest \/dsgetdc:domain.com<\/p><p>4. A\u011f kimlik bilgilerini temizleyelim:<br><br>klist purge<\/p><p>5. Alternatif join komutu deneyelim:<br><br>powershell Add-Computer -DomainName domain.com -Credential (Get-Credential) -Restart -Force<\/p><p>6. Bilgisayar ad\u0131n\u0131n DNS standartlar\u0131na uygun oldu\u011fundan emin olal\u0131m:<br>hostname<\/p><p>7.Zaman\u0131 kontrol edin:<\/p><p>w32tm \/query \/status<\/p><p>G\u00fcvenlik duvar\u0131 kontrolleri:<\/p><p>netsh advfirewall show allprofiles<\/p><ul><li>Gerekirse domain join i\u00e7in gereken portlar\u0131 a\u00e7\u0131n:<br>\u2014 TCP\/UDP 53 (DNS)<br>\u2014 TCP\/UDP 88 (Kerberos)<br>\u2014 TCP 389 (LDAP)<br>\u2014 TCP\/UDP 445 (SMB)<\/li><li>Gerekirse domain join i\u00e7in gereken portlar\u0131 a\u00e7\u0131n:<br>\u2014 TCP\/UDP 53 (DNS)<br>\u2014 TCP\/UDP 88 (Kerberos)<br>\u2014 TCP 389 (LDAP)<br>\u2014 TCP\/UDP 445 (SMB)<\/li><\/ul><p>PowerShell ile iligli portlar\u0131 a\u00e7mak i\u00e7in a\u015fa\u011f\u0131daki komutlar\u0131 kullanabilirsiniz:<\/p><p># DNS (TCP ve UDP port 53)<br>New-NetFirewallRule -DisplayName \"Allow DNS TCP\" -Direction Inbound -Protocol TCP -LocalPort 53 -Action Allow<br>New-NetFirewallRule -DisplayName \"Allow DNS UDP\" -Direction Inbound -Protocol UDP -LocalPort 53 -Action Allow<br><br># Kerberos (TCP ve UDP port 88)<br>New-NetFirewallRule -DisplayName \"Allow Kerberos TCP\" -Direction Inbound -Protocol TCP -LocalPort 88 -Action Allow<br>New-NetFirewallRule -DisplayName \"Allow Kerberos UDP\" -Direction Inbound -Protocol UDP -LocalPort 88 -Action Allow<br><br># LDAP (TCP port 389)<br>New-NetFirewallRule -DisplayName \"Allow LDAP TCP\" -Direction Inbound -Protocol TCP -LocalPort 389 -Action Allow<br><br># SMB (TCP ve UDP port 445)<br>New-NetFirewallRule -DisplayName \"Allow SMB TCP\" -Direction Inbound -Protocol TCP -LocalPort 445 -Action Allow<br>New-NetFirewallRule -DisplayName \"Allow SMB UDP\" -Direction Inbound -Protocol UDP -LocalPort 445 -Action Allow# DNS (TCP ve UDP port 53)<br>New-NetFirewallRule -DisplayName \"Allow DNS TCP\" -Direction Inbound -Protocol TCP -LocalPort 53 -Action Allow<br>New-NetFirewallRule -DisplayName \"Allow DNS UDP\" -Direction Inbound -Protocol UDP -LocalPort 53 -Action Allow<br><br># Kerberos (TCP ve UDP port 88)<br>New-NetFirewallRule -DisplayName \"Allow Kerberos TCP\" -Direction Inbound -Protocol TCP -LocalPort 88 -Action Allow<br>New-NetFirewallRule -DisplayName \"Allow Kerberos UDP\" -Direction Inbound -Protocol UDP -LocalPort 88 -Action Allow<br><br># LDAP (TCP port 389)<br>New-NetFirewallRule -DisplayName \"Allow LDAP TCP\" -Direction Inbound -Protocol TCP -LocalPort 389 -Action Allow<br><br># SMB (TCP ve UDP port 445)<br>New-NetFirewallRule -DisplayName \"Allow SMB TCP\" -Direction Inbound -Protocol TCP -LocalPort 445 -Action Allow<br>New-NetFirewallRule -DisplayName \"Allow SMB UDP\" -Direction Inbound -Protocol UDP -LocalPort 445 -Action Allow<br><br>Get-NetFirewallRule | Where-Object {$_.DisplayName -like \"*Allow*\"} | Format-Table DisplayName, Enabled, Direction, Action<\/p><p>Kurallar\u0131 kontrol etmek i\u00e7in:<\/p><p>Get-NetFirewallRule | Where-Object {$_.DisplayName -like \"*Allow*\"} | Format-Table DisplayName, Enabled, Direction, Action<\/p><p>Belirli bir portu kontrol etmek i\u00e7in:<\/p><p>Get-NetFirewallPortFilter | Where-Object {$_.LocalPort -eq \"53\"}<\/p><p>E\u011fer t\u00fcm bu kurallar\u0131 tek seferde kald\u0131rmak isterseniz:<\/p><p>Get-NetFirewallRule | Where-Object {$_.DisplayName -like \"*Allow*\"} | Remove-NetFirewallRule<\/p><p>Alternatif komut ile domaine almay\u0131 deneyin:<\/p><p>netdom join %computername% \/domain:domain.com \/userD:<a href=\"mailto:admin@domain.com\">admin@domain.com<\/a> \/passwordD:*<\/p><p>RPC (Remote Procedure Call) servisine ula\u015f\u0131lamad\u0131\u011f\u0131nda, durumu \u00e7\u00f6zmek i\u00e7in \u015fu ad\u0131mlar\u0131 uygulayal\u0131m:<\/p><p>1. RPC servisini kontrol edelim:<\/p><p>Get-Service RpcSs | Select-Object Name, Status<br>Start-Service RpcSs<\/p><p>2. RPC ile ilgili di\u011fer \u00f6nemli servisleri kontrol edelim:<\/p><p>$services = @(<br>\u2018RpcSs\u2019, # Remote Procedure Call<br>\u2018RpcEptMapper\u2019, # RPC Endpoint Mapper<br>\u2018DcomLaunch\u2019 # DCOM Server Process Launcher<br>)<\/p><p>Get-Service -Name $services | Select-Object Name, Status<\/p><p>3. RPC portlar\u0131n\u0131 a\u00e7al\u0131m:<\/p><p>4. Domain Controller\u2019a RPC ba\u011flant\u0131s\u0131n\u0131 test edelim:<\/p><p>Test-NetConnection -ComputerName domain.com -Port 135<\/p><p>5. Network ba\u011flant\u0131s\u0131n\u0131n tam testi:<\/p><p>$domainController = \u201cdomain.com\u201d<br>$ports = @(135, 389, 445, 88, 53)<\/p><p>foreach ($port in $ports) {<br>Write-Host \u201cTesting port $port\u2026\u201d<br>Test-NetConnection -ComputerName $domainController -Port $port<br>}<\/p><p>6. RPC servisini yeniden ba\u015flatal\u0131m:<\/p><p>Restart-Service RpcSs -Force<br>Restart-Service RpcEptMapper -Force<\/p><p>7. Netlogon servisini yeniden ba\u015flatal\u0131m:<\/p><p>Restart-Service Netlogon -Force<\/p><p>Bu ad\u0131mlar\u0131 uygulad\u0131ktan sonra tekrar domain\u2019e join olmay\u0131 deneyebilirsiniz:<\/p><p>$cred = Get-Credential \u201cDOMAIN\\admin\u201d<br>Add-Computer -DomainName \u201cdomain.com\u201d -Credential $cred -Force -Restart<\/p>","excerpt":"Domain\u2019e join olmadaki sorunu \u00e7\u00f6zmek i\u00e7in \u015fu ad\u0131mlar\u0131 takip edece\u011fiz","created_at":"2024-12-29 11:31:48","updated_at":"2026-09-06 20:54:47","category_id":6,"view_count":567,"reading_time":3,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2024-12-29 11:31:48","featured_image":"resimyok.jpg","slug":"domain-e-join-olma-islemi-sirasinda-ortaya-cikan-sorunu-cozmek-icin-yapilacak-islemler","category_name":"Sistem","category_slug":"sistem"}