Re: IIS (on SBS 2k) default website stopped 'address already in use'
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Wed, 18 Jan 2006 08:54:27 GMT
Hi Justin,
Thanks for your update. I am glad to know that things are getting fine now.
I appreciate your time and effort to the issue.
To configure automatic update, you need ensure you have install WSUS on the
server box properly and configure the following settings on the ISA server.
I. Please refer to the following article to ensure install WSUS in the SBS
server box properly:
WSUS on SBS
http://wsus.editme.com/WSUSonSBS
More information:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/WSUS/
WSUSReleaseNotesTC/4244109a-395a-4ff8-9989-ea55ab0964a3.mspx
II. To allow the automatic update, we need to configure the following
settings on the ISA server:
Step 1: Create a destination set for Windows Update domains
-------
1) Open the ISA Management console.
2) Expand ArrayName, and then expand Policy Elements.
3) Right-click Destination Sets, click New, and then click Set.
4) In the Name field, type Windows Update, and then click Next.
5) Click Add.
6) In the Domain field, type *.download.microsoft.com.
7) Leave the Path field blank, and then click OK.
8) Repeat steps 5) through 7) to add other 3 domains, and then click OK.
Step 2: Create an anonymous Site and Content rule for Windows Update
requests.
-------
1) Open the ISA Management console.
2) Expand Access Policy.
3) Right-click Site and Content Rules, click New, and then click Rule.
4) In the Name field, type Windows Update, and then click Next.
5) Click Allow, and then click Next.
6) Click Allow access based on destination, and then click Next.
7) In the Apply this rule to list, click Specified Destination Set.
8) In the Name list, click Windows Update.
9) Click Next, and then click Finish.
Step 3: Create an anonymous Protocol rule for Windows Update requests
-------
If your existing protocol rules require authentication
(user/group-limited), you will have to create an anonymous protocol rule
for HTTP and HTTPS. To do this, follow these steps:
1) Open the ISA Management console.
2) Expand Access Policy.
3) Right-click Protocol Rules, click New, and then click Rule.
4) In the Name field, type Windows Update, and then click Next.
5) Click Allow, and then click Next.
6) In the Apply this rule to list, click Selected protocols.
7) In the Protocols list, click HTTP and HTTPS, and then click Next.
8) Click Next two times, and then click Finish.
Additionally, if you would like client to use Automatic Update (AU) to get
the updates from Windows Update web sites, both of the following conditions
must be matched:
1. AU client only supports Auto-Discovery web proxy server. It means that
AU client will NOT go through the proxy server that you have configured in
Internet Options | Connections tab | LAN Settings button. If you want the
AU clients to access Windows Update web sites through the ISA, you must
configure the WPAD to deploy auto-discovery proxy settings. To do that,
please refer to the following KB article:
309814 How To Configure Firewall and Web Proxy Client Autodiscovery in
Windows 2000
http://support.microsoft.com/?id=309814
816320 HOW TO: Configure Firewall and Web Proxy Client Autodiscovery in
Windows 2003
http://support.microsoft.com/?id=816320
296591 A Description of the Automatic Discovery Feature
http://support.microsoft.com/?id=296591
Note: We recommend you use DNS to enable auto-discovery. If you want to
use DHCP, please also check the following KB article:
307502 "Automatically Detect Settings" Does Not Work if You Configure DHCP
http://support.microsoft.com/?id=307502
2. Since AU client is running on the Local System account, you must
configure the Protocol Rule and Site and Content Rule to allow Anonymous to
access the following Windows Update web sites and use the HTTP and HTTPS
protocols:
*.download.microsoft.com
*.windowsupdate.com
*.windowsupdate.microsoft.com
windowsupdate.microsoft.com
More detailed information can be found in the following KB article (Windows
XP SP2 uses Windows Update Version 5):
885819 You experience problems when you access the Windows Update Version 5
Web site through a server that is running ISA Server
http://support.microsoft.com/?id=885819
If your enterprise policy doesn''t allow the Anonymous outgoing web
request, a workaround is to configure Automatic Updates service to be
running on the user account that has the permission to access the above
Destination Sets and protocols in Service MMC. To do that:
1. Run Services.msc to open Service MMC.
2. Double click Automatic Updates service, click Log On tab, click to
select This Account, type the account name and the password, and then click
OK.
3. Repeat Step 1 and Step 2 to configure the settings on every client.
Since this workaround needs to configure settings on every client, this
will lead to the large administrative tasks and we do not recommend you do
that.
Hope above information helps! I am happy to be of assistance to you-)!
Have a nice day!
Sincerely,
Jenny Wu
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: "Justin Bell" <justinbell@xxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>Subject: Re: IIS (on SBS 2k) default website stopped 'address already in
use'
>Date: Tue, 17 Jan 2006 16:00:28 -0000
>Organization: freedom2surf
>Lines: 181
>Message-ID: <dqj4ak$bd2$1@xxxxxxxxxxxxxxxxxxxxx>
>References: <dpmpo5$u70$1@xxxxxxxxxxxxxxxxxxxxx>
<RPaFLLQFGHA.3680@xxxxxxxxxxxxxxxxxxxxx>
>NNTP-Posting-Host: i-83-67-79-124.freedom2surf.net
>X-Trace: news.freedom2surf.net 1137513620 11682 83.67.79.124 (17 Jan 2006
16:00:20 GMT)
>X-Complaints-To: abuse@xxxxxxxxxxxxxxxx
>NNTP-Posting-Date: Tue, 17 Jan 2006 16:00:20 +0000 (UTC)
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfe
ed01.sul.t-online.de!t-online.de!solnet.ch!solnet.ch!news.clara.net!valentin
..news.clara.net!peernews.inweb.co.uk!news.freedom2surf.net!not-for-mail
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:237355
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Thanks Jenny
>
>You are correct in your assumptions. I had got down to the fact that some
>other process must be using port 80. I have however solved the problem. I
>had ISA server set to publish auto discovery info (presumably on port 80)
>and when i disabled it the default web site starts just fine.
>
>It would be nice to have the functionality to do both things but the
default
>website is much more important than being able to auto discover the proxy
>server for the rare occaision where we have a roaming wireless laptop in
the
>office.
>
>Many Thanks
>
>Justin
>
>""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> wrote in message
>news:RPaFLLQFGHA.3680@xxxxxxxxxxxxxxxxxxxxxxxx
>> Hi Justin,
>>
>> Thank you for posting here!
>>
>> I am sorry for the delayed response due to weekend. Please understand
that
>> the newsgroups are staffed weekdays by Microsoft Support professionals to
>> answer your systems and applications questions. Your understanding is
>> greatly appreciated!
>>
>> From your description, I understand the issue to be: the default web site
>> can not be started and received the error "address already in use". If I
>> am
>> off base, please don't hesitate to let me know.
>>
>> The error is caused by another process has occupied the same IP & Port
>> which is configured to your Default Web Site.
>>
>> Please check the setting in Default Web Site Properties->Web Site.
>> If you have never changed the ip and port configuration, the default
>> setting should be:
>>
>> IP: (All Unassigned) TCP port: 80 -> 0.0.0.0 80
>>
>> Type the following command in command line to check:
>>
>> netstat -an
>>
>> If the output contains:
>>
>> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
>>
>> or
>>
>> TCP %some available ip%:80 0.0.0.0:0
LISTENING
>>
>> then it is definitely some process has occupied it yet.
>>
>> I recommend you use the PortQuery utility to find out the details about
>> which process is occupying it. You can go to the following link to get
the
>> tool.
>>
>>
http://www.microsoft.com/downloads/details.aspx?FamilyID=8355e537-1ea6-4569-
>> aabb-f248f4bd91d0&DisplayLang=en
>>
>> If you can notify which process is occupying the port 80, please try to
>> disable it or uninstall it and then test to see if the issue be fixed.
And
>> also you can give the portquery output to me for analyze.
>>
>> Additionally I would like to clarify that we need Re-run CEICW (server
>> management console -> Internet and E-mail -> connect to the internet) to
>> refresh the network connection if you change network connection type or
>> hardware. Please also re-run CEICW to refresh the network connection.
>>
>> It is recommended you take a look at the following KB article to get
>> detail
>> steps to configure network connection:
>>
>> 825763 How to configure Internet access in Windows Small Business Server
>> 2003
>> http://support.microsoft.com/?id=825763
>>
>> Hope above information helps! I am happy to be of assistance to you and
>> look forward to your reply!
>>
>> Have a nice day!
>>
>> Sincerely,
>>
>> Jenny Wu
>> 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: "Justin Bell" <justinbell@xxxxxxxxxxxxxx>
>>>Newsgroups: microsoft.public.windows.server.sbs
>>>Subject: IIS (on SBS 2k) default website stopped 'address already in use'
>>>Date: Fri, 6 Jan 2006 22:08:07 -0000
>>>Organization: freedom2surf
>>>Lines: 32
>>>Message-ID: <dpmpo5$u70$1@xxxxxxxxxxxxxxxxxxxxx>
>>>NNTP-Posting-Host: i-83-67-79-124.freedom2surf.net
>>>X-Trace: news.freedom2surf.net 1136585285 30944 83.67.79.124 (6 Jan 2006
>> 22:08:05 GMT)
>>>X-Complaints-To: abuse@xxxxxxxxxxxxxxxx
>>>NNTP-Posting-Date: Fri, 6 Jan 2006 22:08:05 +0000 (UTC)
>>>X-Priority: 3
>>>X-MSMail-Priority: Normal
>>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>>>X-RFC2646: Format=Flowed; Original
>>>Path:
>>
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfe
>>
ed01.sul.t-online.de!t-online.de!solnet.ch!solnet.ch!news.clara.net!valentin
>> news.clara.net!peernews.inweb.co.uk!news.freedom2surf.net!not-for-mail
>>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:234713
>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>
>>>Hi All
>>>
>>>Hope someone out there can help me,as I am no tech guru!
>>>
>>>I manage a small SBS network (1 server, 12 workstations) it all works
very
>>>well and in general is easy to manage. However, a couple of months ago on
>>>the regular reboot (and on every reboots since), the default website
>> failed
>>>to start and when I tried to restart it I got the message 'address
already
>>>in use'. The default website will start if I change the port from 80 to
>> 81,
>>>but that is no use for my AV (which were installed over port 80 and hence
>>>configured that way!) clients which I am having to manually update at the
>>>moment!
>>>
>>>I have scanned everything with 3 varieties of AV software and countless
>>>spyware detectors and according to all that it is clean of virii and
>>>spyware. Could something else be 'getting first dibs' on port 80 leaving
>>>poor old IIS out in the cold?
>>>
>>>The only change to the network at about the same time, was in the
internet
>>>connection and hardware firewall. I went from a two-way satellite set up
>>>with firewall and sattelite modem to ADSL with a Netgear prosafe firewall
>>>and d-link dsl-300T adsl modem, could this be causing the problem?
>>>
>>>I have not been able to find any MS KB articles to cover this, but maybe
>> I'm
>>>just not asking for the right thing!
>>>
>>>looking forward to your replies
>>>
>>>Justin
>>>(thecheeseguru)
>>>
>>>
>>>
>>
>
>
>
.
- References:
- IIS (on SBS 2k) default website stopped 'address already in use'
- From: Justin Bell
- RE: IIS (on SBS 2k) default website stopped 'address already in use'
- From: "Jenny wu [MSFT]"
- Re: IIS (on SBS 2k) default website stopped 'address already in use'
- From: Justin Bell
- IIS (on SBS 2k) default website stopped 'address already in use'
- Prev by Date: ISA Server (2004) detected routes through adapter "External" that do not correlate with the network element to which this adapter belongs. The address ranges in conflict are: 192.0.0.192-192.0.0.192;. Fix the network element and/or the routing table
- Next by Date: RE: FAX service - Unknown fatal error on certain inbound
- Previous by thread: Re: IIS (on SBS 2k) default website stopped 'address already in use'
- Next by thread: Re: External RWW access
- Index(es):