Re: Will Exchange using nonstandard port cause problems with Sharepoint?
From: Kevin Weilbacher [SBS-MVP] (kweilbacMVP_at_gte.net)
Date: 10/04/04
- Next message: Troy Murray: "Re: DNS Time-out error"
- Previous message: dan kim: "Re: Clients cannot access Internet through Win 2003 SBS"
- In reply to: Sean: "Re: Will Exchange using nonstandard port cause problems with Sharepoint?"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Will Exchange using nonstandard port cause problems with Sharepoint?"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Will Exchange using nonstandard port cause problems with Sharepoint?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 4 Oct 2004 17:26:27 -0400
Sean,
First you say you would "hate to change anything", but then go on to talk
about changing the std outbound port of Exchange.
;-)
IMHO, doing what Frank suggested has far less impact and will provide an
immediate indication if this fixes your problem, rather than going down the
path you want to take. And you can do this in baby steps!
First, open up ESM, drill down to Connectors, where you will find the
'SmallBusiness SMTP Connector'. If you right click on this object, and then
click on Properties, I would suspect you will find the option 'Use DNS to
route to each address space...' selected.
Go ahead and Cancel this window, then right click on 'Connectors', and
select New > SMTP Connector. What we are going to do is to setup an
alternated Connector for sending out mail. You will need to know the name of
your ISP's outgoing email system, and the master accountid and password for
it (especially if they required outgoing authentication'.
For example., I user Verizon for my DSL/Internet acess, and theiur outgoing
email system is simply: outgoing.verizon.net . So, first I named my new SMTP
connector 'Verizon', and then I clicked on the 'Forward all mail option' and
in the box below I listed 'outgoing.verizon.net'.
Next, click on the Advanced tab, then Outbound Security, , then Basic
Authentication, --- and then fill in your master accountid and password for
your ISP's mail account.
Finally, click on the Address space tab. Here you can list specific email
address domains of people you send email to. Let's say, for instance, you
have several friend with AOL addresses. So click on Add > SMTP and enter:
aol.com
Once you close this connector, you have told Exchange--- alright for
outgoing email to anyone with an AOL email address, use my ISP (Verizon'
connector, for everyone else, use my default SmartHost connector.
Then send one of your AOL buddies an email and see if it works. If it does,
then do the following --- delete the new SMTP connector you just created, go
back to the SmallBusiness Server SMTP connector, and switch it from Use DNS
to Use SmartHost and reenter your ISPO info as you did before.
-- Kevin Weilbacher [SBS-MVP] "The days pass by so quickly now, the nights are seldom long" "Sean" <anonymous@discussions.microsoft.com> wrote in message news:3c0201c4a9b8$edfdb400$a601280a@phx.gbl... > Thanks for the response Frank, it may very well be > outbound only. However, the mail setup we use now with no- > ip works very well, and I hate to change anything if I > don't have to. > What I'm more interested in is whether setting Exchange > to listen to a different port will cause problems with > Sharepoint alerts. We're having a problem with that now & > this is the only thing I can think of. > I tried entering the mail servername and the port in the > 2 sharepoint administration web pages, but still have > trouble (servername port). > I haven't been able to verify that the Sharepoint setting > will recognize the extra parameter of the port. I'm > afraid this is going to take longer to figure out than > I'd hoped. If you have any further ideas, I'd appreciate > hearing them. > Sean > > >>-----Original Message----- >>Hi Sean >> >>Are you sure the ISP is blocking 25 inbound or just > outbound? Most ISPs >>blocking 25 block outbound which affects sending but not > receiving. To test >>telnet to your mail.FQDN 25 from outside your network > and see if your server >>connects. If outbound only you can use Smarthost or SMTP > on another port >>using a third party like mailhop outbound from > dyndns.org. >> >>-- >>Frank McCallister SBS MVP >>COMPUMAC >>"Sean" <anonymous@discussions.microsoft.com> wrote in > message >>news:261a01c4a9a6$9b594280$a301280a@phx.gbl... >>> We need to have Exchange listen to a port other than 25 >>> due to ISP blocking port 25. Will this cause problems >>> with Sharepoint alerts? I haven't been able to verify >>> this, buit I expect it will. If someone has run into > this >>> problem, please share. >>> Sean >> >> >>. >>
- Next message: Troy Murray: "Re: DNS Time-out error"
- Previous message: dan kim: "Re: Clients cannot access Internet through Win 2003 SBS"
- In reply to: Sean: "Re: Will Exchange using nonstandard port cause problems with Sharepoint?"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Will Exchange using nonstandard port cause problems with Sharepoint?"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Will Exchange using nonstandard port cause problems with Sharepoint?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
