Solved

URGENT - SBS 2008 not sending and receiving email

Posted on 2011-09-02
7
722 Views
Last Modified: 2012-05-12
I have a SBS 2008 with exchange 2007 not sending email

This is the error I see in the queue
451 4.4.0 primary target ip address responded with 421 4.2.1 unable to connect

After I did a test I see that he and all other users are not receiving any emails either.
The email that the users are trying to send are all in the queue with the error above

I has this same problem a few weeks ago on the server and rebooted the server which solved the problem. Today I have already rebooted twice and no luck.
This is the post from a few weeks ago
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_27247029.html

Please help.
0
Comment
Question by:Gerhardpet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 13

Expert Comment

by:5g6tdcv4
ID: 36476223
are all exchange services running on the server?
Does BPA report any errors?
0
 
LVL 13

Expert Comment

by:5g6tdcv4
ID: 36476229
is the database mounted...?
any event log errors regarding exchange?
0
 
LVL 1

Author Comment

by:Gerhardpet
ID: 36476383
Yes exchange is running. What is BPA and where to I check for errors?
0
Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

 
LVL 13

Expert Comment

by:5g6tdcv4
ID: 36476394
Best practices analyzer
0
 
LVL 1

Author Comment

by:Gerhardpet
ID: 36477855
I don't see anything obvious in Best practices analyzer

Below is the scan I did and perhaps you can look at it


All Issues  
  Windows SBS Update Services not at default setting :  
 Synchronization Options for Windows Server Update Services is not set to All Microsoft Products. Because of this, software updates are not managed by Windows SBS 2008 Update Services. This results in a blue question mark in the Updates section of the Windows SBS Console. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=103721).
 
  Windows SBS Update Services not at default setting :  
 Windows Server Update Services is not set to store files locally. The Store Update Files Locally option is not selected in the Update Files and Languages properties for Windows Server Update Services. Because of this, software updates are not managed by Windows SBS 2008 Update Services. This results in a blue question mark in the Updates section of the Windows SBS Console. For more information, see the Windows SBS 2008 Technical Library at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=103721).
 
  Windows SBS Update Services not set to default settings :  
 Server Targeting for Windows Server Update Services is not selected. The Server Targeting option is not selected in the Computers properties for Windows Server Update Services. Because of this, software updates are not managed by Windows SBS 2008 Update Services. This results in a blue question mark in the Updates section of the Windows SBS Console. For more information, see the Windows SBS 2008 Technical Library at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=103721).
 
  Local activation permission to the IIS WAMREG Admin Service required :  
 The Network Service is missing local activation permissions to the IIS WAMREG admin Service in accordance with the event ID 10016 in the system event log. For more information, see KB "Event ID error messages 10016 and 10017 are logged in the System log after you install Windows SharePoint Services 3.0" at http://go.microsoft.com/fwlink/?LinkId=128063. Note: This warning will continue to appear until at least 24 hours have passed since the most recent occurrence of event 10016.
 
  The BackConnectionHostNames registry key does not exist :  
 The registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames does not exist. To resolve this issue, open Registry Editor, and then locate and click HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\. Right-click MSV1_0, point to New, and then click Multi-String Value. Type BackConnectionHostNames, and then press ENTER. Right-click the BackConnectionHostNames key, and then click Modify. In the Value data box, add the names "companyweb" and "remote.kargomax.ca" (do not include the quotation marks), and then click OK. Exit Registry Editor and then restart the IISAdmin service. For more information see the Knowledge Base article "Errors when crawling content sources in SharePoint Server 2007: "Event ID 2436" and "Access is denied"" at http://go.microsoft.com/fwlink/?LinkId=195553.
 
  The DNS parameter MaxCacheTTL is not set :  
 The DNS parameter MaxCacheTTL is not set. For more information, see "Windows Server 2008 DNS Servers may fail to resolve queries for some top-level domains" in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=152402.
 
  The log file for the Windows SharePoint Services configuration database is getting large :  
 The log file for the Windows SharePoint Services configuration database is larger than 1 GB in size. For information about how to reduce the size of the log file, see the Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=159745.
 
  User account does not show in the Windows SBS Console :  
 The user account MWService does not have the attributes that are necessary for it to display in the Windows SBS Console.
 
  User account does not show in the Windows SBS Console :  
 The user account trend admin does not have the attributes that are necessary for it to display in the Windows SBS Console.
 
  User account does not show in the Windows SBS Console :  
 The user account Printer does not have the attributes that are necessary for it to display in the Windows SBS Console.
 
0
 
LVL 1

Accepted Solution

by:
Gerhardpet earned 0 total points
ID: 36478644
Finally found out that the ISP blocked port 25 without letting me know
0
 
LVL 1

Author Closing Comment

by:Gerhardpet
ID: 36501244
Found the problem myself
0

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Changing a few Outlook Options can help keep you organized!
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question