Re: FWCTool Reporting HTTP Error 403

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

Don't waste your sanity looking for that file - it doesn't exist until a client has requested it, and then it only lives "on the
wire".
Here is your answer:
http://support.microsoft.com/kb/885683

--
--
Jim Harrison [ISA SE]
Read the help, books and articles!

This posting is provided "AS IS" with no warranties, and confers no rights.

"Ty R. Mote" <TyRMote@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C208BE9D-DFEB-4A43-8422-DB8EFD3DC35F@xxxxxxxxxxxxxxxx
We have been running ISA 2004 SP2 very successfully for months. Then this
morning came...

Everyone has promised me that nothing changed on the ISA box overnight
except for a reboot (twice). This morning, no clients can auto-detect the
server. I manually set them up and everything works great.

I ran the FWCTool to troubleshoot the connection and everything reports
fine: DNS lookup, connected. After connecting, we receive the HTTP Error 403.

I went in to the local network and disabled the option to require all users
to authenticate (which we not only need but have had this configured from the
get-go). After applying the setting, firewall clients immediately detect the
server.

As I mentioned earlier, we are on SP2 and we have also applied the registry
hack as required by a KB article (like I said, this was working fine until
this morning).

The only google result of "wspad http error 403" is an isaserver.org forum
post that was never resolved.

I searched the ISA box for the files ws*.dat and cannot even find where they
reside to check folder permissions. Of course, there is also no way that I
can find to check the built-in webserver for issues with authentication.

The status page is set to monitor AD connectivity and DNS ... all of which
report to be communicating.

Can anyone help me??? Thank you!

--
Ty


.

Relevant Pages

  • Re: Setup all client computer not to access ISA for internet acces
    ... adjusted to fix connection problems to web sites and a proxy bypass is not ... >> And you want the clients not to use ISA and bypass it? ... Now I ran the internet connection ...
    (microsoft.public.windows.server.sbs)
  • RE: continuous ISA timeout error 10060
    ... continuous ISA timeout error 10060 ... I have a leased line connection that goes to a distant ... the clients the browser just keeps loading and loading ...
    (microsoft.public.isaserver)
  • Fix to Connectivity problems after upgrading to ISA 2004
    ... non-functional after upgrading to ISA 2004 on the gateway server. ... Connection denials are being reported in the trace monitor, ... This could be caused by the clients sending inappropriate ... Those clients already configured with this registry key were fine after ...
    (microsoft.public.isaserver)
  • Re: ISA 2006
    ... An 'Allow All Users' rule does not require ISA to authenticate a connection ... ISA will terminate a connection if ...
    (microsoft.public.isa)
  • Re: Clients are authenticated but reports still show only IP addre
    ... I hadn't checked the "Require all clients to authenticate" option on the web ... It's just that the ISA ... server reporting function would only show IP addresses for most users. ...
    (microsoft.public.isa.configuration)