error deploying on server 2003 (domain controller)

cannot find localhost page

[evanheld]

I am trying to deploy a website on windows server 2003. The site is written and runs fine both locally on my XP Pro box and also out on my personal domain (I deployed it there for testing.)

I have created the virtual directory and placed my files on the 2003 server. I have created and granted the ASPNET account the rights it requires on the wwwroot folder. (There is a bug in the Framework 1.1 that forces you to set up the ASPNET account yourself when using a domain controller to host your site. See [support.microsoft.com...] for details.)

Here's my problem. After copying my files to the virtual folder I try to access the site from the server using [localhost...] folder name]/default.aspx and I get the error "Page cannot be found." All settings and directory structures match my XP box.

I'm baffled. Anyone have any suggestions?

Thanks,
evanheld

[korkus2000]

Do any of the pages work? What happens if you hit the folder without the default.aspx?

[plumsauce]

what happens when:

-- trying 127.0.0.1 instead of localhost
-- pinging localhost

[evanheld]

Answers to questions:

1)I can ping the localhost (address returned is 127.0.0.1)

2)I still get a Page not found when I reference the address without the default.aspx (Http://localhost/[virtual folder name])

3)When I access \\127.0.0.1 I get a folder view which displays the netlogon, Office, Shared, sysvol, and scheduled Tasks folders

[plumsauce]

ok, it seems localhost is resolving ...

btw, i meant [127.0.0.1...] not \\127.0.0.1

so, what happens if you goto [127.0.0.1...]

forget the vdir for the moment.

[evanheld]

I get a logon dialog box (in which I entered Administrator (and pasword.))

I get the "Team Web Site" home page, (windows sharepoint services)

[plumsauce]

good, this implies that your web server is at least
working.

at this point i would be looking at the vdir setup.

try setting up a mapping for your site to a
directory that is local to the server and
putting a file in there. then browse for that.

btw, if you already have a web site on the box,
ie, "Team Web Site", you will need to set up
host headers. (see help file)

and to test, if you do not yet have dns setup
for your new site, then you will need to setup
a hosts file to let you resolve by something
other than ip address or localhost.

set a host header for your site to www.example.com

set a host file entry for www.example.com to the
ip address of your server on the client machine,
preferably another machine

[evanheld]

I can't thank you enough, that worked like a charm!

One last question for you. We are bringing a T1 line in here and when I'm ready with the site I will be taking over the web site from EarthLink (who is currently hosting their website, email, and ftp.) When the T1 is installed, I will have a static ip address(s). At this point, I would just change the Host Header info and the Host file to match. Am I correct in thinking that?

Thanks again,
evanheld

[plumsauce]

At this point, I would just change the Host Header info and the Host file to match. Am I correct in thinking that?

almost. the host file thing was just for testing
name resolution. you will need to have your dns
entries setup to point whatever host name you are using
in the host header to the ip address assigned to the
outside ip address of the server. you may also
need to deal with split horizon dns to be able
to reach the server from inside. the alternative
is to use a different host name for inside networks.

DO NOT FORGET TO SECURE YOUR SERVER BEFORE CONNECTING
WITH THE OUTSIDE WORLD

[evanheld]

As far as securing the server, this is what I have done. (Realize I'm a programmer, not a network engineer.) I have created three internal security roles on a windows server 2003 network, only one of which has any significant rights. I have enabled the built in firewall on the server. The web application will run as a Domain User, and that's it. Although the web app will make inserts into a sql database, it will not do any updates or deletes. (The SQLDataAdapter for the web app is only configured for inserts and selects.) I do client side validation and on the server side I have also secured the fields on the insert(s) to guard against SQL injection attacks.

Do you think I need extra firewall software to protect sensitive files on the server?

[plumsauce]

what you have already done is a good start.
however, the subject of server security
could go on for many pages.

there are whitepapers on building secure iis
servers at ms.

your alternative is to have an expert configure
those aspects of the system that you are
uncomfortable with.