• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 398
  • Last Modified:

Slow access to server

We have an SBS2000 network.

Prior to upgrading our SBS 2000 server to SBS 2008 I am upgrading all of the client PCs to Windows XP Pro (I don't like Vista).

This is going fine apart from a couple of strange issues.

Firstly, I get the following events on most, if not all, XP Pro workstations but not existing 2000 workstations that I haven't yet upgraded:

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1054
Date:            18/02/2009
Time:            11:23:32
User:            NT AUTHORITY\SYSTEM
Computer:      COMPUTERNAME
Description:
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      AutoEnrollment
Event Category:      None
Event ID:      15
Date:            18/02/2009
Time:            11:23:34
User:            N/A
Computer:      COMPUTERNAME
Description:
Automatic certificate enrollment for local system failed to contact the active directory (0x8007054b).  The specified domain either does not exist or could not be contacted.
  Enrollment will not be performed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5719
Date:            18/02/2009
Time:            11:23:32
User:            N/A
Computer:      COMPUTERNAME
Description:
No Domain Controller is available for domain DOMAINNAME due to the following:
There are currently no logon servers available to service the logon request. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.

The XP workstations are not all the same hardware so this kind of eliminates the old NIC driver solution.

Additionally, on each of the computers they have Outlook 2002. Now, I thought using Exchange in Cached Mode was a 2003+ feature. However our Outlook 2002's appear to run in what appears to be this mode as emails sent locally between PCs can sometimes be instant and sometimes require either and Send/Receive or changing mail folders for the inbox to be polled.
0
BahBah52
Asked:
BahBah52
  • 5
1 Solution
 
tntmaxCommented:
Those are typically DNS issues. Can you confirm the TCP settings on the workstations that they are pointing to the server for DNS? Did you join the machines via /connectcomputer?
0
 
BahBah52Author Commented:
Hello,

The TCP information looked correct although I'm no longer infront of the machines to be able to post that info. I can still access the server though remotely

No I joined the machine through the Network Identification tab. Some of these computers were replaced so their names already existed. Those that didn't already exist I added through Active Directory User & Computers on the server. I didn't think connectcomputer was on sbs 2000.

The DNS on the server looks ok for each workstation.
0
 
BahBah52Author Commented:
More information ...

Overnight i received this in my event viewer:

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            22/02/2009
Time:            00:00:02
User:            N/A
Computer:      MYSERVER01
Description:
Process MAD.EXE (PID=2888). All Domain Controller Servers in use are not responding:
MYSERVER01.MYDOMAIN.local
 

For more information, click http://www.microsoft.com/contentredirect.asp.
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
BahBah52Author Commented:
I am attaching a copy of a section of the DNS page. The section is from the Forward Lookup Zones.

I am concerned by the 172.20.0.71 entry. Is this suggesting the my server should also be known as this ?

The server is 172.20.1.1
The 192.168.1.100 is the outward facing 2nd NIC that is connected to the router.

dns.jpg
0
 
BahBah52Author Commented:
And the server passed a dcdiag test.
0
 
BahBah52Author Commented:
172.20.0.71 is the RAS IP.

Anyone got any ideas ? Am kinda lost here, and in need of urgent help.

Thank you
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now