Windows Forum

Ask something
Discussion Locked

Win2k Server and SP3

0 helpful
6 replies

by k.zitko 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm just wondering what issues exist while installing SP3 on a Windows 2000 Server. I have a Win2k domain controller running Exchange 2000. I'm running IIS on the same machine to host Outlook Web Access. Most things are working fine. I have justone problem - the 'www' alias for my primary domain is not resolving properly. I get the default site instead. It has been recommended that I install SP3. Has anybody had a good experience doing this? What has MS done with that 'security roll-uppatch' (the patch of death)? Is it included in SP3? Your input will be appreciated.

6 replies

by quintar51

When you say it's getting to the default site, I'm assuming you mean the 'under construction' page and the iislocalstart.asp.

what you need to do is in IIS, Properties of your website, Documents tab, make sure index.htm is the first one in the list. This will be the starting page for your website.

Regarding sp3, I haven't had any issues with it so far. I also run Win2k AD with Exch2k sp3 and I haven't had any problems.

The IIS security lockdown tool is available to download seperately from MS, I'm pretty sure it's not included in sp3.

for a list of what is being update in windows 2000 sp3, go here
http://support.microsoft.com/support/misc/kblookup.asp?ID=320853

to download the IIS lockdown tool, go here
http://www.microsoft.com/downloads/release.asp?ReleaseID=43955

by k.zitko

Thank you "quintar51"

I want to leave the question open for more input. I'll send your points when the question is closed.

Anybody with additional specific experiences to share will get points too.

by curlergirl

I've run SP3 on all of my Win2K servers (about 10 or so), some with Exchange 2K and IIS on them, and not had any problems at all. I stay away from the security rollup patches and the security wizards in Win2K - I've heard of and experienced too many problems with them - so I can't comment on that. I tend to install security patches separately - concentrating on those I know my servers need. SP3 would include any security patches that have been fully tested by Microsoft up to the point of SP3being published - but I think that was some time late Spring or early Summer of 2002, so there are a lot of individual patches that have been issued since. I would recommend installing Exchange SP3, too, if you haven't done so - I just ran into some problems today that supposedly are fixed by that service pack.

As to the "www" site, your description of the problem is a little vague, but it could be a DNS problem. If your DNS server is internal only, and your web site is hosted externally, you would need to add a host entry on your DNS server to point to the correct IP address of your web site. Otherwise, internal clients will go to the default web site on the internal IIS server instead of to the external web site. On your DNS server, just add a host record for host name "www" (assuming your web site is the same domain name as your internal DNS zone), and put in the correct IP address for that page. Hope this helps!

This discussion is closed to new replies.