Re: SBS2003 behind router on private IP - Setup MX - Exchange
- From: <workinghard@xxxxxxxxxxxxxx>
- Date: Sun, 28 May 2006 11:27:45 +0200
Hello or "gday mate",
A quick response on this sunday morning. You don't need POP to "to pop mail
in Outlook
from private or public IPs" POP is the "Post Office Protocol" used to
retrieve mail. You don't need it to either send or retrieve mail when your
mail clients can use MAPI or IMAP. I'm not saying that you can't use it but
it is not required.
Some ideas/questions:
For your external OWA Access. Your router deals with HTTP en POP you say but
what about HTTPS (for SSL == port 443)? Is SSL configured? Did you use the
CEICW wizard?
Try an nslookup against servername.dom.com ... what do you get?
Enable IIS logging and try to access the OWA then get to the IIS log:
1. Open IIS MMC, right click Default Web Site and then click Properties.
2. Click Website tab and then check Enable logging.
3. Stop the Default Website and rename the existing IIS log files under
C:\WINDOWS\system32\LogFiles (helps to see the newly created log entries
seperated from the log files).
4. Restart the Default Website
5. Try to reach OWA a couple of time and then go have a look at the IIS
logs.
Do you have one NIC in the SBS 2003 Server?
Cheers
.
- References:
- SBS2003 behind router on private IP - Setup MX - Exchange
- From: learndotnet
- SBS2003 behind router on private IP - Setup MX - Exchange
- Prev by Date: SBS2003 behind router on private IP - Setup MX - Exchange
- Next by Date: RE: Cannot connect computer to domain
- Previous by thread: SBS2003 behind router on private IP - Setup MX - Exchange
- Next by thread: Re: SBS2003 behind router on private IP - Setup MX - Exchange
- Index(es):
Relevant Pages
|
