Unidentified Network (Public Network) after running dcpromo on 2008 server

I've added a 2008 domain controller to the network to replace the current 2003 domain controller.  ADPREP ran fine and I ran DCPROMO on the 2008 server but after the first reboot the server lost network connectivity and it seems the reason is because now instead of using the domain network profile it's using the Public one because it thinks it's on an "unidentified network".   I cannot connect to or out of the 2008 server anymore, not even pings and the Network and Sharing Center says I have Local Access only.  

Also, the domain policy enabled the firewall and turned off the standard profile firewall in the registry as part my troubleshooting.   netsh shows the opmode as enabled and it won't let me disable. (if this is a firewall issue)

When the server was a member server everything was fine.

Thanks.
daboyleAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AdoBeeboCommented:
Ping won't work in Public profile mode as ping is only available when you enable File Sharing in Network & Sharing Center, unless you make a seperate Firewall entry for it. Public profile is going to stop most in/out traffic as it is the profile that is designed for connecting to an unsecure hotspot in a cafe.
Try deleting all of the existing network locations, reinstalling the NIC with the latest driver from the manufacturer, checking the NIC settings match up to your network settings (e.g. flow speed), setting the new DC to DHCP and testing it on the same switch as the DHCP server.
After it rebooted did the wizard finish successfully? Any errors in the Event logs? Although I maybe wrong, I doubt this is a firewall issue. Might be worth running gpresult and see what policies have applied to it ...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
daboyleAuthor Commented:
I'll go try that now.  

The event logs are full of errors about not being able to contact the domain.   When the server came back up I don't think it did finish because it couldn't see the network.   I see on the 2003 servers that there isn't any records in the DNS except for it's one A record, it's own DNS however looks like it syncronized and is correct with all three servers.  The existing two domain controllers have replication entries for the new server and are trying to replicate with it.
0
daboyleAuthor Commented:
I tried what you suggested and have the same problem.   I tried a different NIC as well and got the same result.
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

AdoBeeboCommented:
Have you run gpresult and has it picked up the Domain Controller policy?
0
AdoBeeboCommented:
Also, did you run domainprep and forestprep before bringing up the new 2008 DC?
0
daboyleAuthor Commented:
It's working now but I don't actually know what was wrong.  Yesterday as part of troubleshooting I tried the built in Broadcom NIC that was in the server (I was using an intel card) and I experienced the same problem so I didn't think it was a bad NIC and switched back to the original.    I tried it again this afternoon and the Broadcom network card worked.    I'm not sure what has changed between yesterday and today, I had the firewall off yesterday and I turned it back on today but I dont' think that would be it.

It wasn't a TCP/IP setting and because nothing changed in the intel adapter setup from before and after the DCPROMO I can't explain it.   Maybe it was just a coincidence that the NIC failed when it did.   Whether it's a hardware issue or not I don't know, I'll have to try it in a spare server.

Thanks for your help.   And the server has replicated now with the others and it looks good.
0
daboyleAuthor Commented:
Your thinking around the network adapter being the problem was correct.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.