Re: ISA2004 SP2: EventID 14148

In SBS the external accessible websites are configured to listen on "(All
Unassigned)" IP addresses and TCP port 80. Host header resolving is used to
resolve external website names. Only thing changed is the default website
that has been disabled (for security reasons). I can't understand why I have
to use a second server (with the costs of an additional Windows 2003 Server
license).

Nowhere in the documentation on the web is told that I MUST use two seperate
servers when publishing websites. Like many products the information for
requirements lack this kind of information. I'll kick the resellers ass and
tell him that all sold product do not comply with my requirements (also
bought a HP USB DAT72 which doesn't seem to be compatible with ARCserver
r11.5 although they are in the HQL on the websites of CA and HP).

Thanks for your replies and thinking with me... Too bad the problem can't be
solved.


Jeroen



"Ori Yosefi [MSFT]" <oriy@xxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:%237inLCNUGHA.1444@xxxxxxxxxxxxxxxxxxxxxxx
I'm not really sure how it is configured on SBS. I guess that IIS is
listening on one NIC / IP address and ISA is listening on a different one.

You can try to configure it this way.

HTH,

Ori.

--
Please do not send email directly to this alias. This alias is for
newsgroup purposes only.This posting is provided "AS IS" with no
warranties, and confers no rights.


"Rotzooi" <rotzooi@xxxxxxxxxxxx> wrote in message
news:Odv5WjlTGHA.6084@xxxxxxxxxxxxxxxxxxxxxxx
Yes, there is only one server running both IIS 6.0 and ISA 2004 SP2 (and
Exchange 2003 SP2).

What I was wondering about, is that it does work on Small Business Server
2003 SP1, but not on a server installed with the seperate applications.
Big question is how to get this working on just one box (I started my own
small company with a little budget, so there isn't room for seperate
servers. But I did buy seperate products keeping future expansion in
mind. I hope to do this as soon as it pays off running my own business.
Meanwhile I need to solve this problem)




"Ori Yosefi [MSFT]" <oriy@xxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:uPmcQnaTGHA.4792@xxxxxxxxxxxxxxxxxxxxxxx
Are you running both ISA and IIS on the same machine? If so, then they
are both "competing" for the use of port 80.

HTH,

Ori.

--
Please do not send email directly to this alias. This alias is for
newsgroup purposes only.This posting is provided "AS IS" with no
warranties, and confers no rights.


"Rotzooi" <rotzooi@xxxxxxxxxxxx> wrote in message
news:%23R4VXUGTGHA.5924@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I've used a webserver quite a long time using one NIC and a hardware
router, IIS 6.0 and host headers. My router broke down, I upgraded to
SDSL with a Cisco 828. I added a second NIC that has a public IP and
connects to the Cisco, e.g. NIC=218.188.188.188 and the
GW/Cisco=218.188.188.187. No firewall is active on the Cisco and all
ports are passed through.

I created a rule so LAN users can access the internet through the ISA
2004 server/proxy. This works fine. However, if I create a web server
publishing rule, I'mnot able to access the websites from the internet.
A-records are correctly setup by the provider.

The firewall reports the following error when starting:
The Web Proxy filter failed to bind its socket to 218.188.188.188 port
80. This may have been caused by another service that is already using
the same port or by a network adapter that is not functional. To
resolve this issue, restart the Microsoft Firewall service. The error
code specified in the data area of the event properties indicates the
cause of the failure.

MS Knowledge Base says it has something to do wih ports that are bind
by another service. Most likely it is IIS. But why doesn't this work
well. I checked all settings and rules from reference SBS2003SP1 server
and there are no thing different for web server publishing (HTTP only)
and IIS.



Jeroen










.

Relevant Pages

  • Re: Add a new DC to a new branch
    ... A Cisco router serves as DHCP server ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add a new DC to a new branch
    ... Did you solved the problem about booting the server in Directory Services ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Port 25 redirection w/ Barracuda
    ... I would suggest that you change this and consider using Outlook over HTTP...should resolve the issue. ... the server, since the Barracuda is receiving all SMTP traffic. ... port, but any mail sent via it is never received. ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA remote login issue
    ... >The first time I tried to login I typed in the IP address with the new port ... I found that I was able to connect to one of our Internal websites ... >which is hosted on a test bed server by just entering the IP address. ... Subsequent logins have been able to go directly to the Exchange ...
    (microsoft.public.exchange2000.admin)
  • Use of host headers fails after 4 hours
    ... There a 3 websites hosted in total. ... If I reset the server, all works fine for about 4 hours. ... defined in the host headers of the websites no longer respond. ... port 80, customer.mydomain.com, ...
    (microsoft.public.inetserver.iis)