Re: Still can't connect to RWW or OWA remotely

Also go to IIS then Click on Websites and expand it. Then go to Default
Website and expand it.

The right click on the Remote directory and choose properties.

Go to Directory Security and Click on Authentication and access control
Make sure that you have a check in Enable Anonymouse access
Click Ok

Then Click on IP Address and Domain Name Resolutions
Make sure that Granted Access is selected.
Click Ok
Click Ok Again

Then Right Click on the Exchange Folder and choose properties.
Go to Directory Security Then Click on IP Address and Domain Name
Resolutions
Make sure that Granted Access is selected.
Click Ok
Click Ok Again

Then run your test after you have the routers DMZ set.

Let me know how that turns out.

Neadom

Leon Willard wrote:
Neadom - here's our installation:

The server is a SBS2003 SP1 Standard box without ISA, using the two NIC
configuration. Broadband is an Efficient 5800 Series DSL modem-router with a
4-Port switch set up with a static IP from our (AT&T) ISP. The NIC #1
(external WAN) has a fixed IP address192.168.254.10, and connects to the DSL
router 4-port switch.

DHCP is handled by the server, and the #2 NIC (internal LAN) uses fixed IP
192.168.16.2. This NIC connects to the LAN 24-port switch along with all
workstations. -- The laptop was plugged into the Efficient 4-port switch.

This installation worked as expected once it was set up -- that is, all
workstations have Internet access, Exchange server handles the email, and
all users are able to connect printers, files, and other resources.We could
access features like RWW and OWA internally, but not remotely. As you can
see, Merv has been a big help on diagnosing some of these problems step by
step.

Here's where we are right now. If I try to check the bindings on either of
the two NICs by clicking the Advanced tabs, it won't open that box, and
instead pops up this message: "Windows Firewall cannot run because another
program or service is running that might use the network address translation
component (Ipnat.sys)".

This turns out to be a bogus message. Windows Firewall is disabled. So
something else seems to be seriously wrong. Your comment, "To me it sounds
like a routing issue. Because your request to the server is not being
answered", is probably correct. But what is causing it? And what's causing
these network cards to be so goofy?

Leon


<neadom@xxxxxxxxxxxxxxxxxx> wrote in message
news:1159565036.401754.157850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Leon can you give us your network topology?

For Example

Internet>Modem>Router>Switch>SBS Server

Or

Internet>Modem>Router>Switch>SBS Server Internal Nic
Internet>Modem>Router>SBS Server External Nic

What sort of provider do you have coming in? DSL/Cable or T1?

Is the Modem also your Router? If not what type of Router? If your
using DSL is the Modem acting as a bridge or is it doing the PPOE Auth?

Where is the mix are you connecting your laptop? From inside the
network or outside the network.

To me it sounds like a routing issue. Because your request to the
server is not being answered.

Thanks
Neadom Tucker
Kotori Technologies, LLC


Leon Willard wrote:
Whoa! -- The ipconfig /all stuff I cut and pasted into my response looks
ugly now, and with too much space in between lines. It was formatted
using
courier, and looked OK before I hit the Send button.
Is there a better way to do it?
- Leon





"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uxNfmoc3GHA.3492@xxxxxxxxxxxxxxxxxxxxxxx
Hi Leon,

Could you please post an ipconfig /all for the SBS server and for a
workstation?

When you ran CEICW, did you select "a direct broadband connection",
enable
the firewall, select the services, select the Web Services, enter your
Public IP address for the web server certificate, then finish the rest
of
CEICW?

Also, try taking the router out of the equation...

Attach a laptop that's configured for a workgroup (not a domain) to a
free
port on the router. Give it a static IP address of 192.169.254.x, a
Subnet Mask of 255.255.255.0, and a Default Gateway of 192.169.254.10
(the
LAN IP address of the router). Then try to RWW into the SBS server.
If
you're successful, the router configuration is the problem. If not,
you're SBS server config (or the external NIC) is having a problem.

--
Merv Porter [SBS-MWP]
============================
"Leon Willard" <leonwill@xxxxxxxxxxx> wrote in message
news:Os4g8zb3GHA.5092@xxxxxxxxxxxxxxxxxxxxxxx
To update my problem from what is stated below: I followed the advice
I
received from serveral people on this newsgroup, and opened ports 443,
444, 4125, 1723 and 3389 in our Efficient 5861 DSL router, and AT&T
verified port 25 was open.

But I still couldn't connect remotely using https://publicIP/remote.
So I
called Efficient tech support to have them verify that the ports I
specified were actually opened. Their tech told me he couldn't telnet
into our router through our public IP to check. And he couldn't ping
that
IP either. He asked what method I used to forward the ports using
telnet
(it's <system addserver [private IP for server] tcp port number> which
I
took from their app note), and he said I was doing it correctly. After
that I reran CEICW to verify all Web services were checked.

But I still could not connect remotely. So it would seem that I've got
something cofigured wrong, or something not yet configured. Also,
Adaptec
wanted to connect to our SBS to update some drivers, but were not able
to
connect. They asked me to connect to their site remotely from our
server,
and I wasn't able to do so. However, I was able to connect to their
site
from a workstation on our network. So it seems our SBS is still the
source of the connection problems. And once again, I'll appreciate
your
help on this. Thanks.

Leon



I recently completed an installation of SBS2003 Standard without ISA
using
the two NIC configuration. At the front of the external 'WAN' NIC is a
DSL
router set up with a static IP from our ISP. This external NIC IP
address
is
192.169.254.10 Our ISP (SBC) also provides us five additional static
IP
addresses which we don't use. The internal (LAN) NIC is using IP
192.168.16.2. We also have a website hosted by SBC, but we don't use
it's
registered name or IP address for our SBS2003 network configuration.
(except
as mentioned below for a certificate).

From inside the network, all users can access RWW and Exchange just
fine.
And the rest of the network and email works fine for all users also.
Our
problem is that we cannot connect to RWW or OWA from the Internet.
When I
try to connect using https://certificate/remote I always get the
"Cannot
find server or DNS Error" message.

I have run CEICW a bunch of times and haven't gotten any errors. I
have
assumed that the problem is the certificate I am generating. I have
tried
using server.registered website name, but it doesn't work. I have also
used
the DSL public side IP address/remote, and that doesn't work either.
It's
pretty clear that I don't know how to fix this problem, and any help
will
be
greately appreciated. Thanks.







.