{"id":4605,"date":"2026-09-10T08:00:00","date_gmt":"2026-09-10T05:00:00","guid":{"rendered":"https:\/\/www.ozgurguler.net\/blog\/?p=4605"},"modified":"2026-09-10T11:16:15","modified_gmt":"2026-09-10T08:16:15","slug":"windowsta-acik-portlari-ve-bu-portlari-kullanan-uygulamalari-bulma","status":"publish","type":"post","link":"https:\/\/www.ozgurguler.net\/blog\/windowsta-acik-portlari-ve-bu-portlari-kullanan-uygulamalari-bulma\/","title":{"rendered":"Windows’ta A\u00e7\u0131k Portlar\u0131 ve Bu Portlar\u0131 Kullanan Uygulamalar\u0131 Bulma"},"content":{"rendered":"

Windows’ta Hangi Uygulama Hangi Portu Kullan\u0131yor? Port ve PID Bulma Rehberi<\/strong><\/p>\n

Windows \u00fczerinde \u00e7al\u0131\u015fan bir uygulaman\u0131n hangi portu kulland\u0131\u011f\u0131n\u0131 bilmek, \u00f6zellikle sunucu ve istemci sistemlerinde olduk\u00e7a \u00f6nemlidir.<\/p>\n

ERP uygulamalar\u0131, SQL Server, web servisleri, entegrasyon programlar\u0131 veya arka planda \u00e7al\u0131\u015fan Windows servisleri belirli portlar\u0131 kullanabilir. Ayn\u0131 portu ba\u015fka bir uygulaman\u0131n kullanmas\u0131 ise ba\u011flant\u0131 sorunlar\u0131na veya uygulaman\u0131n hi\u00e7 \u00e7al\u0131\u015fmamas\u0131na neden olabilir.<\/p>\n

Peki Windows’ta hangi portlar\u0131n dinlendi\u011fini ve bu portlar\u0131 hangi uygulamalar\u0131n kulland\u0131\u011f\u0131n\u0131 nas\u0131l bulabiliriz?<\/p>\n

Bu yaz\u0131da bunu hem\u00a0CMD<\/strong>\u00a0hem de\u00a0PowerShell<\/strong>\u00a0\u00fczerinden ad\u0131m ad\u0131m inceleyelim.<\/p>\n

    \n
  1. Neden hangi portun kullan\u0131ld\u0131\u011f\u0131n\u0131 bilmek gerekir?<\/strong><\/li>\n<\/ol>\n

    Bir sistemde port bilgisi bir\u00e7ok durumda \u00f6nem kazanabilir.<\/p>\n

    \u00d6rne\u011fin:<\/p>\n

      \n
    • ERP servislerinin kulland\u0131\u011f\u0131 portlar\u0131 kontrol etmek,<\/li>\n
    • SQL Server’\u0131n hangi port \u00fczerinden ba\u011flant\u0131 kabul etti\u011fini g\u00f6rmek,<\/li>\n
    • Web servislerinin dinledi\u011fi portu tespit etmek,<\/li>\n
    • Entegrasyon uygulamalar\u0131n\u0131n kulland\u0131\u011f\u0131 portlar\u0131 bulmak,<\/li>\n
    • \u0130ki uygulaman\u0131n ayn\u0131 portu kullanmas\u0131 nedeniyle olu\u015fan \u00e7ak\u0131\u015fmalar\u0131 tespit etmek,<\/li>\n
    • Bir uygulaman\u0131n neden ba\u015flat\u0131lamad\u0131\u011f\u0131n\u0131 ara\u015ft\u0131rmak,<\/li>\n
    • G\u00fcvenlik a\u00e7\u0131s\u0131ndan sistemde hangi servislerin d\u0131\u015f ba\u011flant\u0131 kabul etti\u011fini g\u00f6rmek.<\/li>\n<\/ul>\n

      \u00d6zellikle bir program\u0131n \u00e7al\u0131\u015fmad\u0131\u011f\u0131 durumlarda ilk bak\u0131labilecek konulardan biri\u00a0kullan\u0131lmak istenen portun ba\u015fka bir uygulama taraf\u0131ndan kullan\u0131l\u0131p kullan\u0131lmad\u0131\u011f\u0131d\u0131r.<\/strong><\/p>\n

      \u26a0\ufe0f\u00a0Not:<\/strong>\u00a0Bu yaz\u0131daki komutlar\u0131n bir k\u0131sm\u0131 (\u00f6zellikle\u00a0taskkill\u00a0ve sistem s\u00fcre\u00e7lerini listeleyen\u00a0Get-Process\u00a0\u00e7a\u011fr\u0131lar\u0131) i\u00e7in CMD veya PowerShell’i\u00a0Y\u00f6netici olarak \u00e7al\u0131\u015ft\u0131rman\u0131z<\/strong>\u00a0gerekebilir. Aksi halde baz\u0131 PID’lerin uygulama adlar\u0131 bo\u015f g\u00f6r\u00fcnebilir.<\/p>\n

        \n
      1. Windows’ta a\u00e7\u0131k\/dinleyen portlar\u0131 bulma<\/strong><\/li>\n<\/ol>\n

        Windows’un Komut \u0130stemi’nde (CMD) a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131rabiliriz:<\/p>\n

        netstat -ano | findstr LISTENING<\/p><\/blockquote>\n

        Bu komut bize bilgisayar \u00fczerinde ba\u011flant\u0131 bekleyen, yani\u00a0LISTENING durumundaki portlar\u0131<\/strong>\u00a0g\u00f6sterir.<\/p>\n

        \u00d6rne\u011fin \u015f\u00f6yle bir sonu\u00e7 g\u00f6rebiliriz:<\/p>\n

        TCP\u00a0\u00a0\u00a0 0.0.0.0:8080\u00a0\u00a0\u00a0\u00a0\u00a0 0.0.0.0:0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTENING\u00a0\u00a0\u00a0\u00a0\u00a0 4520<\/p>\n

        TCP\u00a0\u00a0\u00a0 0.0.0.0:1433\u00a0\u00a0\u00a0\u00a0\u00a0 0.0.0.0:0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTENING\u00a0\u00a0\u00a0\u00a0\u00a0 1234<\/p>\n

        Burada dikkat etmemiz gereken son s\u00fctundur.<\/p>\n

        4520\u00a0ve\u00a01234<\/p>\n

        de\u011ferleri\u00a0PID (Process ID)<\/strong>\u00a0de\u011ferleridir.<\/p>\n

        Ancak\u00a0netstat\u00a0bize do\u011frudan uygulaman\u0131n ad\u0131n\u0131 g\u00f6stermez.<\/strong><\/p>\n

        \u0130\u015fte burada PID bilgisi devreye girer.<\/p>\n

          \n
        1. PID’den uygulamay\u0131 bulma<\/strong><\/li>\n<\/ol>\n

          \u00d6rne\u011fimizde 8080 portunu kullanan i\u015flemin PID de\u011feri:<\/p>\n

          4520\u00a0Bu PID’nin hangi uygulamaya ait oldu\u011funu \u00f6\u011frenmek i\u00e7in CMD’de:<\/p>\n

          tasklist \/FI “PID eq 4520”\u00a0komutunu \u00e7al\u0131\u015ft\u0131rabiliriz.<\/p>\n

          Windows bize ilgili i\u015flemin ad\u0131n\u0131 g\u00f6sterecektir.<\/p>\n

          B\u00f6ylece i\u015flem s\u0131ras\u0131 \u015fu hale gelir:<\/p>\n

          Port<\/p>\n

          \u2193<\/p>\n

          PID<\/p>\n

          \u2193<\/p>\n

          Uygulama<\/p>\n

          \u00d6rne\u011fin:<\/p>\n

          8080 \u2192 PID 4520 \u2192 uygulama.exe<\/p>\n

          Bu y\u00f6ntem \u00f6zellikle bir uygulaman\u0131n hangi portu kulland\u0131\u011f\u0131n\u0131 tespit etmek i\u00e7in olduk\u00e7a kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n

            \n
          1. Tek komutla Port + PID + Uygulama Ad\u0131<\/strong><\/li>\n<\/ol>\n

            Windows PowerShell kullan\u0131yorsak i\u015flemi daha da kolayla\u015ft\u0131rabiliriz. A\u015fa\u011f\u0131da ihtiyaca g\u00f6re \u00fc\u00e7 farkl\u0131 seviye sunuyoruz.<\/p>\n

            \ud83d\udd39 Basit kullan\u0131m (h\u0131zl\u0131 bak\u0131\u015f)<\/strong><\/p>\n

            G\u00fcnl\u00fck kullan\u0131mda h\u0131zl\u0131ca portlar\u0131 listelemek i\u00e7in yeterlidir. Ancak sistem s\u00fcre\u00e7lerinde (System,\u00a0Idle) veya yetki yetersizli\u011fi durumunda\u00a0ProcessName\u00a0alan\u0131 bo\u015f kalabilir.<\/p>\n

             <\/p>\n

            Get-NetTCPConnection -State Listen | Select-Object LocalPort,OwningProcess,@{N=”ProcessName”;E={(Get-Process -Id $_.OwningProcess).ProcessName}}<\/p><\/blockquote>\n

             <\/p>\n

            \ud83d\udd39 Raporlama \/ d\u00fczenli \u00e7\u0131kt\u0131 i\u00e7in<\/strong><\/p>\n

            LocalAddress\u00a0s\u00fctunu eklenir, port numaras\u0131na g\u00f6re s\u0131ralan\u0131r ve s\u00fctunlar otomatik hizalan\u0131r. Sunucu raporlar\u0131nda okunmas\u0131 kolayd\u0131r.<\/p>\n

            \u00a0<\/strong><\/p>\n

            Get-NetTCPConnection -State Listen | Select-Object LocalAddress,LocalPort,OwningProcess,@{N=”ProcessName”;E={(Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).ProcessName}} | Sort-Object LocalPort | Format-Table -AutoSize<\/strong><\/p><\/blockquote>\n

            \u00a0<\/strong><\/p>\n

            \ud83d\udd39 Script i\u00e7inde g\u00fcvenilir \u00e7\u0131kt\u0131 i\u00e7in (\u00f6nerilen) <\/strong>\u2705<\/strong><\/p>\n

            try\/catch\u00a0ile hata yakalan\u0131r; i\u015flem bulunamazsa\u00a0ProcessName\u00a0alan\u0131na\u00a0\u2014\u00a0yaz\u0131l\u0131r. B\u00f6ylece \u00e7\u0131kt\u0131 hi\u00e7bir zaman bozulmaz ve\u00a0Export-Csv,\u00a0ConvertTo-Json\u00a0gibi komutlarla rahat\u00e7a birle\u015ftirilebilir.<\/p>\n

             <\/p>\n

            Get-NetTCPConnection -State Listen | ForEach-Object { $procName = try { (Get-Process -Id $_.OwningProcess -ErrorAction Stop).ProcessName } catch { “\u2014” }; [PSCustomObject]@{ LocalAddress = $_.LocalAddress; LocalPort = $_.LocalPort; PID = $_.OwningProcess; ProcessName = $procName } } | Sort-Object LocalPort | Format-Table -AutoSize<\/p><\/blockquote>\n

             <\/p>\n

            \u00d6rnek \u00e7\u0131kt\u0131:<\/p>\n

            LocalAddress\u00a0\u00a0 LocalPort\u00a0\u00a0 PID\u00a0\u00a0\u00a0 ProcessName<\/p>\n

            ————\u00a0\u00a0 ———\u00a0\u00a0 —\u00a0\u00a0\u00a0 ———–<\/p>\n

            0.0.0.0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1433\u00a0\u00a0 1234\u00a0\u00a0 sqlservr<\/p>\n

            0.0.0.0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8080\u00a0\u00a0 4520\u00a0\u00a0 uygulama<\/p>\n

            127.0.0.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5432\u00a0\u00a0 3320\u00a0\u00a0 postgres<\/p>\n

            ::\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 445\u00a0\u00a0\u00a0\u00a0\u00a0 4\u00a0\u00a0 System<\/p>\n

            ::\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5357\u00a0\u00a0\u00a0\u00a0\u00a0 4\u00a0\u00a0 System<\/p>\n

            Burada art\u0131k ayr\u0131ca\u00a0tasklist\u00a0\u00e7al\u0131\u015ft\u0131rmam\u0131za gerek kalmaz. Tek komutta\u00a0Port + PID + uygulama ad\u0131<\/strong>\u00a0bilgisine ula\u015fabiliriz. Bu nedenle \u00f6zellikle \u00e7ok say\u0131da portun bulundu\u011fu sunucularda PowerShell y\u00f6ntemi daha pratiktir.<\/p>\n

            \u26a0\ufe0f\u00a0Not:<\/strong>\u00a0Get-Process -Id $_.OwningProcess\u00a0baz\u0131 sistem s\u00fcre\u00e7leri (System,\u00a0Idle) veya yetki yetersizli\u011fi durumunda hata verebilir. Bu y\u00fczden\u00a0-ErrorAction SilentlyContinue\u00a0eklemek veya\u00a0try\/catch\u00a0kullanmak daha sa\u011flam bir \u00e7\u0131kt\u0131 alman\u0131z\u0131 sa\u011flar.<\/p>\n

              \n
            1. Belirli bir portu arama<\/strong><\/li>\n<\/ol>\n

              E\u011fer yaln\u0131zca belirli bir portu kontrol etmek istiyorsak t\u00fcm listeyi incelememize gerek yoktur.<\/p>\n

              \u00d6rne\u011fin 8080 portunu aramak i\u00e7in:<\/p>\n

              netstat -ano | findstr :8080<\/p><\/blockquote>\n

              komutunu kullanabiliriz.<\/p>\n

              Sonu\u00e7 \u00f6rne\u011fin:<\/p>\n

              TCP\u00a0\u00a0\u00a0 0.0.0.0:8080\u00a0\u00a0\u00a0 0.0.0.0:0\u00a0\u00a0\u00a0 LISTENING\u00a0\u00a0\u00a0 4520<\/p>\n

              \u015feklindeyse 8080 portunu kullanan i\u015flemin PID’si:\u00a04520\u00a0demektir.<\/p>\n

              Ard\u0131ndan:<\/p>\n

              tasklist \/FI “PID eq 4520”<\/p><\/blockquote>\n

              ile uygulamay\u0131 bulabiliriz.<\/p>\n

              PowerShell taraf\u0131nda ise do\u011frudan port filtresiyle \u00e7al\u0131\u015fabiliriz:<\/p>\n

              Get-NetTCPConnection -LocalPort 8080 -State Listen |
              \nSelect-Object LocalAddress, LocalPort, OwningProcess,
              \n@{N=”ProcessName”;E={(Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).ProcessName}}<\/p><\/blockquote>\n

                \n
              1. Portu kullanan i\u015flemi sonland\u0131rmak<\/strong><\/li>\n<\/ol>\n

                Bazen bir uygulamay\u0131 kapatmam\u0131za ra\u011fmen portun h\u00e2l\u00e2 kullan\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6rebiliriz.<\/p>\n

                Bu durumda i\u015flemin PID’sini tespit ettikten sonra Windows’un\u00a0taskkill\u00a0komutu kullan\u0131labilir.<\/p>\n

                \u00d6rne\u011fin:<\/p>\n

                taskkill \/PID 4520 \/F<\/p>\n

                Burada\u00a04520\u00a0ilgili i\u015flemin PID’sidir.<\/p>\n

                Ancak bu komut dikkatli kullan\u0131lmal\u0131d\u0131r.<\/p>\n

                PID’nin hangi uygulamaya ait oldu\u011funu do\u011frulamadan bir i\u015flemi sonland\u0131rmak do\u011fru de\u011fildir.<\/strong><\/p>\n

                \u00d6zellikle sunucu bilgisayarlar\u0131nda SQL Server, ERP servisleri, Windows servisleri veya ba\u015fka kritik uygulamalar \u00e7al\u0131\u015f\u0131yor olabilir.<\/p>\n

                Bu nedenle do\u011fru s\u0131ra:<\/p>\n

                Portu bul<\/p>\n

                \u2193<\/p>\n

                PID’yi tespit et<\/p>\n

                \u2193<\/p>\n

                PID’nin uygulamas\u0131n\u0131 kontrol et<\/p>\n

                \u2193<\/p>\n

                Gerekliyse i\u015flemi sonland\u0131r<\/p>\n

                \u015feklinde olmal\u0131d\u0131r.<\/p>\n

                \u26a0\ufe0f\u00a0Not:<\/strong>\u00a0taskkill\u00a0komutu \u00e7o\u011fu zaman\u00a0Y\u00f6netici yetkisi<\/strong>\u00a0gerektirir. Ayr\u0131ca\u00a0\/F\u00a0parametresi i\u015flemi zorla sonland\u0131r\u0131r; kaydedilmemi\u015f veri kayb\u0131na yol a\u00e7abilir.<\/p>\n

                  \n
                1. \u00d6rnek senaryo<\/strong><\/li>\n<\/ol>\n

                  Bir uygulamay\u0131 \u00e7al\u0131\u015ft\u0131rmaya \u00e7al\u0131\u015f\u0131yoruz ve uygulama 8080 portunu kullanmak istiyor.<\/p>\n

                  Ancak uygulama ba\u015flat\u0131lam\u0131yor.<\/p>\n

                  \u00d6ncelikle 8080 portunu kontrol ediyoruz:<\/p>\n

                  netstat -ano | findstr :8080<\/p><\/blockquote>\n

                  Sonu\u00e7:<\/p>\n

                  TCP\u00a0\u00a0\u00a0 0.0.0.0:8080\u00a0\u00a0\u00a0 0.0.0.0:0\u00a0\u00a0\u00a0 LISTENING\u00a0\u00a0\u00a0 4520<\/p>\n

                  8080 portunun kullan\u0131mda oldu\u011funu g\u00f6r\u00fcyoruz.<\/p>\n

                  \u015eimdi PID 4520’nin hangi uygulamaya ait oldu\u011funu buluyoruz:<\/p>\n

                  tasklist \/FI “PID eq 4520”<\/p><\/blockquote>\n

                  B\u00f6ylece portu hangi uygulaman\u0131n kulland\u0131\u011f\u0131n\u0131 \u00f6\u011freniyoruz.<\/p>\n

                  Yani asl\u0131nda birka\u00e7 saniyede:<\/p>\n

                  8080<\/p>\n

                  \u2193<\/p>\n

                  4520<\/p>\n

                  \u2193<\/p>\n

                  Uygulama<\/p>\n

                  \u015feklinde ilerleyerek port \u00e7ak\u0131\u015fmas\u0131n\u0131n kayna\u011f\u0131n\u0131 tespit etmi\u015f oluyoruz.<\/p>\n

                    \n
                  1. UDP portlar\u0131<\/strong><\/li>\n<\/ol>\n

                    Buraya kadarki t\u00fcm komutlar\u00a0TCP<\/strong>\u00a0portlar\u0131n\u0131 listeler. Ancak DNS (53), DHCP (67\/68), SNMP (161), Syslog (514) ve baz\u0131 oyun sunucular\u0131 gibi servisler\u00a0UDP<\/strong>\u00a0kullan\u0131r.<\/p>\n

                    CMD’de UDP portlar\u0131 i\u00e7in:<\/strong><\/p>\n

                    cmd<\/p>\n

                    netstat -ano -p UDP<\/p>\n

                    PowerShell’de UDP u\u00e7 noktalar\u0131 i\u00e7in:<\/strong><\/p>\n

                    Get-NetUDPEndpoint |
                    \nSelect-Object LocalAddress, LocalPort, OwningProcess,
                    \n@{N=”ProcessName”;E={(Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).ProcessName}} |
                    \nSort-Object LocalPort |
                    \nFormat-Table -AutoSize<\/p><\/blockquote>\n

                    \ud83d\udca1\u00a0\u0130pucu:<\/strong>\u00a0Bir portun hem TCP hem UDP taraf\u0131nda dinlenip dinlenmedi\u011fini kontrol etmek i\u00e7in iki komutu ayr\u0131 ayr\u0131 \u00e7al\u0131\u015ft\u0131rman\u0131z gerekir.<\/p>\n

                      \n
                    1. Hangi komut ne i\u015fe yar\u0131yor?<\/strong><\/li>\n<\/ol>\n\n\n\n\n\n\n\n\n\n\n\n\n
                      Komut<\/td>\nNe g\u00f6sterir?<\/td>\n<\/tr>\n<\/thead>\n
                      netstat -ano<\/td>\nAktif TCP ba\u011flant\u0131lar\u0131n\u0131 ve PID bilgilerini<\/td>\n<\/tr>\n
                      netstat -ano | findstr LISTENING<\/td>\nDinleyen TCP portlar\u0131n\u0131 ve PID bilgilerini<\/td>\n<\/tr>\n
                      netstat -ano -p UDP<\/td>\nYaln\u0131zca UDP ba\u011flant\u0131lar\u0131n\u0131<\/td>\n<\/tr>\n
                      tasklist \/FI “PID eq 4520”<\/td>\nBelirli PID’nin hangi uygulamaya ait oldu\u011funu<\/td>\n<\/tr>\n
                      Get-NetTCPConnection<\/td>\nPowerShell \u00fczerinden TCP ba\u011flant\u0131 bilgilerini<\/td>\n<\/tr>\n
                      Get-NetTCPConnection -LocalPort 8080<\/td>\nBelirli bir TCP portunu do\u011frudan<\/td>\n<\/tr>\n
                      Get-NetUDPEndpoint<\/td>\nPowerShell \u00fczerinden UDP u\u00e7 noktalar\u0131n\u0131<\/td>\n<\/tr>\n
                      Get-Process<\/td>\n\u00c7al\u0131\u015fan i\u015flemler hakk\u0131nda bilgi<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                      Sonu\u00e7<\/strong><\/p>\n

                      Windows \u00fczerinde bir portun hangi uygulama taraf\u0131ndan kullan\u0131ld\u0131\u011f\u0131n\u0131 bulmak i\u00e7in asl\u0131nda birka\u00e7 temel komutu bilmek yeterlidir.<\/p>\n

                      CMD taraf\u0131nda en temel y\u00f6ntem:<\/p>\n

                      netstat -ano | findstr LISTENING<\/p><\/blockquote>\n

                      Ard\u0131ndan PID’yi uygulama ad\u0131na \u00e7evirmek i\u00e7in:<\/p>\n

                      tasklist \/FI “PID eq 4520”<\/p><\/blockquote>\n

                      PowerShell taraf\u0131nda ise i\u015fi tek komutta ve g\u00fcvenilir \u015fekilde yapmak m\u00fcmk\u00fcnd\u00fcr:<\/p>\n

                      Get-NetTCPConnection -State Listen | ForEach-Object {<\/p>\n

                      $procName = try {<\/p>\n

                      (Get-Process -Id $_.OwningProcess -ErrorAction Stop).ProcessName<\/p>\n

                      } catch { “\u2014” }<\/p>\n

                      [PSCustomObject]@{<\/p>\n

                      LocalAddress = $_.LocalAddress<\/p>\n

                      LocalPort\u00a0\u00a0\u00a0 = $_.LocalPort<\/p>\n

                      PID\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = $_.OwningProcess<\/p>\n

                      ProcessName\u00a0 = $procName<\/p>\n

                      }<\/p>\n

                      } | Sort-Object LocalPort | Format-Table -AutoSize<\/p><\/blockquote>\n

                      UDP portlar\u0131n\u0131 da g\u00f6rmek isterseniz:<\/p>\n

                      Get-NetUDPEndpoint | Select-Object LocalAddress, LocalPort, OwningProcess, @{N=”ProcessName”;E={(Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).ProcessName}} | Sort-Object LocalPort | Format-Table -AutoSize<\/p><\/blockquote>\n

                      \u00d6zellikle\u00a0ERP, SQL Server, web servisleri ve entegrasyon uygulamalar\u0131n\u0131n bulundu\u011fu bilgisayarlarda<\/strong>\u00a0bu birka\u00e7 komut, ba\u011flant\u0131 ve port sorunlar\u0131n\u0131n kayna\u011f\u0131n\u0131 bulmak i\u00e7in olduk\u00e7a kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n

                      Bir sonraki sorun ya\u015fand\u0131\u011f\u0131nda ak\u0131lda tutulabilecek en basit zincir ise \u015fudur:<\/p>\n

                      PORT \u2192 PID \u2192 UYGULAMA<\/strong><\/p>\n

                       <\/p>\n","protected":false},"excerpt":{"rendered":"

                      Windows’ta Hangi Uygulama Hangi Portu Kullan\u0131yor? Port ve PID Bulma Rehberi Windows \u00fczerinde \u00e7al\u0131\u015fan bir uygulaman\u0131n hangi portu kulland\u0131\u011f\u0131n\u0131 bilmek, \u00f6zellikle sunucu ve istemci sistemlerinde olduk\u00e7a \u00f6nemlidir. ERP uygulamalar\u0131, SQL Server, web servisleri, entegrasyon programlar\u0131 veya arka planda \u00e7al\u0131\u015fan Windows servisleri belirli portlar\u0131 kullanabilir. Ayn\u0131 portu ba\u015fka bir uygulaman\u0131n kullanmas\u0131 ise ba\u011flant\u0131 sorunlar\u0131na veya uygulaman\u0131n […]<\/p>\n","protected":false},"author":4,"featured_media":1588,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,6],"tags":[],"class_list":["post-4605","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji-haberleri","category-web-servis"],"_links":{"self":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4605","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/comments?post=4605"}],"version-history":[{"count":3,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4605\/revisions"}],"predecessor-version":[{"id":4608,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4605\/revisions\/4608"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media\/1588"}],"wp:attachment":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media?parent=4605"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/categories?post=4605"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/tags?post=4605"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}