Still can't connect to RWW or OWA remotely

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.



.

Relevant Pages

  • Re: Hacked?
    ... have some kind of pointer to try to contact a computer on that network. ... Those are NetBIOS ports, and NetBIOS is somewhat chatty and can generate ... installing Zone Alarm on the computer in question would be ... > currently hosting the email server, DNS, as well ...
    (microsoft.public.security)
  • Re: IIS / Web Services Security threats
    ... You will be surprised to know, due to a recent virus attack on the perimeter network, the common ports have been closed too. ... I also develop Java applications which runs on weblogic server. ... Since, the entire world knows about port 80 and 443, I thought opening a specific port with IP Sec configuration may make the network little secure. ... My security team thinks allowing communication between the two IIS ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Getting around corporate firewalls to access ssh server
    ... the ports on the two servers and put the release server on 22. ... restrictive of what the users are allowed to do with the network. ... For those customers where you are having problems, ...
    (comp.os.linux.networking)
  • Re: When do I choose for OUTBOUND or INBOUND in a protocol?
    ... Ori YosefiISA Server Team ... > tab I only checked the external network. ... >> If you want to allow access to iSpQ on the internal network, you should>> create a publishing rule that publishes these ports to the external> network. ...
    (microsoft.public.isa)
  • Re: When do I choose for OUTBOUND or INBOUND in a protocol?
    ... Regarding INBOUND and OUTBOUND. ... The usuall meaning of INBOUND is when you have a server in your "internal" ... network, usually being NATed, that ... defines the ports used by the application and then creating a publishing ...
    (microsoft.public.isa)