Exchange 2007 Pop3 Sorunu

Merhaba ,

1. MMC konsulunu açıp Services ,  Services (Local).
   
   
2. Sağ tıklayıp Microsoft Exchange POP3, Properties i açalım.
   
   
3. General tabından,  Startup type, Automatic i seçelim, ve  Apply diyelim.
   
   
4. Service status, den Start, ve OK diyip çıkalım ...

servisler kısmında pop3 servisi yok sorunda burdan kaynaklanıyor diye düşünüyorum.

Merhaba kullanıcıların mail alıp vermeye devam ettiğini söylediniz.Eventlara düşen birşeyler varmı bununla ilgili.

kullanıcılar exchange hesaplarından mail alıp verebiliyorlar.Fakat pop3 servisi service ler kısmında gözükmüyor.

Eventlarda bununla ilgili bir log varmı?

Active Directory kısmında verilen log bu;

Active Directory Domain Services could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory Domain Services successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.
 
Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory Domain Services forest, including logon authentication or access to network resources.
 
You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS.
 
Alternate server name:
 fabsql
Failing DNS host name:
 4131e188-43f8-490a-8b51-a19bc3c196e7._msdcs.FABEKS.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:
 11001 No such host is known.

Exchange tarafında verilen log ;

Microsoft Exchange could not find a certificate that contains the domain name mail.fabeks.com in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector FABEKS with a FQDN parameter of mail.fabeks.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

 ve

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18.02.2010 15:38:54
Event time (UTC): 18.02.2010 13:38:54
Event ID: 8ae8ca7357514018932c27aa837283c2
Event sequence: 87
Event occurrence: 86
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1/ROOT/EWS-1-129109514574184687
    Trust level: Full
    Application Virtual Path: /EWS
    Application Path: D:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\EWS\
    Machine name: FABEKSDOMAIN
 
Process information:
    Process ID: 7636
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
 
Exception information:
    Exception type: FileNotFoundException
    Exception message: Could not load file or assembly 'Microsoft.Exchange.Diagnostics, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
 
Request information:
    Request URL: https://fabeksdomain.fabeks.local:443/EWS/Exchange.asmx
    Request path: /EWS/Exchange.asmx
    User host address: 192.168.0.57
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: NT AUTHORITY\SYSTEM
 
Thread information:
    Thread ID: 8
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:    at Microsoft.Exchange.Services.AuthorizationModule.Init(HttpApplication context)
   at System.Web.HttpApplication.InitModulesCommon()
   at System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers)
   at System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context)
   at System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context)
   at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
 
 
Custom event details:
 

Bu farklı bir uyarı system altında varsa eğer pop3 servisi ile ilgili bir log onu verin farklı log yollamayın.

pop3 ile alakalı düşen bir log yok.

Sistemi restart edip denedinizmi?

bir çok kez restart ettim

http://technet.microsoft.com/en-us/library/dd469606(WS.10).aspx  bu makaleyi incelermisiniz?

öncelikle ilginize çok teşekkür ederim.Vermiş olduğunuz link SBS için anlatıyor.Burdaki sistemde std. x64 var

Merhaba,

EMC / Server Configuration / Client Access  kısmında POP ve IMAP4 ü görebiliyormusunuz peki ?

Merhaba

öncelikle netstat -na|find "110" komutu yardımı ile 110 nolu portu dinleyen başka bir servisin olup olmadığını kontrol edin

ekran görüntüsünü bizimle paylaşabilirsiniz

ayrıca EMC üzerinden Receive Connector lerden 110 nolu portu dinleyen bir connector olup olmadığını kontrol edermisiniz.

EMC - Server configuration - Client Access - POP3 and IMAP sekmesinde