Networks

Ask something
Discussion Locked

DNS DHCP Problem in Win 2k3

0 helpful
7 replies

by wortos

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I was configuring my dhcp server when I made a mistake. I told it to have a scope of xxx.xxx.0.10 to xxx.xxx.0.16 because we have only 5 workstations and the server. The problem is that the server's ip is xxx.xxx.0.1 so the server went out of the network. I reconfigured the ip scope to xxx.xxx.0.1 to xxx.xxx.0.16 (Hey! It was a good idea after all!). But still the server cannot comunicate with the workstations and they don't appear in the Network Places.

I check the dhcp server and it is leasing the ip addresses to the workstations. I know that since my shop is so small I can reinstall AD all over but IS THERE ANOTHER TO DO IT?

Thanks for your time.

7 replies

by timwalsh

The fact that the servers IP address was not included in the scope has no bearing on your problem. As long as all nodes have the same network address and subnet mask, they should be able to communicate over IP. The fact that your network ceased working after implementing DHCP tells me that there is something wrong with your DHCP configuration, not the server.

Fixed IP addresses should either not be included in the scope or excluded once the the scope is created.

Check to make sure the DHCP scope and your server both have the same subnet mask. If they are different, the only way to change the subnet mask of the scope is to delete the scope and recreate it. Always change the scope subnet mask to match the server, not the other way around (even though it is easier).

If the subnet masks are different, even though everything else matches, your server and workstations are in 2 different networks as far as DNS and TCP/IP are concerned.

Hope this helps.

by wortos

I double checked it and the DHCP's scope is in the same subnet mask as the server's.

by monice

Make sure that your AD DNS server is configured in your dhcp scope for your workstations. Also your AD DNS server should have itself entered as its primary DNS server, and your ISP DNS servers set up as forwarders. If your clients are other that Win2k Pro or XP Pro, configure your DHCP server to automatically update DNS for non-AD compliant workstations.

by wortos

I tried this tip already but the DNS wizard told me that the zone was already made. So I checked the DNS config and it was in there.

I'm gonna try to say how it was working before my "accident" so that you can make better suggestions.

AD was installed with the wizard as a "Typical setup for a first server" and it created this log:

(7/18/2003 3:44:08 PM)
Configurations for Your First Server
Static IP address: 192.168.0.1
Subnet mask: 255.255.255.0
Preferred DNS server: 192.168.0.1
DHCP installed successfully.
This server has been successfully set up as a domain controller.
Install Active Directory and DNS
Full domain name: Biblioteca.local
NetBIOS domain name: BIBLIOTECA
DNS installed successfully.
DNS queries will not be forwarded.
DHCP Server successfully authorized.
TAPI directory successfully set up.
An Application Naming Context was successfully set up in Active Directory on this domain controller for use by TAPI client applications. If you later need to demote this machine from being a domain controller, this Application Naming Context should be removed with the TAPICFG utility. The Application Naming Context has the following DNS name: casco.Biblioteca.local.

Hopefully this will help.

This discussion is closed to new replies.