Link to home
Start Free TrialLog in
Avatar of darahood
darahoodFlag for United States of America

asked on

Configure intranet on MS Server 2000

I have been tasked with setting up an old server running Server 2000 pro as an intranet server to be shipped to another location.  I have gone round and round but can't seem to get the browser to see the site even though I have configured dns and iis.  

This is far out of my area of expertise so any help, preferable detailed (or a working link), as to how to set it up.  Most links have either not gotten me anywhere or are MS links and microsoft no longer supports 2000.

In an ideal world, I would just upgrade to 2008 but that isn't an option right now.
Avatar of Brad Howe
Brad Howe
Flag of Canada image


1. Confirm DNS is correct. Open CMD and type the following

   Does this resolve the proper Server IP?

2. Open Internet Services Manager. from the Tree, Select SERVERNAME\Your Website. Right click and select Properties. Open the Web Site Tab, Web site Identication , Advanced. confirm you are running IP Address (All unassigned)_, TCP Port 80 and Host Header Name (Empty).

3. Craete a simple test.html file and save it in your web root. Attempt to browse locally http://localhost/test.html

4. check the Logs for the site in default location (C:\WINNT\system32\Logfiles\W3SVC\....) if it is enabled. If not enable it and try again.

5. Are you run a firewall? Some network protection software.

Let us know,
Avatar of darahood


DIdn't get me there.  With nslookup I get "Cant find server name for address ...."

Feel like I am beating my head against the wall!
If at all possible, is it possible to go from the initial "Active Directory" setup?
. IIS doesn't require AD to install. It is done through add/remove programs windows features.

Is IIS installed?  Do you have access to manager?

OK, so I have been going about this incorrectly...  I can install iis that way (just nuked it so I could start from scratch).

Do I also need dns?
Not on the web server. If this is network then dns should already be on place. Just start with IIS install ad then try to broswe using a hostile entry.

OK, with iis installed (dns is not), I can access the site from a browser on the server.  Trying to access it from a pc, it does not see it.   Is this what you meant by a "hostile entry"?

I will install dns and try again.
Yes, a hostfile entry on your local PC Host file is to simple test that your bindings are setup properly. #where is your internal serverIP.

In the local PC hostfile to bypass DNS and load the site for now.

1. Where is this server to be hosted?
2. Is it internal or external?
3. Do you not have a DNS server in the office?


NOTE: DNS should not be installed on a WEB Server. DNS is a inrastructure service that is usually installed on separate internal servers, DC's or separate External servers.

If the host file works, IIS is installed and working. .NET framework will still need to be added if the site requires it.

What are you trying to do here?
Back to basics.  This is a stand-alone server for an intranet application.  I have to set it up here (as well as some pc's) to ship it to another office out of the area.  

Right now, because it is connected to our local system, it is assigned an IP address.  Obviously, this will go away when I disconnect it to make it stand-alone.  Something tells me that is where it will get a bit more tricky and I need something else installed... right or wrong?  and if right, what else?
That is fine. Intranet is internal meaning that the remote office should have it's own internal DNS Server.

If so, then all you need to do is create a A record for to point to the new internal server IP.

The host entry just removes DNS from the mix to ensure you set it up properly. - It is only a test.

Does this new Office have AD? Do they have a DNS Server?

It's out of the country but I don't think they have anything at the moment.  As far as I know, this is the only server of any kind.  They have a few old pc's that only access the internet.
Ok, are they run Active Directory? - Hades666
I don't believe so.  
Ok then,

If it is only a small office, and under 10 PC's and you are not going to use AD, I would suggest leaving it in WORKGROUP and simply using the url http://Servername or http://server.ip.addr . If you really want a domain name, you could also just add it to their workstation host file and it will work via http://server.ip.addr. Having a DNS service for just 1 url and no AD is really a waste of resources in my honest opinion.


That makes sense to me.  One additional question... in order to modify the hosts file, the server will have to be connected first, its IP gotten via ipconfig and then the hosts files modified on all the pc's...

Is that a valid assessment?
Avatar of Brad Howe
Brad Howe
Flag of Canada image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I'd love to be able to do that... problem is no one there is savvy enough to get me the range.  In addition, part of the pc's are here and part are already there.

It will be a challenge enough just to get someone to get the IP and then edit the hosts file to add the line needed there.

Pretty sure we are good now.  Thanks for the assistance.
Not a problem. Post a comment if you have issues. Cheers, Hades666