Netopia ****

ftlnn · 02-25-2010, 07:29 AM

Hi All,

This is driving me mad.
A friend of mine has recently been ill advised by an ISP support to reset his router. I say this because he is running a business with Exchange Server and the router should have been configured appropiately. Since this reset he has not been able to get on to the Inet until I talked him through setting up the router ip within his network. Now he is able to access the internet and is able to retreive emails BUT he cannot send emails. I suspect that there is some sort of outbound rule that needs to be applied to the router but cannot for the **** find how to do it. Neither Netopia or the ISP have been helpful in resolving the matter. He can send emails internally though. I don't suspect there is any issue with the Exchange server since no change has been made to it. The router is a Netopia 2247 nwg. PLEASE PLEASE Any help greatfully apppreciated!

wimiadmin · 02-25-2010, 12:27 PM

I doubt the router has an outbound firewall blocking traffic.

Port 25 is outgoing mail (default) so you'll need to investigate why that's being blocked.

Is he assigned a static IP via his ISP? Most residential IPs have port 25 blocked unless you are sending mail through the ISPs mail system. Since he's sending mail on his own server, he'll need to make sure that the ISP has his IP in a 'business' group so that port 25 isn't blocked.

Since you can send/receive mail internally, then yes, most likely the Exchange server is fine.

AboveTheLogic · 02-25-2010, 04:58 PM

When you say he can send emails internally, do you mean from the LAN--- or do you mean he can only send to internal emails? I'm guessing the former--- but if its the latter then its definitely an Exchange issue (probably just not doing SMTP authentication).

Also the story changes if you are using RPC over HTTP (Outlook Anywhere) with Exchange instead of IMAP/POP/SMTP.

All signs point to an ISP blocking port 25. Consider setting Exchange to listen on both port 25 and 26 (and do the appropriate port forward of course), and set your clients to send on port 26 instead of 25.

02-25-2010, 07:29 AM	#1
ftlnn Member Join Date: Feb 2010 Posts: 1	Netopia ** Hi All, This is driving me mad. A friend of mine has recently been ill advised by an ISP support to reset his router. I say this because he is running a business with Exchange Server and the router should have been configured appropiately. Since this reset he has not been able to get on to the Inet until I talked him through setting up the router ip within his network. Now he is able to access the internet and is able to retreive emails BUT he cannot send emails. I suspect that there is some sort of outbound rule that needs to be applied to the router but cannot for the ** find how to do it. Neither Netopia or the ISP have been helpful in resolving the matter. He can send emails internally though. I don't suspect there is any issue with the Exchange server since no change has been made to it. The router is a Netopia 2247 nwg. PLEASE PLEASE Any help greatfully apppreciated!

02-25-2010, 12:27 PM	#2
wimiadmin Administrator Join Date: May 2008 Location: Pigeon Forge, TN Posts: 858	I doubt the router has an outbound firewall blocking traffic. Port 25 is outgoing mail (default) so you'll need to investigate why that's being blocked. Is he assigned a static IP via his ISP? Most residential IPs have port 25 blocked unless you are sending mail through the ISPs mail system. Since he's sending mail on his own server, he'll need to make sure that the ISP has his IP in a 'business' group so that port 25 isn't blocked. Since you can send/receive mail internally, then yes, most likely the Exchange server is fine. __________________ Brian Please Search Before Posting

02-25-2010, 04:58 PM	#3
AboveTheLogic Super Moderator Join Date: Jul 2008 Location: Los Angeles Posts: 475	When you say he can send emails internally, do you mean from the LAN--- or do you mean he can only send to internal emails? I'm guessing the former--- but if its the latter then its definitely an Exchange issue (probably just not doing SMTP authentication). Also the story changes if you are using RPC over HTTP (Outlook Anywhere) with Exchange instead of IMAP/POP/SMTP. All signs point to an ISP blocking port 25. Consider setting Exchange to listen on both port 25 and 26 (and do the appropriate port forward of course), and set your clients to send on port 26 instead of 25. __________________ Internet IP vs. Local IP Port Forwarding

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode