Win Server 2008 Network Sharing Center freezes

I have a win2k8 server that just this AM started having troubles identifying the network it belongs to. it spins and spins and then eventually shows a red X over network sharing center.

there have been no network changes, i havent changed the firewall at all eiher. the servers on same network in same rack are able to identify its a domain network. this one (MAIL) is not... it does perfectly in safemode. i tried going back to last known good config... same issue. any ideas? perhaps besides some updates that might have come in over night there have been NO system changes,
any help appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Glen KnightCommented:
Have you tried uninstalling the NIC from device manager and restarting, let Windows detect the NIC again?

Does the server have a second NIC? Can you try using that one instead? Or if you have another NIC you can put in?
mxrider_420Author Commented:
It has 2 NICs. Not sure what caused all this.... I will disable the NIC and let the one stay live. see if that fixes it. Have you seen this occure before randomly?...
Has something else changed on your network?  Could another DHCP server have been introduced eg new piece of networking gear?

Go to a command prompt and type ipconfig /all  Does the expected IP address range come up, is the subnet correct and expected gateway/DNS

Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

mxrider_420Author Commented:
The only thing that has changed is its a exchange 2010 server and the preferred DC is down as the MOBO fried. id assume that it (exchange) would pick up from another DC on the network. but other than that its exhibiting weird behaviors. Such as taking forever to show my desktop etc... it all happened over night. oddly enough. DHCP is fine.
mxrider_420Author Commented:
sorry for yet another post but this is what my event viewer shows. - anyone know how i can force prefered ad server when power shell cant even connect to the mail server its locally installed on even?

this site shows how to do it but im not connected to the mail server... even locally power shell isnt connecting to exchange

Process MAD.EXE (PID=1540). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Glen KnightCommented:
do you have any other domain controllers?

Is Exchange installed on a Domain Controller? if so it must also be a global catalog server.

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
mxrider_420Author Commented:
Yes two DC's both are GCs too
mxrider_420Author Commented:
Okay so let me summarize what i have done so you can help me farther. (and thanks for the help btw)

I ran adprep /forest and domain.. on the last DC in the forest eclipse.... (small smb only had 2 dc's one will be rebuilt after i get all this running) -> it came back saying it had already been done prior. ..also i should mention the ad-server that went down was running windows server 2003 the one left 2008.

i checked my error log and read everything i could find on the net about error 2080 and im not sure how to change the variables for PDC and SACL.. which are the zeros as pointed out above.

I have also turned OFF ALL windows firewalls for domain, home and private on both the mail server and the domain controller (eclipse)

i have done many reboots.

i should also mention that i removed ALL DNS records of the old domain controller and also verified that ALL 5 FSMO roles have been moved correctly to the last DC eclipse.

I have verified that "Exchange Servers" group is in as a member group for the GPO for the mail server.

im sure im missing something too.... basically im absolutely shocked that all this hasnt brought up exchange. and YES i still want to force exchange to point to eclipse but it seems like it is dynamically pointing to it but it (eclipse the last DC which is a GC too) is not giving exchange the correct permissions to work or something.

ANY ideas appreciated.


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.