Domain controller cannot browse network

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I had a 2003 domain which was working fine until recently. I added an
Exchange 2003 server and then migrated to a second Exchange 2003 server.

After I had done this my domain controller lost it's ability to browse the
network - I started getting messages '\\Servername is not accessible. You
might not have permission to use this network resource. Contact the
administrator of the server to find out if you have access permissions. The
account is not authorized to log in from this station'

I have since been unable to open any mailboxes on my Exchange server - they
get the 'Unable to open your default folders. The Microsoft Exchange Server
computer is not available. Either there are network problems or the Microsoft
Exchange server computer is down for maintenance'
However I can open mailboxes using OWA with no problem.

As a test I added another domain controller which could then browse the
network fine so I moved all the DC roles to this new DC. In Exchange I then
changed the GC to the new DC and the recipient update services - made no
difference.

I don't get any error messages in the event logs to indicate any problems
and having run DCDiag, Netdiag and AdDiag they all report no problem.

After adding the second DC, workstations are unable to browse the Exchange
server and cannot resolve any entries in the address book - I get a message
to say 'Logon failure: the target account name is incorrect'

I am at a loss as to what the problem could be - or even if they are related.

DNS appears to be ok and all servers are on the latest service packs (SP1
for 2003 , SP2 for XP and SP1 for Exchange 2003). Windows firewall is
disabled for the purposes of testing and I have Mcafee AV software.

Any suggestions - other than to rebuild the domain!
.

Relevant Pages

  • Re: Webserver on a DMZ still needed?
    ... built the network, I made the Exchange server its own Domain Controller. ... say risk is concentrated at a single point instead of being distributed. ...
    (Security-Basics)
  • Re: Same two Domain Names in the same network
    ... the exchange server which handles the email part of your domain for the users ... PresentlyDomain name, network name, name of domain controller and name ...
    (microsoft.public.win2000.dns)
  • Re: Changing Cofiguration Domain Controller
    ... The Exchange server is on a different network ... Exchange server has no problem discovring both DC's for "Domain ... "Configuration Domain Controller" and it is this CDC that Exchange cannot be ... there is no network or name resolution problem. ...
    (microsoft.public.exchange.admin)
  • Re: Network design involving an new exchange server
    ... What if the domain controller is also the exchange server? ... This small network with a low usage ... Exchange server with about 30 mailboxes. ... The applications are a client server app and exchange services ...
    (microsoft.public.exchange.design)
  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)