Re: OWA problem
- From: "Matthew Tisdel" <MatthewTisdel@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 20 Jun 2005 11:00:04 -0700
WebDav happens inside of port 80 (or port 443 is SSL), so you can't really
open a specific port for it, but many firewalls only allow a certain set of
"safe" http: commands to make it through, and so WebDav is blocked by
default. Maybe look into the "allowed" http commands in the Netgear.
I don't know anything about the Netgear firewalls, but with other firewalls
that I have worked with, the logs might not show anything for denails unless
you tell it to show it. The router may be the same way. However, I would
probably do some pinging from outside the network just to make sure that you
can get there. Try going to the default web site on the server and see if you
are able to get to it, it would not even use WebDav for that.
(http(s)://NewServer)
--
Matthew Tisdel
South Carolina
"Neil Jarman" wrote:
> Hi Matthew,
>
> Thanks for the questions -
>
> 1) my firewall is quite old, and it doesn't have a setting for WebDav - what
> port is this? I can create custom ones.
>
> 2) according to the log, there have been no external hits at all - only ones
> from local machines.
>
> In fact I can't even see a denial or request coming into the router or
> firewall from outside the building.
>
> Does this make sense?
>
> NEIL
>
> "Matthew Tisdel" <MatthewTisdel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:F48F2A92-E735-4766-A955-E53298061363@xxxxxxxxxxxxxxxx
> > Let me know about these things:
> > 1. Many firewalls are set by default to deny WebDav. Check on that with
> the
> > Netgear and check and see if anything else is showing up in the logs of
> the
> > firewall. They are often quite informative on problems like this.
> > 2. Look at the IIS log files on the Exchange server and compare a working
> > and non-working attempt to use OWA. On the Exchange server: go to
> > Start-->Run.... ; Type "logfiles" and OK it; Go to the W3SVC1 folder (The
> > ending number could be different or there may be a number of them--find
> the
> > one with the latest entries); Check in the logfiles for the entries from
> the
> > IP addresses that you are testing from.
> > --
> > Matthew Tisdel
> > South Carolina
> >
> >
> > "Neil Jarman" wrote:
> >
> > > Hi Matthew,
> > >
> > > Just installed a virgin copy of Server 2003 and Exchange 2003 (both
> standard
> > > editions.)
> > >
> > > Firewall is a NetGear FV318 - I have others like it where OWA works.
> > >
> > > Yes, using IE v6.
> > >
> > > NEIL
> > >
> > >
> > > "Matthew Tisdel" <MatthewTisdel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message
> > > news:ADF54FA5-8899-40B7-A1C8-2322C560735F@xxxxxxxxxxxxxxxx
> > > > What version of Exchange are you using? What firewall are you going
> > > through?
> > > > Are you connecting with IE?
> > > > --
> > > > Matthew Tisdel
> > > > South Carolina
> > > >
> > > >
> > > > "Neil Jarman" wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I can't seem to get OWA to work from beyond the building.
> > > > >
> > > > > I have got my router pointing to the server's IP, but still I can't
> see
> > > OWA.
> > > > >
> > > > > Sorry this isn't much info - any suggestions ehich direction to look
> in?
> > > > >
> > > > > Thanks
> > > > >
> > > > > NEIL
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>
.
- References:
- OWA problem
- From: Neil Jarman
- RE: OWA problem
- From: Matthew Tisdel
- Re: OWA problem
- From: Neil Jarman
- Re: OWA problem
- From: Matthew Tisdel
- Re: OWA problem
- From: Neil Jarman
- OWA problem
- Prev by Date: Corrupted Calender items
- Next by Date: Re: Public Folder Replication
- Previous by thread: Re: OWA problem
- Next by thread: OWA PRoblem
- Index(es):
Relevant Pages
|
