ChrisH3
asked on
DNS/DHCP Issue Windows 2003
Hello,
I just set up a local domain on my Windows 2003 box, Altec.Local. In the process of creating Active Directory, windows install and configured a DNS & DHCP Server.
This box is connected to a router that automatically distributes a network IP Address (duh!). Now, when I go to the command prompt and check ipconfig the IP address showing up is NOT in the router's range. The routers range is 192.168.2.x, however IPCONFIG is returning a range of 192.168.0.x. Therefore, my internet does not work & I cannot get updates.
Any help would be greatly appreciated!
I just set up a local domain on my Windows 2003 box, Altec.Local. In the process of creating Active Directory, windows install and configured a DNS & DHCP Server.
This box is connected to a router that automatically distributes a network IP Address (duh!). Now, when I go to the command prompt and check ipconfig the IP address showing up is NOT in the router's range. The routers range is 192.168.2.x, however IPCONFIG is returning a range of 192.168.0.x. Therefore, my internet does not work & I cannot get updates.
Any help would be greatly appreciated!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is there a way to change the DHCP to Relay on the router? if so use that to relay the server DHCP. It'd be the first router I heard about that your couldn't disable DHCP on, is it a cable modem or something?
ASKER
Its a Belkin Wirelss Mimo, perhaps I'm missing something. The only thing under DHCP that it says is the connect computers/clients with their Mac Adresses.
can you post a screen shot
ASKER
Okay, I found the option to turn the DHCP Server off, it was burried under some random settings. I right clicked the network connection and chose to use a static IP, with the IP Address 192.168.2.4, which falls in the router's range. I also placed it in the same router subnet. Now would should I do as far as the DNS and DHCP are concerned? Im new to this so the specifics make it much easier.
DNS should be set as the server itself under the network connections.
In the DNS console right click on the server go properties->forwarders-> and type in the IP addresses of your ISP's DNS servers or your router, but I always prefer ISP DNS.
For DHCP go into the console, right click on the server and go all tasks and go create new address pool (or just follow the wizard instructions) setting up. When you have finished with that right click on the server and authorise it then right click again and activate it.
If you have already configured it and the address pool is like 192.168.0.x then I'd change that one instead to suit your network. Make sure you list the DNS as the server.
In the DNS console right click on the server go properties->forwarders-> and type in the IP addresses of your ISP's DNS servers or your router, but I always prefer ISP DNS.
For DHCP go into the console, right click on the server and go all tasks and go create new address pool (or just follow the wizard instructions) setting up. When you have finished with that right click on the server and authorise it then right click again and activate it.
If you have already configured it and the address pool is like 192.168.0.x then I'd change that one instead to suit your network. Make sure you list the DNS as the server.
how are you getting on?
ASKER
I was able to get it working. I was actually having DHCP conflict with my VOIP Box. I was assigning IP Addresses in the VoIP Range, and the server was taking x.x.x.1, which was the default VoIP assignment. As a result, I bumped the server address up to x.x.x.2 and placed a reservation in DHCP for x.x.x.1. Everything works well now. I told the router to act as a wireless access point to reduce the chance of a collision.
So far so good.
So far so good.
ASKER