RE: SBS 2003, ISA 2004
- From: v-edtian@xxxxxxxxxxxxxxxxxxxx (Edward Tian)
- Date: Thu, 13 Oct 2005 02:00:25 GMT
Dear Ze'ev:
Thanks for your update. I have received your mail and I am glad to hear the
OWA is working now. :-)
Since you received the original error message "The Web Proxy filter failed
to bind its socket to 192.168.16.2 port 80/443" again, it appears that both
ISA and IIS try listening on these two ports.
There are four reasons which may cause this issue:
1. Socket Pooling.
As I mentioned before, to disable Socket Pooling, we can also perform the
steps in this KB article:
813368 IIS 6.0: Setting Metabase Property DisableSocketPooling Has No Effect
http://support.microsoft.com/?id=813368
2. Generally speaking, by default the Web Proxy is listening on port 8080
of the local network adapter. Can I assume that you have changed the proxy
listening port from the default TCP 8080 to 80? Please go to the ISA 2004
management console, navigate to Configuration->Networks->Internal, double
click it and go to the Web Proxy tab. Please double check if the HTTP port
is 8080 and the option "Enable SSL" is UNCHECKED.
3. By default the Web Listener (Not the Web Proxy) is listening on the
external network adapter. By checking your ISA info, the setting is
correct. To double confirm, please navigate to Firewall Policy, on the
right pane, click Toolbox->Network Objects->Web Listener, and double click
the "SBS Web Listener", go to the Network tab, ensure only the "External"
option is checked in the list and the status is "The default IP address on
the ISA Server computer in the selected network".
4. The problem may also caused by anti-virus application. If you have any
anti-virus software installed on the ISA Server, please temporarily disable
them.
Meanwhile, please also check the binding order of the two network cards:
1. Open the Network Connections, click Advanced->Advanced settings.
2. Double check if the Local NIC is the first order and the External NIC is
listed under the Local NIC.
Please also check all the Web Sites in IIS Server to make sure they are all
listening on the local network card other than the external network card.
In addition, if the web sites are working well, you may safely ignore the
alert message since it may be caused by third-party web based applications
in some cases.
Hope the above information helps. Please feel free to let me know if there
is anything I can do for you.
Have a nice day! :)
Best Regards
Edward Tian(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Ze'ev Ionis" <z.ionis@xxxxxxxxx>
| Subject: SBS 2003, ISA 2004
| Date: Sun, 9 Oct 2005 23:26:33 -0400
| Lines: 17
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| X-RFC2646: Format=Flowed; Original
| Message-ID: <uxtRrpUzFHA.156@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: d141-37-132.home.cgocable.net 24.141.37.132
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp1
3.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:211581
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Everything is installed, and seems to be working. But ISA reports
message
| "The Web Proxy filter failed to bind its socket to 192.168.16.2 port 80"
and
| again for port 443. Per the knowledge base article
| http://support.microsoft.com/default.aspx?scid=kb;en-us;888650 I can make
| this message go away by changing my web sites, and especially my default
web
| sites, away from ports 80 and 443 (e.g. to 9180 and 1443). Then I do not
| get this message, and once I configure the proxy rules I can access the
| login site "mydomain.com/exchange" to access OWA. However, upon signing
in,
| instead of getting directed to the web outlook mail page, I receive an
error
| something along the lines of this port not recognized for SSL (most
servers
| use 443). I do not see where I can change this.
|
| Help!! Should I change the IIS ports, or change ISA, or ???
|
| Ze'ev
|
|
|
.
- Prev by Date: Re: Can't access public folders from System Manager, SBS 2003
- Next by Date: Re: Basic firewall/ISA
- Previous by thread: RE: SBS 2003, ISA 2004
- Next by thread: RE: How to add a user with very limited rights
- Index(es):
Relevant Pages
|
