Re: Help. Loss of OWA and SPS access via Internet after ISA 2004 u

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



Not really. Is ISA logging anything in the application log about this? I
do get app log errors for certain misconfigured web sites, but I haven't
seen any case where they prevent access to the site.

The other thing you can do is go to the ISA monitoring. Try to visit the
site in question from a specific workstation. Then on the server, query ISA
for that workstation's IP address for the last x time period (the shorter
the better - ISA logs a mountain of data). Hopefully the log will tell you
specifically what's happening.


"ACK" <elee@xxxxxxxxxxxxxxxx> wrote in message
news:F32CC945-3DB6-45F2-BB87-0AD8458CB41C@xxxxxxxxxxxxxxxx
Thanks Dave. Any thoughts on why certain actions in MOSS 2007 now result
in
the following error message:

"This error (HTTP 500 Internal Server Error) means that the website you
are
visiting had a server problem which prevented the webpage from
displaying."

This was not an issue until upgraded from ISA 2000 to ISA 2004 SP2 on the
SBS Server.

Thanks.

"Dave Nickason [SBS MVP]" wrote:

Strange - the CEICW should configure all of that for you. But anyway,
glad
to hear it's working.


"ACK" <elee@xxxxxxxxxxxxxxxx> wrote in message
news:AD002C35-EF0F-4143-8B24-6A717FCD5055@xxxxxxxxxxxxxxxx
I think I may have fixed the problem.

MOSS: I created a web publishing rule pointing to my SharePoint server.
Selected the "Forward Original Host Header" option. Chose "SBS Web
Listener."
Added my FQDN as the "Public Name."

OWA: I added my FQDN as the "Public Name" to the SBS OWA Web Publishing
Rule.

This worked fine prior to the install of ISA 2004, so I am a little
disappointed that it didn't transfer correctly with the upgrade.

"Dave Nickason [SBS MVP]" wrote:

Did you remember to re-run the CEICW after you upgraded to ISA 2004?


"ACK" <elee@xxxxxxxxxxxxxxxx> wrote in message
news:BB1D31C2-7D83-4C99-921C-3014F7DAF1C5@xxxxxxxxxxxxxxxx
I just ran the SP1 upgrade from ISA Server 2000 to ISA Server 2004. I
am
no
longer able to get to OWA or a SharePoint Portal 2007 website using
my
FQDN.

https://fqdn/exchange used to take me to OWA which is hosted on my
SBS2k3
Server.

http://fqdn used to take me to my SharePoint Portal which is located
on
its
own server.

This stopped working when I installed ISA 2004 from the SBS SP1 CDs.
If
I
use the NetBios name of the server in place of my FQDN, then both
OWA
and
SharePoint Portal work fine.

I'm sure to start fielding some angry calls any second, so thanks
for
any
help on this!









.



Relevant Pages

  • Re: odd owa issue
    ... Since you access the OWA from external thru ... On the SBS 2003 Server open the Server Management console. ... Please open the ISA management console, ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP Issues. Very strange
    ... default order of rule in ISA 2004. ... Windows SharePoint Services intranet site, ... server certificate on Web server name column and then click Next. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS VPN setup?
    ... The 2-nic configuration is used when the SBS server will *also* act as your network's firewall. ... You purchase 2k3 PREMIUM and that comes with ISA to handle the firewall duties. ... To compare apples to apples, let us assume there is a network setup as I outlined above...and the firewall appliance is an ISA server, such as those available from Celestix. ...
    (microsoft.public.windows.server.sbs)
  • RE: ISA access rules, help
    ... please let me know whether you're using ISA 2000 or ISA 2004 ... (SBS SP0 or SBS SP1). ... the ISA server will not be used as a proxy server. ... Since SBS already used port 80, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Advice Please
    ... Notice that the netgear router will be infront of ISA. ... Javier [SBS MVP] ... > SQL server as it is the protected patient data. ... >> always keeps a copy of the profiles (even if you are using roaming ...
    (microsoft.public.windows.server.sbs)