paganchi
asked on
Switching DHCP/DNS from Router to Windows Server 2003 DC
Using Windows Server 2003 standard x64 edition. Currently DHCP and DNS by router. Trying to switch DHCP and DNS to DC. I shut off DHCP on the router and activated it on the DC. I pointed the DC to the router for DNS for now. I turned off all the client computers and turned one back on. It can't get an IP address. Under ipconfig, it has a random IP address and there is not gateway listed. Any ideas? Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Since it's a DC it should be automatically authorized.
That's almost true. It all depends on how DHCP was added to the DC, and whether it was running DHCP before it was promoted. In fact, Microsoft even says it's not definitive. Check the following document and look where it says "In most cases..." That means not always. http://technet2.microsoft.com/windowsserver/en/library/9a4157c4-3c2f-4871-9ffe-7d405781f2cf1033.mspx?mfr=true
"In most cases, if you are installing a DHCP server on a computer also running as a domain controller, the server is automatically authorized the first time you add the server to the DHCP console."
I simply suggested that the OP check to be sure that it was authorized to rule that out as a possible issue.
"In most cases, if you are installing a DHCP server on a computer also running as a domain controller, the server is automatically authorized the first time you add the server to the DHCP console."
I simply suggested that the OP check to be sure that it was authorized to rule that out as a possible issue.
ASKER
It is authorized (there is a green arrow) and the scope is activated. I did not do the release and renew... I just hit repair and it said it couldn't get an IP address... I will try to release and renew.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also check the DHCP logs, located by default in:
C:\WINDOWS\system32\dhcp
C:\WINDOWS\system32\dhcp
ASKER
I have almost full success at this point. My main problem was that my router and DC were on different subnets. My DC is now 192.168.1.1, my router is 192.168.1.10 and DCHP and DNS are both working on the DC. The router DCHP is off. While I was working on this, I turned off all the computers in the network except the DC and one client. Once I got it going, I turned on a total of 6 clients. All got on the network/domain fine. The problem is that in Network Neighborhood, two of the clients are not accessible to any other computer except to themselves. These two computers can access the other clients fine. I logged into all the clients with the same administrator username and password. All have valid IP addresses confirmed on the DC and the client. I cannot ping these two clients from the other clients either. The DC cannot connect with these two clients either! Can anyone help??
ASKER
KCTS - can I leave the forwarders blank or is it better/more efficient to have them?
ASKER
KCTS - my router lists two DNS IP address for my ISP. Is it better to use these two addresses as forwarders or to leave it blank? Thanks.
ASKER
By the way, the error message I get when I double click on the two problem clients in network neighborhood is:
"\\client is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions"
"The network path was not found"
Thanks.
"\\client is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions"
"The network path was not found"
Thanks.
ASKER
I feel a little stupid on this one. The Windows firewall was activated on both of those clients. It was off before but somehow it was on now. I turned it off and it solved the problem. All clients are now available.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you configured and activated a scope?
What does the event log say?