Austin
Wed Feb 11 16:52:22 CST 2004
Could it be the issue detailed in Q331062??
Known Issues That Occur When Running ISA Server on Windows Server 2003
a.. When you run ISA Server 2000 and Microsoft Internet Information
Services 6.0 (IIS) on the same computer, you may experience issues with the
ISA Server Web proxy service (W3proxy). By default, IIS listens on all IP
addresses. This prevents W3proxy from binding to port 80 for Web publishing.
To resolve this issue, follow these steps:
1.. Install the Windows Server 2003 Support Tools (included with Windows
Server 2003), and then locate the Httpcfg.exe file.
2.. Run the Httpcfg.exe utility to configure HTTP.sys to stop listening
on all IP addresses. To do this, type httpcfg delete iplisten -i 0.0.0.0 at
a command prompt.
3.. Configure HTTP.sys to listen only on the specified IP address
(usually the internal IP address of ISA Server) by typing httpcfg set
iplisten -i ip-address at a command prompt.
4.. Stop the IIS HTTP service by typing net stop http at a command
prompt.
5.. Stop the ISA Server Web proxy service by typing net stop w3proxy at
a command prompt.
6.. Restart the IIS HTTP service by typing net start http at a command
prompt.
7.. Restart any related IIS services. For example, type net start "World
Wide Web Publishing Service".
8.. Restart the ISA Server Web proxy service by typing net start w3proxy
at a command prompt.
b.. ISA Server digest authentication may not function when it is run with
a Windows Server 2003 domain. On the Windows Server 2003 domain controller,
you have to register Iissuba.dll. By default, this file is not registered on
Windows Server 2003. To resolve this issue, follow these steps:
1.. Start a command prompt.
2.. Type Rundll32 iissuba.dll, RegisterIISSUBA on each Windows Server
2003 domain controller
Anyone????
"Austin" <NoEmail> wrote in message
news:%23i9$iVO8DHA.2556@TK2MSFTNGP09.phx.gbl...
> Hi Group, I have a customer who has a web application that must sit on
it's
> own webserver.
>
> I have tried to publish this website to the outside world, but with no
joy.
> (SBS2003 Premium)
>
> The internal webserver is 192.168.0.3, the SBS 2003 server is 192.168.0.2,
> we have a fixed external IP on a 2nd NIC.
>
> If you
http://192.168.0.3 the website loads internally. The website is in
> the 'default web site' in IIS. The member server is Windows 2000 server.
>
> What are we doing wrong. This member server also acts as an FTP server
which
> works perfectly on the internet though ISA.
>
> Any tips, clues.
>
> Regards
>
>
>