
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
Basically goes something like this. One server, typically the domain controller, acts as a DHCP agent. This computer is assigned a static IP address on the domain. All the client computers on the domain, if not assigned a static address, send out a broadcast request to find the DHCP server. The DHCP server says "here i am." The client says "Oh, ok, now that I know who and where you are, could you please give me an IP address." The DC LEASES an address to the client from a pool of addresses called the scope, configured in the DHCP mmc snap-in. The client gets to keep that lease for a set amount of time (I think the default is 8 days) at which point the client must contact the DHCP server again and renew the lease. Thats the easy part. The trick is that none of them can browse the inernet without a DNS server to reolve names to IP addresses and vice versa. This can be the same server as the DHCP server, or it can be another server altogether, even another server out somewhere on the world-wide-web. I suggest you get a book though, because you will learn it a heck of alot faster than you will on the newsgroups. Hope that helps. Anyone feel free to correct me if I'm wrong. [EMAIL PROTECTED] (Snowman) wrote in message news:<[EMAIL PROTECTED]>... > I dont understand the whole concept of IP addresses and DHCP. > Who assigns them... etc... > > I have a computer (server) hooked up to several other computers (LAN) > through a switch... which in tern is hooked up to the internet via a > router. > > As I understand it the Server, computer clients, switch, and router > all have to IP addresses.
| <-- __Chronological__ --> | <-- __Thread__ --> |
Please check out one of the premium Usenet Newsgroup Service Providers below for access to Usenet.