Win2k Adv Serv DNS

Use a router to interconnect the 2k box and the rest of the network. Then use a relay point on another server to administer DHCP

Someone, can you please extrapolate on this, becuse I am short on time, unless you dont need it

OK, gonna try again, Running Win2k Adv Serv on one machine. This machine is connected to the internet via Cable modem that has me connected with DHCP. I have a Win98 Machine that I would like to log into a domain on the server. If I try to install DNS on the server, I loose my internet connection. How can I set up the server so that I can run DNS and have a domain for the other machine to log into and gain access to the net thru the server?

I have the same setup at home. As the previous answer mentioned, you should get a router. I use a D-Link 704. The WAN goes into the back and is dynamically assigned by my IP. My PC's connect to the front side of the router which is a switch. The router itself does DHCP on the internal side of the network that helps with the configurations. You don't have to allow the router to assign IP addresses, but if this functionality is built in, use it. It cost about $80. If purchasing a router is not an option you can use W2K's NAT capabilities. It will require two cards in the server. This is also a very viable solution and works very well. Hope this gives you some workable options. Good luck!!!

Norm

How do you have your network set up? Do you have a router or a switch pluged into your cable modem? If so which one? You really do not have to have anything set up in DNS if you have a linksys router or something along that line because it can handle all this problems that you are having. If you do not have one of these routers you cable provider should have DNS servers to which you can reference in your PCs.

I don't have any router or switch right now. going to try to invest in one soon, but for now, all I have is a HUB connection the two PC's, Part of what I am looking for is some security on the server as well. I thought Someone once told me that I can connect the server with my cable modem to the network, and internally have my own Domain and some how assign it its own internal IP's. does that make any sense ?

Okay, let's try this to put it all together.
1. You will need a cable/DSL router to pull this off. There are several on the market that will work. Most will also act as a firewall.
2. Your physical connection will essentially look like this: cable modem <--> cable/DSL router <--> hub <--> computers.
3. Your configuration will essentially be as follows:
On the router, set the WAN side (from ISP) to accept DHCP info from the ISP. Make note of ISP's DNS server(s) IP address. On the LANside (your internal network), do not set the router to act as a DHCP server. Your router will also act as the gateway for your local network.
I'm assuming you are using Active Directory. AD must have access to a DNS server which allows dynamic updates (most ISP DNS servers do not). Therefore you will need to set up a local DNS server to service your private network. Also since you want to use DHCP (which requires a fixed IP address), I would setup both DHCP and DNS on your Win2K server. Make sure you assign IP addresses in the private IP range for your DHCP scope. Give your Win2k server a fixed IP address in this range and have the server point to itself for the primary DNS. Also set up DHCP to point to your local DNS server. Once you have DNS set up, set it to forward to the ISP's DNS server.
What all this in effect causes to happen is the following: when a client submits a DNS query, it will go to your local DNS server first. If the query can be answered by the local DNS (queries involving all your local resources), nothing will go to the ISP's DNS server for resolution. If the query can't be answered locally (all queries involving the Internet), it will be forwarded to the ISP's DNS server for resolution.

This question was auto closed due to inactivity