Re: Remote access through linux Firewall

Tech-Archive recommends: Fix windows errors by optimizing your registry

I actually have already forwarded HTTP (any port), 4125 and HTTPS
(any port) to the internal SBS server. I tried various connection
attempts with putty and just get connection refused so maybe there is
a problem with the firewall config, but I believe at one point I was
receiving an error page "unauthorized to view this page" and something
about my IP address being denied. I am going to get more specific with
the firewall rules so hopefully that will get me back to the
unauthorized issue. Once there what would be my next step?



"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:O4acMQY4GHA.3644@xxxxxxxxxxxxxxxxxxxxxxx
Port 80 is not required.

"ALeghart" <aleghart@xxxxxxxxx> wrote in message
news:1159285637.705668.187680@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
IIRC, using the firewall for NAT to the LAN server, TCP ports 80,
443,
and 4125 are required for RWW (Remote Web Workplace).
--
Alan Leghart

Gaius wrote:
I have an SBS 2003 server sitting behind a Redhat Firewall.

I need to allow a couple users remote access to their exchange
mailboxes. What is the best way to do this. I opened up https on
the
firewall and forwarded requests to the SBS server.

When I type in https://localhost on the server I get the "welcome
to
windows small business server 2003" page and can then click on
the
remote web workplace link and can then log in and access outlook
web
access, works perfectly. So how do I get it to work externally
for my
laptop users?

TIA





.

Relevant Pages

  • Re: RWW with no https
    ... I do not consider a:8080 a url that is appropriate for a SSL end user connection. ... So just so we are all clear, RWW HAS to go over HTTPS. ... Even if I do https but port 8080 would not matter ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook Vs Outlook Anywhere
    ... My _opinion_ is that if users are too lazy to remember httpS they should not be allowed to connect. ... Regardless, you don't need to open port 80 for Outlook RPC, as you're configuring that to use https anyway, and once configured, the user doesn't have to worry about the connection settings. ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook Vs Outlook Anywhere
    ... This guy at my company was going on about opening port 80 and I didn't really like the sound of that, that's why I stuck with the CEICW and sought your views/recomendations. ... He kept talking about Outlook over http...I kept saying to him " you'll be talking about 'rpc over https then' "? ... Regardless, you don't need to open port 80 for Outlook RPC, as you're configuring that to use https anyway, and once configured, the user doesn't have to worry about the connection settings. ...
    (microsoft.public.windows.server.sbs)
  • Re: cannot access windows update when behind a firewall (was Re: IE in XP cannot connect to Windows
    ... >which is the router and though which we share one high speed connection. ... Yes, port 443. ... You should see a connection on 'https' similar to the following: ...
    (microsoft.public.windowsxp.network_web)
  • Re: cannot access windows update when behind a firewall (was Re: IE in XP cannot connect to Windows
    ... >which is the router and though which we share one high speed connection. ... Yes, port 443. ... You should see a connection on 'https' similar to the following: ...
    (microsoft.public.windowsxp.general)