Re: Connecting to Exchange Part II

Ethon:

I re-read the original thread, and as I said back then, the ping issue would be unrelated. I'm glad you solved it, but the smarmy response about you asking and "nobody" helping you will not endear you to anybody here.

As far as RPC over HTTPS, based on your initial post, it appeared that you had done some 'customizing' of the default IIS website. At that time, I recommended you ensure that the RPC virtual directory existed. This is *essential* in RPC over HTTPS. In none of your replies since (nor any now) can I see anywhere that you've checked this. So that is where I'd start...

-Cliff

"Ethon Bridges" <ethonbridges@xxxxxxxxx> wrote in message news:2008070317405975249-ethonbridges@xxxxxxxxxxx
Okay. I can login with OWA over the internet. Still having the same ongoing issue. Cannot connect to the Exchange Server with Outlook over the internet. Error is that "the name could not be resolved". Name resolves with Explorer to get to OWA, server responds to pings on the name and IP.

So we don't go round and around again:

There is no device to block ports at this time, so port forwarding is not necessary on some external device.

NAT has been turned off, basic firewall is on. I have opened one port in the firewall for a remote desktop sharing program that I use and that works fine.

One of my previous questions here that nobody would answer was how to make my server respond to pings. Figured that one out on my own thank you.

SMTP is on in the firewall.
HTTPS is on in the firewall.
RWW was not on. Not sure why this is required as we are not using RWW, but turned it on anyway. No effect on the problem.

ISA is not being used.

Anything else I should be checking?



On 2008-07-02 17:57:28 -0500, "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> said:

Ethon Bridges <ethonbridges@xxxxxxxxx> wrote:
There is no NAT or filtering. The ISP passes through everything for
us to deal with. The SBS is basically hooked straight up to a public
IP at this point. Firewall device will be installed shortly.

Then "shortly" is when you ought to connect this network to the Internet.
Don't do so without a good firewall! You're running with scissors. It takes
only nanoseconds to get attacked/exploited.

Here's what I did to get it to work: disabled the LAN interface.
Turned off the Window's firewall, then re-enabled it. Now everything
is responding. This leads me to believe that something in SBS
firewall was wacky.

Now onto the next minor (I think) problem in another thread....



On 2008-07-02 15:37:56 -0500, "Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> said:

Ethon Bridges <ethonbridges@xxxxxxxxx> wrote:
The first thread was entitled "Connecting to Exchange...".

Ah. But this isn't a web forum, it's a newsgroup - so it doesn't
make any difference what you'd put in the subject line; it won't
show up right next to your "part II" unless the timestamp was
immediately prior.

It's a fresh install. Nothing has been tried because I have been
told it should work out of the box. As for what errors, well, I
guess a "page cannot be displayed" error in Explorer when trying to
access the server. When trying to connect with Outlook, it just
says "The connection to the Microsoft Exchange Server is
unavailable....".

Did you enable them both in the CEICW? Do you have the correct port
forwarding configured in your ISP's router?

SMTP: TCP 25
HTTPS: TCP 443
RWW: 4125

(for starters)

If you can access OWA via HTTPS then both should work. If you can't,
there's your problem.

So, maybe we should back up a step. During install, I don't recall
there being any option to NOT install both NIC's on the SBS server.
The installer sees them and wants to try and configure one for
internal and one for external. If I could just configure one, that
would be fantastic as we are not using anything on the LAN for SBS.

OK - disable one in the BIOS or in device manager, and rerun the
CEICW ...and I would suggest that you have the ISP disable NAT and
filtering in their device, and use your own good firewall appliance
between you & the Internet. I personally like sonicwalls.

I'm still not clear what ISA is,

http://www.microsoft.com/isaserver/default.mspx

and there wasn't any option during
installation to install or not install it, enable or not enable it.

ISA is something you'd have only if you had SBS 2003 Premium & had
manually installed it...




On 2008-07-02 10:17:17 -0500, "Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> said:

Ethon Bridges <ethonbridges@xxxxxxxxx> 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.

You haven't posted any of your original (part I?) in here so I
don't know what you've tried yet, what troubleshooting steps & what
symptoms/ errors. That said, unless you use ISA you do not need two
NICs - and if you aren't using ISA you need a *good* firewall
appliance. I'm not a fan of the two NIC config in general on any
DC. Please include more info.


.

Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS VPN setup?
    ... And if you have a hardware firewall you haven't flashed in years they just got in through a exploit. ... SBS plugs into a switch with the other computers and the switch is plugged into a firewall appliance with 2-nics. ... To compare apples to apples, let us assume there is a network setup as I outlined above...and the firewall appliance is an ISA server, such as those available from Celestix. ... > learn and test the RWW solution before deploying it. ...
    (microsoft.public.windows.server.sbs)
  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS VPN setup?
    ... The 2-nic configuration is used when the SBS server will *also* act as your network's firewall. ... You purchase 2k3 PREMIUM and that comes with ISA to handle the firewall duties. ... To compare apples to apples, let us assume there is a network setup as I outlined above...and the firewall appliance is an ISA server, such as those available from Celestix. ...
    (microsoft.public.windows.server.sbs)