Re: Email Issue with SBS2008

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Cliff, I've already started to head down that exact same path.

1. I have hooked up a laptop directly to the cable modem and set the same
static IP information. I then tried a Telnet session and it worked.... OK
Comcast is getting ruled out now.

2. I rehooked the Sonicwall, verified the firewall settings for port
traffic and tried again not only from a workstation but the server as well.
(Original setting had only the server with outbound port 25 traffic allowed
but I opened it up more). Same problem at server and workstation.
Connection could not be established.

3. I turned on all log monitoring at the Sonicwall and checked logs.
NOTHING in their about denied connections for port 25. (very confusing
part). I am going to try and temporaily replace the Sonicwall with a cheap
router and see how things look. I'm going to do that tomorrow morning.

4. Since refused telnet connections are happening at the server and
workstation (plus no information in the logs about a refused connection) I am
leaning toward the firewall and something not right there. Just in case I
powered down/up the sonicwall but still the same.

Let's see what I find tomorrow morning.

"Cliff Galiher" wrote:

We may be stumbling down a blind alley at this point though.

As LanWench indicated, we need to know why you can't send yet. As far as I
can tell, *nothing* as been verified.

If it were me, I'd say a trusty laptop hooked directly into the cable modem
and a telnet test would be my first stop.

No server. No domain. No firewall. No "rules" to figure out. Just verify
if this is even a Comcast issue.

Then, if that works, move behind the firewall. Laptop to Watchguard LAN
port (crossover cable if necessary, depends on model) and cable modem to
watchguard WAN port. Re-do the test.

walk your way back until telnet stops working. Once you know that, you know
the culprit.

-Cliff


"Ace Fekay [MCT]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OvfEJFNPKHA.1280@xxxxxxxxxxxxxxxxxxxxxxx
"Richard K" <RichardK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:15E743EE-04F7-489C-8BF9-CD4367EADCB7@xxxxxxxxxxxxxxxx
Ah, some good points Ace. The SBS and Watchguard may be configured
correctly
but Comcast is stopping port 25 traffic hence my telnet open port
failures.
I'm assuming by default that SBS uses 25 so that is the way I configured
the
firewall for allowing outbound 25 from the server. As I said everything
was
working fine then all of the sudden it stopped working for outbound mail.
Comcast could be the culprit?

I did speak with their tech support (this is business class btw) and they
were the ones who told me use smtp.comast.net as the address for setting
up
the smarthost. They also told me about the 587 port but I don't see
where to
change it Exchange. All I see are the inbound info. I configured that
via
SBS wizard and all of the retry queues wrapped themselves up into the
comcast
queue.... but they are just sitting in the queu and not sending.

thoughts?

-Richard K

My thoughts are that you call them back and tell them you do not want to
send through their servers. Tell them it was working, and now all of a
suddent is stopped. Sending through their servers is not an option for a
business. You need and DESERVE a full explanation of why it is now being
blocked. It's business class, therefore you have the right to send it
directly.

I would rather not see you do this. You will get more issues with sent
mail in your business recipients' Junk mail folder. You'll be posting back
with a question asking why mail you are sending out is not being received
or landing in your recipient's junk mail folder. Believe me, I went
through this with Comcast in the past with someone.

If you really want to change the Send connector port, the easiset way is
with a PowerShell command.

Set-SendConnector -identity "<name of send connector>" -Port:<port number>
Then restart the Transport services on the server.

Then you have to go to Org, Hub, Send Connector, right click the send
connector, properties, Network tab, choose "Route Mail to the Following
Smart Host," and type in "smtp.comast.net " (without the quotes).

Ace







.

Relevant Pages

  • Re: Dynamic IP, dyndns.org, and RWW
    ... After firmware is updated, re-run CEICW, enable the firewall, select your ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... The port forwards on the Linksys for 443/3389/4125 only need to ... receives fine, cannot send?, Deleted POP3 connector emails, ...
    (microsoft.public.windows.server.sbs)
  • Re: Dynamic IP, dyndns.org, and RWW
    ... Merv Porter [SBS-MVP] ... Ethernet adapter Server Local Area Connection: ... The port forwards on the Linksys for 443/3389/4125 only need to be ... receives fine, cannot send?, Deleted POP3 connector emails, tried ...
    (microsoft.public.windows.server.sbs)
  • Re: Frage zum Smarthost
    ... Nun - jeder virtuelle Server sendet nur auf einem Port, ... Mit einem virtuellen Server über einen Connector auf das Faxgateway nach ... Port 25 zu senden und über einen anderen Connector auf den anderen Smarthost ...
    (microsoft.public.de.exchange)
  • Re: Will Exchange using nonstandard port cause problems with Sharepoint?
    ... the email server in Sharepoint administration. ... >about changing the std outbound port of Exchange. ... >alternated Connector for sending out mail. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Access to SBS 2000 Server
    ... >From outside your network, can you telnet to your public IP on port 3389? ... >>> I have a small business server w 2 NICS. ... >>> connected to cable modem, ...
    (microsoft.public.windows.server.sbs)