Win2K Server + IIS w/ Cable?

[St. Babu]

Hey, any networking genius out there want to help me out with planning/implementing a web server using IIS 5 on Win2k? I can't seem to figure out how to configure my DNS server for this, and as such, having a registered domain does no good! Can anyone walk me through it?


:D

[Rosco]

Saint,

What problems are encountering with DNS?
And what web server help do you need?

I am a partner in a small hosting company and am fimilar with IIS and 2000 DNS, so I may be able to help.

[Matt615]

I am knowledgeable about IIS so if you need help there just post your questions. :)

[St. Babu]

OKY...

So hypothitcally, My WAN IP is 77.22.65.102. My domain is registered as www.setupthis.com

Okay, internally, I've got everything set through a Linksys BEFR series router. All machines pull their IP's from DHCP (Can I even do this for the DNS server?). The gateway on the router is 192.168.1.1.

So what do I set the forward and reverse lookup zones to? I think I've figured out the whole IIS thing. And while we're discussing this, do I stand more of a chance of ISP detection running a DNS server on my LAN than I would simply running an HTTP server and having an outside DNS server route to me?

Thanks a lot for the help, guys!

[BOWTYE8]

Babu,
you sound like you want to run somthing close to what I have setup.

I have 2 pc's both running win XP thru a befsr41 router via DSL. one is my daily net surfer the other host my website.

I have a dynamic IP so I use a the TZO service to forward my IP addy with a domainname.(eg.=http:/yoursite.tzo.com)


I let the router handle the dchp= With the linksys the addys usually start at 192.168.1.100 =server pc
192.168.1.101-surfin PC.

under the linksys admin I port forward 80 for Http to this dchp addy eg. forward port 80 for 192.168.1.100......This will let port 80 open to the net. otherwise the linksys firewall will block it.

Then on your PC you want to run as a personal web server you will have to run IIs with your site.

Some problems that occur for me time to time is hte router acts up and does not let port 80 pass thru. even in DMZ mode all ports open to the net. The system then usually needs a full reboot.

I would start off by running IIs on your server PC. Then try pining that PC with your IP. Your website should appear. If not try setting it up with out the router. Connect that PC directly to the net via cable or DSL modems find your IP. Run IIs , then ping your IP. you should see your site .

I am no expert...just what has been working for me. I am not too familiar with manually setting up DNS etc....

bowtye

[St. Babu]

Yeah, that's more or less what I have running right now. The problem with that is that I can't have FTP or Mail service from that server. I registered a domain name, and right now, it's just forwarded and I use the service's DNS servers, so I can only host web. I want to put a DNS server on my network so I can host whatever I want.

Thanks for answering, though!!
St. B

[balad99]

My setup is something similar but I have far many machines on the Internal LAN so I have the DNS server and an Win2k Active Directory Domain. I guess if you are talking about just a couple of systems DNS server is'nt really required (you could rely on your ISP's) but if you must - it doen't harm to have one.
I can give you a background on how I have it setup. My PDC is native Active Directory Win2k Adv Server and the DNS services are running on it in Active Directory enabled mode. All my systems have Static IP's (I don't rely on the router for anything other than access in and out), The DNS server has all the entries for my local lan (dynamicaly updated) and in the "forwarders" section I have a whole bunch of External DNS server entries -starting with my ISP's and some others. This setup resolves all internal names from its own database and any requests for an external site are forwarded to one external DNS server. Over time the cache locally has most of the entries so resolving is very efficient. This is the only type of setup (that I can think of) you could probably have, because the internal DNS cannot replicate its data to the outside world since its only private range and replicating it down from the outside world means a certain external DNS server needs to be configured as a replicating and zone transer partner to your internal one - which is all up to your ISP whether they would do it. As far as IIS, you could have running on any system and have the appropriate port opened for that IP. On side note I think a static configuration internally would be more opt since I have found it less troublesome, specially since there are only a couple of systems involved - Buts thats your choice - Hope this helps.