Install Web Server on new Server that is not DC 1

[romh]

I have been running a Windows 2000 Adv Server DC, that acts as a web server, database server, mail server and file server. It does everything, DNS, Wins, etc... The DHCP is done by the hardware router. Anyway, I never used to get much traffic at all from the web server, but now, it will be go commercial. So I decided to build a new server machine exclusively to act as a web server.
I have it up and running with Windows 2003 server. I have IIS running and can view the website locally. When I configured the router to forward the HTTP port 80 to the new machine, it still opens up the old web site from the old computer which is the DC.
I know something is very wrong. I dont want to get rid of the original DC computer, I would still like to keep the original DC to act as the database / email / file server. Why is web traffic still going to the original DC? Is it because of DNS? or something else?

Thanks

Please recommend the appropriate network setup. Thanks

 

[porkchopexpress]

Have you tested this on an internal PC or external from your network?

Also just to rule this out have you flushed your DNS cache, IPCONFIG /FLUSHDNS at the command prompt.

 

[romh]

on an internal pc within my network. It is connected to the internal router. I have not flushed anything out. I was looking up some info on microsoft.com. I found this article. Does this apply to what I am asking?

*********************************************
How to install Small Business Server 2003 in an existing Active Directory domain
***********************************************

http://support.microsoft.com/default.aspx/kb/884453/en-us

I did not install Small Business Server, but the article does provide similar usefull info.

Additionally, I instaled VPN server and Terminal Server on the new Windows 2003 Server box, and I can easily use those features. i forwarded the correct ports to that computer, and I can succesfully log on to that machine from home.
Its the webserver that's not responding.

Thanks

 

[porkchopexpress]

I don't think that article will help.

Can you connect to the new website by IP or host name if you bypass the router straight over the LAN?

 

[romh]

Yes, I can connect to the website via its internal address of
192.168.1.4.

 

[porkchopexpress]

How are you connecting remotely are you using a domain name? If so what do you get if you run tracert on that domain name?

 

[romh]

remotely i connect with the ip address that the dsl company gave me. If I use the domain name it does not work. Good point.

 

[Seaspray0]

what are you typing on the internal pc to get to the web page? Check your DNS and see what IP address it is resolving it to.

A+/MCP/MCSE/MCDBA

 

[romh]

on the internal pc i am typing the internal ip address on the web browser. 192.168.1.4

I think it might have somthing to do with the DNS as you say.

 

[romh]

I dont have DNS service installed on the new server 2003 machine. I have DNS service installed on the original Windows 2000 server DC. Should I enable it on the new server 2003 as well?

 

[porkchopexpress]

No but you need to check the DNS on the 2000 DC see if there is an address record for your web site that points to the old IP.

 

[romh]

In the DNS snap in I opened up the forward lookup zones. Under that, is my domain name, I right clicked on properties and went to the name servers tab, and noticed that the server name is there, with its internal IP address. Am I on the right track? Is that what you are referring to? Should I add the new 2003 server DC instead?

 

[porkchopexpress]

Err im not at a server to look so i'll guess here, don't right click the forward lookup zone just open the panel and there should be a list of all PC's and servers in your domain. There should be the name of your webserver under there followed by the IP.

 

[romh]

That worked like a charm. there was an entry for

http://www andthen

the old ip address. I changed it and it worked.
But it worked for when i type in

http://www.domainname.com

in the browser. But not when i simply type
domainname.com


Thanks alot, that was great and simple.

 

[romh]

But I think I might have to configure IIS on the new server in order for it to work without the www. Am i right? That has something to do with the headers. But the strange thing is that it points back to the old server when i open it with
domainname.com

 

[romh]

and I know that i configured the dns zones properly in zoneedit for when users type in www. or without the www.
It used to work both ways, I think it has something to do with what I just fixed, but no other record shows there, inside of the DNS snap in.