DHCP and Internet Access 4

[Genimuse]

Sorry for the basic question, but no amount of searching here or Googling seems to provide me with what I need to know.

I'm helping manage a small network, a dozen workstations and a server. So far we've just had Win2k Pro on all of the machines and have handled security and logons and such on a machine-by-machine basis (there are also a couple of Win 98 machines running legacy apps). A Linksys DSL router provides DHCP service for every computer.

Now I'm installing Win2k Server on the server. I've spent the week trying to make things work, but have had no real success.

So my basic question (finally!) is this: Does the Win2k server need to be providing DHCP for the workstations now, instead of the router, in order for them to be part of the domain?

Also, the organization has a domain name, with their website hosted on a shared server somewhere else. I have no interest in bringing the website in-house, but am confused about what domain name to use for the internal network? Should I use the same domain name, and somehow set up the DNS so that requests to

http://www.theirdomain.org

automatically go outside the network, or should I uses a ficticious domain inside, or... sorry, I just don't understand how this is supposed to work.

(And I'm feeling especially dense as I have two books on Win2k Server and still can't grasp these basics.)

Thanks in advance for any help you can provide.

 

[Genimuse]

I am thrilled to report that, thanks to the help of all of you, I've managed to get DHCP working correctly.

Unfortunately, I suspect due to DNS problems, I'm unable to get any of the workstations to log into the domain -- they indicate that they can't find it.

My domain is clinic.local. Setting up a user with the name, say, Bob, and then running the Network Identification Wizard on the workstation using that info results in it failing to find the domain.

On the server, running the manual test (simple and recursive query, both) works fine. Is there something special I need to do on the workstations besides running that wizard?

And again, thank you for your patience.

 

[buddafish]

from a client machine, if you right click my computer --> properties --> network id tab --> properties, is the machine part of a domain? or still in a workgroup? if not in domain, attempt to join the domain here. i would be logged onto the local machine as the local admin. if this fails, run an ipconfig on the client machine and verify that you have a valid IP address, Subnet Mask, and DNS server listed. Can you ping the DNS server. When a W2k client boots, it needs to locate a local (subnet) DNS server to find SRV (service) records that will allow it to locate a logon server, ect.

No DNS --> No Dice.

scottie

 

[basst]

In your DHCP scope are you issuing DNS and a Default gateway addresses to the clients? Also, on the W2K server it needs to point to itself for DNS.

 

[Genimuse]

Thanks again, you guys pointed me in the right direction yet again. Somehow I had not provided a DNS address in DHCP. Now that I've resolved that, things seem to be sort-of working.

However, DNS still isn't right. If I perform an nslookup on from a workstation authenticated by the server, I get this (for example):

[b]nslookup google.com[/b]
*** Can't find server name for address 192.168.1.202: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.1.202

Non-authoritative answer:
Name:    google.com
Addresses:  216.239.57.99, 216.239.37.99, 216.239.39.99

If I perform the same thing on the server, prior to supplying a DNS address in DHCP I got that thing above. Now I get this:

[b]nslookup google.com[/b]
*** Can't find server name for address 192.168.1.202: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.1.202

DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

It seems like, then, that I need a DNS entry for the server itself? Or something along those lines? (The server is set to point to itself for DNS.) What am I missing.

And again, apologies for such newb questions. I'm learning a ton, though, and thank you very much for that.

 

[karlisi]

On server try 'nslookup clinic.local' it should return your server's IP address and DNS name, if not, check DNS server configuration.

You dont need to add DNS server's address to primary zone. There should be already NS and SOA records, they are built automatically, when you created the zone.

===
Karlis
ECDL; MCP

 

[basst]

Have you configured your ISP's DNS server address in the DNS forwarder tab on the server? You also need to create a reverse lookup zone for your local subnet.

 

[encata]

Try configuring

Server option 015 DNS Domain name.............clinic.local

on your DHCP server

and try joining the clients.

Why you worry? Life is too short to worry.