Can't connect to Exchange

Still can't connect to Exchange over the WAN. LAN access works fine.
To recap what was learned from previous thread on this subject:

Dual-NIC server. One configured for LAN, one for WAN. WAN port has no
router/firewall in between and is configured with a public IP. Public
IP has a DNS entry for convenience. Access by name or IP fails.

This is a fresh install of SBS with no configuration changes as of yet.
As stated before, we only need Exchange capability from remote
laptops. There is nothing on the LAN that will use SBS.

This really shouldn't be this hard, yet I am still fighting it.

Ethon Bridges <(E-Mail Removed)> wrote:
> Still can't connect to Exchange over the WAN. LAN access works fine.
> To recap what was learned from previous thread on this subject:
>
> Dual-NIC server. One configured for LAN, one for WAN. WAN port has
> no router/firewall in between and is configured with a public IP. Public
> IP has a DNS entry for convenience. Access by name or IP
> fails.
> This is a fresh install of SBS with no configuration changes as of
> yet. As stated before, we only need Exchange capability from remote
> laptops. There is nothing on the LAN that will use SBS.
>
> This really shouldn't be this hard, yet I am still fighting it.

Hi - I replied to your identical post in the SBS group (which is the best
place to post this anyway). In the future, please don't multipost - if you
need to post to multiple groups, it's best to crosspost instead, by posting
a single message to a handful of relevant groups (separate the NG names with
commas) so that everyone can follow the thread. Multiposting wastes
everyone's time, including yours, and may lead to your actually getting
*less* help rather than more.

See http://www.blakjak.demon.co.uk/mul_crss.htm

On 2008-07-02 10:18:52 -0500, "Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> said:

> Ethon Bridges <(E-Mail Removed)> wrote:
>> Still can't connect to Exchange over the WAN. LAN access works fine.
>> To recap what was learned from previous thread on this subject:
>>
>> Dual-NIC server. One configured for LAN, one for WAN. WAN port has
>> no router/firewall in between and is configured with a public IP. Public
>> IP has a DNS entry for convenience. Access by name or IP
>> fails.
>> This is a fresh install of SBS with no configuration changes as of
>> yet. As stated before, we only need Exchange capability from remote
>> laptops. There is nothing on the LAN that will use SBS.
>>
>> This really shouldn't be this hard, yet I am still fighting it.
>
> Hi - I replied to your identical post in the SBS group (which is the best
> place to post this anyway). In the future, please don't multipost - if you
> need to post to multiple groups, it's best to crosspost instead, by posting
> a single message to a handful of relevant groups (separate the NG names with
> commas) so that everyone can follow the thread. Multiposting wastes
> everyone's time, including yours, and may lead to your actually getting
> *less* help rather than more.
>
> See http://www.blakjak.demon.co.uk/mul_crss.htm

Sorry about the "multi-post". I only posted it on the networking side
after I re-read the original thread on the SBS side and someone said I
should be posting here. Now you're saying post over there. Seems I
can't win today, both in posting and getting the server to work. I'll
limit my responses to the SBS group on this issue.

Ethon Bridges <(E-Mail Removed)> wrote:
> On 2008-07-02 10:18:52 -0500, "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com> said:
>
>> Ethon Bridges <(E-Mail Removed)> wrote:
>>> Still can't connect to Exchange over the WAN. LAN access works
>>> fine. To recap what was learned from previous thread on this
>>> subject: Dual-NIC server. One configured for LAN, one for WAN. WAN
>>> port has
>>> no router/firewall in between and is configured with a public IP.
>>> Public IP has a DNS entry for convenience. Access by name or IP
>>> fails.
>>> This is a fresh install of SBS with no configuration changes as of
>>> yet. As stated before, we only need Exchange capability from remote
>>> laptops. There is nothing on the LAN that will use SBS.
>>>
>>> This really shouldn't be this hard, yet I am still fighting it.
>>
>> Hi - I replied to your identical post in the SBS group (which is the
>> best place to post this anyway). In the future, please don't
>> multipost - if you need to post to multiple groups, it's best to
>> crosspost instead, by posting a single message to a handful of
>> relevant groups (separate the NG names with commas) so that everyone
>> can follow the thread. Multiposting wastes everyone's time,
>> including yours, and may lead to your actually getting *less* help
>> rather than more. See http://www.blakjak.demon.co.uk/mul_crss.htm
>
> Sorry about the "multi-post".

No worries.

> I only posted it on the networking side
> after I re-read the original thread on the SBS side and someone said I
> should be posting here. Now you're saying post over there.

Yeah - SBS is its own beast, and SBS questions are best left in that group,
even if you also need to x-post elsewhere.

> Seems I
> can't win today, both in posting and getting the server to work.

;-) My sympathies.

> I'll
> limit my responses to the SBS group on this issue.

Yep - I replied in that thread, as did someone else.