SMB 1.0/CIFS File Sharing Support is not running – Even though the standard is outdated, users have reported that turning it on managed to resolve the problem.Important services are not running – Network Discovery depends on certain services to run so make sure you start them.Child/Parent domain users should be able to access their mailboxes too. Once it has, restart the Exchange Active Directory Topology Service (check all the other exchange services restart OK), and after a little while mail should flow. It should also then drop back onto the domain profile without “(unauthenticated)” after the NIC name. Once you get all the DC’s in the domain (or at least the ones exchange is looking for for DNS), try the same with Exchange. If not change the primary DNS of the server to a known good DC, ipconfig /flushdns and try again. Re-enable it and it should drop back on to the domain profile. Open device manager (devmgmt.msc) and disable the network connection on the AD servers first. Closer investigation reveals that the servers (possibly AD) are on the public network, and other servers (possibly Exchange) are on the domain network with “(unauthenticated)” showing on the network connections.īefore you try removing and re-adding the vNic (this will take ages/forever for the server to recognise, don’t bother!) try this simple fix:
Rebooting the servers or flushing DNS doesn’t resolve these odd issues. Members of other (parent/child) domain who have mailboxes on the server may not be able to login to webmail though, and will get authentication errors on mobile devices. Mail should flow and members of the domain that exchange is on will be able to login and get mail. If you manage to change the DNS servers on exchange to a non problematic DC, exchange will come up – or so it seems. I say properly, because some things will work and some things wont.Įxchange might have most of its services still starting, and it will be a total pain, and take a very long time to open ncpa.cpl (network control panel). Servers might have dropped onto the public network and are unable to replicate or communicate properly with the domain. All the fun stuff.Īfter a little investigation (and waiting for very unhappy exchange servers that cannot find AD to respond), you may find some strange behaviour. Failure to find domain, replication, zone transfer failures etc. There are lots of errors in the event logs, relating to Active Directory and DNS. You get the servers back online but strange things are happening. All the equipment comes back up in a strange order (servers before SAN, Exchange before AD etc). Something dramatic happens (lets say a power cut to the head office).
Everything on your network is running fine, multiple sites, multiple VPNs, multiple domains.
0 kommentar(er)
