Re: SBS and TS

Yup. The more I hear, the more I think that's the best solution. And even that may not work - since I very much doubt that you'll be able to cleanly pull over the AD to the TempDC. But at least it's worth a try.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message news:eiNBjH7HIHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
What a mess. I think I agree with Charlie... As long as your Active Directory is in good shape, do a Swing Migration so you can save the SIDs and not have to mess with the TS and/or workstations profiles.

--
Merv Porter [SBS-MVP]
============================

"Terry" <terryc@xxxxxxx> wrote in message news:490C4785-F91A-4D42-B95B-11742AF7223D@xxxxxxxxxxxxxxxx
Hi Thx for all the replies.

we noticed that we were getting problems where the NIC on the SBS server was showing no IP address even in DOS and yet we could pint the server.
We tried re-installing the NIC and TCP/IP and then Winsock but things just got worse. We then tried to uninstall and re-install DNS and things went really downhill.

We are getting numerous error messages now in both servers and are unable to even setup a new user!! The user gets created but no Mailbox. If I force a mailbox and associate it to the account Outlook says it does not exist. The server is SBS2K3 R2 with all patches applied.
I have created a list of the current errors in the various event viewer options, I am starting to think though that the re-load is going to be the only option open to us. Errors currently showing are:

Event Type: Error
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1126
Date: 01/11/2007
Time: 00:29:45
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: server01
Description:
Active Directory was unable to establish a connection with the global catalog.

Additional Data
Error value:
1792 An attempt was made to logon, but the network logon service was not started.
Internal ID:
3200cf3

User Action:
Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the nltest utility to diagnose this problem.

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


Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 2088
Date: 02/11/2007
Time: 08:31:00
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: server01
Description:
Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.

Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory forest, including logon authentication or access to network resources.

You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS.

Alternate server name:
server.domain.office
Failing DNS host name:
6fbd0a82-0846-4842-ab6c-6d7aa4e90011._msdcs.domain.office

NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1:

Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client

User Action:

1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.

2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".

3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns

dcdiag /test:dns

4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:

dcdiag /test:dns

5) For further analysis of DNS error failures see KB 824449:
http://support.microsoft.com/?kbid=824449

Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type was found.


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


Event Type: Error
Event Source: ESENT
Event Category: Logging/Recovery
Event ID: 215
Date: 05/11/2007
Time: 06:09:26
User: N/A
Computer: server01
Description:
tcpsvcs (4416) The backup has been stopped because it was halted by the client or the connection with the client failed.

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


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4521
Date: 02/11/2007
Time: 14:08:29
User: N/A
Computer: server01
Description:
The DNS server encountered error 32 attempting to load zone 0.0.128.in-addr.arpa from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.

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


Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13509
Date: 01/11/2007
Time: 02:29:34
User: N/A
Computer: server01
Description:
The File Replication Service has enabled replication from TSserver01 to server01 for c:\windows\sysvol\domain after repeated retries.

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


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date: 02/11/2007
Time: 13:55:36
User: N/A
Computer: server01
Description:
The DNS server machine currently has no DNS domain name. Its DNS name is a single label hostname with no domain (example: "host" rather than "host.microsoft.com").

You might have forgotten to configure a primary DNS domain for the server computer. For more information, see either "DNS server log reference" or "To configure the primary DNS suffix for a client computer" in the online Help.

While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname. This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name.

To correct this problem:
1) open Control Panel
2) open System applet
3) select Computer Name tab
4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name
5) reboot to initialize with new domain name

After reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name. However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server.

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


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4521
Date: 02/11/2007
Time: 13:29:01
User: N/A
Computer: server01
Description:
The DNS server encountered error 32 attempting to load zone domain.office from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.

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


Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 01/11/2007
Time: 00:04:13
User: N/A
Computer: server01
Description:
The File Replication Service is having trouble enabling replication from TSserver01 to server01 for c:\windows\sysvol\domain using the DNS name TSserver01.domain.office. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name TSserver01.domain.office from this computer.
[2] FRS is not running on TSserver01.domain.office.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: ba 06 00 00 º...


Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1010
Date: 05/11/2007
Time: 06:09:26
User: N/A
Computer: server01
Description:
The DHCP service encountered the following error while cleaning up the database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 4e 00 00 -N..

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 05/11/2007
Time: 07:38:28
User: NT AUTHORITY\SYSTEM
Computer: server01
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: server01$
Domain: domain
Logon Type: 3
Logon Process: Ðù_ð?
Authentication Package: NTLM
Workstation Name: server01
Status code: 0xC000006D
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8063
Date: 05/11/2007
Time: 07:35:00
User: N/A
Computer: server01
Description:
Could not read the root entry on directory 'server01.domain.office'. Cannot access configuration information. DC=domain,DC=office

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: ServerStatusReports
Event Category: None
Event ID: 1
Date: 05/11/2007
Time: 06:00:19
User: N/A
Computer: server01
Description:
Server Status Report:
URL: http://localhost/monitoring/perf.aspx?reportMode=1&allHours=1
Error Message: The parameter is incorrect.
Stack Trace: at Microsoft.SBS.UpdateServices.ConfigurationHelper.AUPolicySetupClass.GetPolicyConfiguration(SBSPolicyType type, AUInstallationOption& pInstallationOption, Int32& piInstallationDay, Int32& piInstallationHour)
at Microsoft.SBS.UpdateServices.DataProvider.GetUpdateSchedule(String GroupName)
at Microsoft.SBS.UpdateServices.StatusPage.Utility.GetUpdateSettings()
at usage.frmPerf.renderReportWorker()
at usage.frmPerf.renderReport()

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


Event Type: Warning
Event Source: SQLBrowser
Event Category: None
Event ID: 3
Date: 01/11/2007
Time: 02:08:47
User: N/A
Computer: server01
Description:
The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid.

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


Event Type: Warning
Event Source: DLOMaintenanceSvc
Event Category: None
Event ID: 60
Date: 01/11/2007
Time: 02:08:33
User: N/A
Computer: server01
Description:
The maintenance service was unable to register its interface with active directory. The maintenance service will be unable to manage files on file servers other than the computer running the maintenance service. Service class = {14E52635-0A95-4a5c-BDB1-E0D0C703B6C8}, Error = 80090350.

TS

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 02/11/2007
Time: 13:56:58
User: N/A
Computer: TSserver01
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "00000000: LdapErr: DSID-0C090A1A, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece". The event data contains the error.

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


Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 4513
Date: 02/11/2007
Time: 13:55:27
User: N/A
Computer: TSserver01
Description:
The DNS server detected that it is not enlisted in the replication scope of the directory partition ForestDnsZones.domain.office. This prevents the zones that should be replicated to all DNS servers in the domain.office forest from replicating to this DNS server.

To create or repair the forest-wide DNS directory partition, open the the DNS console. Right-click the applicable DNS server, and then click 'Create Default Application Directory Partitions'. Follow the instructions to create the default DNS application directory partitions. For more information, see 'To create the default DNS application directory partitions' in Help and Support.

The error was 9002.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..



"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message news:%23PL%23GewHIHA.5328@xxxxxxxxxxxxxxxxxxxxxxx
What is the TCP/IP problem on the SBS server? Exact text of error message?

--
Merv Porter [SBS-MVP]
============================


"Terry" <terryc@xxxxxxx> wrote in message news:8F5E67BB-D964-48F5-A2B0-53A0F03E8A1E@xxxxxxxxxxxxxxxx
Hi,

We are running and SBS2K3 server, and also have a 2003 Server setup as a terminal server.
The SBS server seems to have developed a problem with TCP/IP. we have tried various resolutions but to no avail.
We are now looking at re-loading the SBS server. As we have quite a few profiles setup on the TS we are loathe to lose these.
Is there a way we can re-load the SBS server and keep to replication and profiles etc safe on the TS??

Many thanks for any help

Terry






.