Primary DC problems 1

[snyperx3]

I have a server that has been in use for a while and become unstable so the company purchased a new server to serve as a domain controller and dns server.

I transferred FSMO roles to the new server so that it would serve as the primary DC following the guide posted here:

http://www.petri.co.il/transferring_fsmo_roles.htm

This new server has itself set as its primary dns and the old server set as the secondary dns. The issues I am having are:

1. It doesn't seem to be the primary DC. When I browse to \\<domainname>\NETLOGON and create a new file it is not placed in \\<newserver>\NETLOGON but rather \\<oldserver>\NETLOGON.

2. It's DNS seems reliant on the old server. When the (unstable) old server is offline, PCs on the network cannot translate names to IPs. All PCs on the network have the new servers IP set as their primary dns server, but when the old server is offline and the new server is on they cannot browse the internet. As soon as the old server is turned back on they can browse fine.

Thanks for any suggestions.

Pete

 

[58sniper]

1. It doesn't seem to be the primary DC. When I browse to \\<domainname>\NETLOGON and create a new file it is not placed in \\<newserver>\NETLOGON but rather \\<oldserver>\NETLOGON.

There is no "primary DC". If you go to \\domain\netlogon and wind up at the old server, then that's just because that's the DC you were referred to. Through FRS, the file should ultimately be on ALL DCs.

2. It's DNS seems reliant on the old server. When the (unstable) old server is offline, PCs on the network cannot translate names to IPs. All PCs on the network have the new servers IP set as their primary dns server, but when the old server is offline and the new server is on they cannot browse the internet. As soon as the old server is turned back on they can browse fine.

What server is being given out in the DHCP configuration?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[snyperx3]

What server is being given out in the DHCP configuration?

No server was being given out in DHCP. I was changing them manually in each PCs configuration. I have added the correct server to DHCP so that it will be in there from now on.

This problem still exists.

-Pete

 

[58sniper]

If a PC is configured to look at the new DNS server, and that DNS server is properly configured for Internet forwarders, then it will work. The assumption being that the "old" server isn't acting as a proxy or ISA box.

I suspect that you're missing forwarders in you DNS config on the new box.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[SteveRoadWarrior]

what are the results of dcdiag /c
(just the last section, FSMO roles)

 

[snyperx3]

I suspect that you're missing forwarders in you DNS config on the new box.

This is correct. There were two forwarders setup, but they were invalid. I setup the correct forwarders and everything was working correctly afterwards.

Thanks!
Pete