This may not be the right place because this is a feature of SBS 2008 with Exchange 2007 so please forward if necessary.Internally, I'm able to send and receive email to users on the network, but this is where it stops. Sending and receiving email doesn't arrive at the destination without any errors (outside will get a return to sender after 24 hours). Using the Fix My Network feature of SBS 2008, I get the following problems:- An Internet port mapping is missing- A network component is not configured properly. (Component ID 3) - One or more networking components are not configured properly. (Component ID 3. For more information, see http://go.microsoft.com/fwlink?/LinkID=120178).It offers to fix and does so "successfully". Unfortunately it doesn't actually fix anything because rerunning the wizard shows the problem again.What I've tried is: - updated Exchange 2007 to SP2 - updated ForeFront to SP2 - manually forwarded port 25 on the router to the server (UPnp used to do this automatically) - verified the other ports are forwarded (80/443/etc) - verified OWA and Outlook can connect - verified that all the Exchange services are running. - run the Exchange Best Practices tool. Only problem that comes up is that IPv6 is not supported, otherwise is clear.I haven't seen anything stand out in the Event log but it's pretty big and hard to sift through but I'm going to keep trying. Any ideas? What's Component ID 3? Thanks for your help.

Hi,If you don't have an edge server in your network, you need to create a send/Receive connector on the HUB transport server. You also need to make sure that the exchange server can perform name resolution (find other mail server on the internet) and that port 25 is open in the firewall from the server to the internet.See here also to check, how to configure Hub Server for mail configurations" http://technet.microsoft.com/en-us/library/bb738138(EXCHG.80).aspx Regards from www.windowsadmin.info

Hi, thanks for the quick reply.Unfortunately this wasn't the answer. I hate this too because there's no sending or receiving email while this is down so I'm not sure what I'm losing.So, I've got some more information that might help narrow this down more. One very important part is that this is not a new install. This has been working for awhile and spontaneously stopped overnight. No updates other than block lists/spam filter updates. I did install Exchange SP2 after in hopes this would fix the problem.Next, I looked at the HUB configuration and compared to the link above and several others and everything looks correct. This includes the listening IP address of the server and the port 25. I also tested the router to make sure it was at least trying to forward port 25.But there's a couple things wrong. First is NetStat doesn't report a connection on port 25. 80/443 and such are there, and all the services are running, including the Transport. Also, both sending and receiving fails. So, if I send an email out to hotmail from Outlook (on the domain), it tries and returns it after 24 hours. Same goes for sending email from hotmail to exchange: fails in 24h. The ATT0001 says "Delayed, 4.4.7".What I really hate is the lack of tracing and event reporting in Windows, SBS, and Exchange. Nothing informative in the Eventvwr, the failure emails, the SBS "Fix Network" tool, Exchange Best Practices tool. Can anybody tell me what "Component ID 3" is?Thanks for your help.

I would suggest using Telnet to test SMTP communication as outlined here:http://technet.microsoft.com/en-us/library/bb123686(EXCHG.80).aspxAlso, you can use the Mail Flow Troubleshooter found in Exchange Management Console's (EMC) Toolbox.

Sorry. I should have mentioned this earlier, I forgot to mention the Mail Flow Ttroubleshooter with the Exchange Best Practice tests and SBS's Fix Network tool when I explained the problems, my fault.The MFT does say everything is okay, I went through every option it had. The EBP tool does have a warning that Exchange doesn't support IPv6 however it's not configured to use it (that I know of). SBS's tool does find a problem but is vague about it and fails on it's promise to fix it.I was hoping netstat would provide a clue on this warning showing a binding of port 25 to an IPv6 address, but since there are none on IPv4 or 6, there's no way it can work. Side note, no, telnet cannot connect to this port.Here's the issue: 1) no listening port 25. the rest are in fact fine and I can even get mails in Exchange, OWA, and Mobile Exchange that my mail attempts aren't received2) fix'em up utilities don't help3) configuration looks acceptable, particularly in the HUB transport and their IP/Port bindings4) all services are running and no changes if they or the system restarts5) it used to work greatWhat's left? This is day 4 of no email and I'm starting to panic. Still, any ideas what Component ID 3 is yet? Is it the Exchange Transport or Binding? Is it a broad component or a specific one?

Hi,For the SBS2008 issue, please post it on the below link: https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx?wa=wsignin1.0 ThanksAllen

If your Exchange server is not listening on port 25 you will need to diagnose that problem. Start by checking your Send Connectors and Receive Connectors. You can also enable protocol logging on your Send Connectors and Receive Connectors to gather information about mail flow and SMTP conversations into and out of your organization. See this article:http://technet.microsoft.com/en-us/library/bb124531(EXCHG.80).aspxBy default, the protocol log files will be placed in C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive and C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend

Where did you telnet from to test port 25? Try "telnet localhost 25" on the server. If that answers, then it is listining, and you're looking for a firewall issue.

SOLVED! Well, sortof. Not really solved but at least I know the problem. As a background, this server system is at home running on a popular (yet expensive and problematic) ISP. The problem was caused by them cuttng off all Port 25 traffic at the router level. This is why there were no informative or obvious log files, configuration settings, or problems detected by Exchange or SBS test tools. They were all happily sending and recieving email as they always did, but according to them, the other side was down. This also explains why it spontaneously stopped working.Upon looking up their name + "port 25", complaints are too numerous to count. It's understandable that they want to manage spam, but I wish they'd base this on blocking offenders instead of everybody. Sigh. They're well known for not volunteering this either.Either way, thanks everybody for your help and suggestions. Sorry if I sounded grumpy later.Brendan

Brendan- My home ISP has some similiar features to yours. What I did is paid for this service called Mailhop from Dyndns. It's 40 or 50 bucks a year and they function as your MX and then relay the mail back to you on a nonstandard port (e.g. my Exchange server at home is listening on port 2525).Active Directory, 4th Edition - www.briandesmond.com/ad4/