Re: Problems connecting to Exchange 2000 through internet with Out

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Omer maydan (omermaydan_at_yahoo.com)
Date: 07/19/04 

Date: Mon, 19 Jul 2004 21:37:41 +0200

hi. you can check out the following link:
http://support.microsoft.com/default.aspx?kbid=270836

but i must take lanwench side, you should consider other posibillities. your
solution is highly unrecommended! if you don't like the Exchange2000 OWA,
check out exchange2003. i it's premium owa version, it is almost exactly
like an Outlook client, and it is by far more secure... your expanses on the
exchange2003 license, will be lesser by the long run, from the
expenses that arrives from dealing with the security threates and their
circumstances that you create...

"Cyberpastor" <Cyberpastor@discussions.microsoft.com> wrote in message
news:B54DB400-2937-47D5-A19D-30E851D68A7E@microsoft.com...
> Sorry but this is not really an answer. VPN causes an awful lot of network
trafic as our Antivirus will start updating etc. At home this wouldn't be a
problem but on the road this is definately a problem.
> I understand that opening up ports is dangereous (potentially every port
opened is dangerously), however we would like to get full exchange
connections through our firewall. (Could you indicate which port is
dangerous? Only 135? or all of them? Port 5000 is standardly opened by
windows XP, so everyone should have visitors?)
> Does anyone have a clue? Has anyone ever accomplished this?
>
> "Lanwench [MVP - Exchange]" wrote:
>
> > Cyberpastor wrote:
> > > It seems quite simple, but somehow it turns out to be extremely
> > > difficult.
> > >
> > > We have a Small Business Server 2000 running at our office behind a
> > > Hotbrick firewall. Exchange works fine at the office, however we
> > > would like to give our homeworkers the full connectivity to the
> > > Exchange server.
> > >
> > > We can connect from home to the office through the POP and SMTP
> > > protocols, however fullscale connection to Exchange is only possible
> > > through VPN (which works fine). We would like to establish a
> > > connection without the use of VPN as it involves an extra step before
> > > connecting, which some people will forget.
> >
> > Then they will simply have to learn. Do not open up potentially
dangerous
> > ports as you've done - you will very likely have unwanted visitors on
your
> > network before long. If they can't figure out how to use VPN, have them
use
> > OWA. I would close all the ports you've opened up at once and rethink
this.
> >
> > >
> > > So far we have done the following steps:
> > > We have opened port 135 (TCP) on the firewall.
> > > We have opened port 5000 (TCP) for MSExchangeSA
> > > We have opened port 5001 (TCP) for MSExchangeIS
> > > We have opened port 5002 (TCP) for MSExchange NSPI Proxy
> > > We have opened port 5003 (TCP) for MSExchange SRS
> > >
> > > We have entered in all the Registry keys, etc. in order to make the
> > > ports static. We have also entered in the MSExchange/Parameters the
> > > value: "No RFR Service=1"
> > >
> > > At this point we cannot connect through to the server. The error
> > > message we get is that the server should be online in order to work.
> > > The server is online but not reachable.
> > >
> > > Does anyone have a solution or does anyone know a document which
> > > guides you through all the steps and possible problems to setup the
> > > connection to Exchange 2000 through the internet with Outlook
> > > 2002/2003?
> >
> >
> >

Relevant Pages

  • RE: OWA access and security
    ... What I first like to know is what portdoes OWA needs to ... reports Enables internal access to Exchange by OWA and OMA clients. ... - Port 4125 enable external OWA ... 'Outlook Web Access' Web site service from the Internet in the 'Web ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP: security and administrative issues?
    ... I'd still like to know how many people and his speed of the network. ... A lot of you are right, owa works, why change it? ... >> A VPN allows a foreign PC or network into your private IP space, ... >>> consultants ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange + Entourage
    ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange + Entourage
    ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
    (microsoft.public.mac.office.entourage)
  • Re: Exchange + Entourage
    ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
    (microsoft.public.exchange.clients)