Re: Clients can't login after restore SBS2003 SP2 - URGENT


Hi, I do a monthly image (Paragon Drive Copy 8 Pro) as well as daily data
backups. The daily backups had failed due to client not following procedure
with swapping media daily. I used the monthly image, which is on a seperate
harddrive and is a bootable image. I recovered the data from the dead drive
using data recovery software. I simply copied it over the old data but no OS
files, just data. This ran but the clients could not login top the domain.
The original HD had its partitions damaged and a bit of work enabled me to
access the data as I said. I am now setting up a firmer process for the
client's daily backups. I will monitor them again for a period.

By following the process of removing the client PCs and setting them up
again using the wizards I have a full system again. All is well. All software
is functional and has been all along.

Thanks for all the help, its greatly appreciated.
Barry




"kj [SBS MVP]" wrote:

There are more events going on than just simple machine account password
changes can account for and without complete results from recommended
actions, it's a little hard to stitch together the enviroment.

I'm begining to wonder about the integrity of your restoration process.
Perhaps you can describe in more detail (step by step) how you recovered
from the drive failure.

I had a drive failure and used a bootable backup from a month ago. I
recovered the data and restored to the backup, so it's up to date
generaly. BUT the clients can't log in now.





Bazzar wrote:
Thanks everyone. OK here it all is...

First let me say I had tried before removing a client computer and
doing as suggested and it didn't work!! I just tried it again and it
now works fine, it logs in, its in DNS and DHCP and all is well. I
will do this now for all clients, there are several with impatient
staff manning them but I'll sweet talk them. Thanks again.

Now the dcdiag test has less errors than first time. The frsevent
error is still there. The syslog has many less errors now. I'm
assuming these will go as I reconnect clients. I hope I don't have to
reestablich desktops etc for each user login on clients. What drag if
so. The nltest error is still there. I'm leaving in the information
from the first run anyway for your inspection. You may want to
comment on some of the errors and that would be greatly appreciated,
I'm always learning.

Here is the first effort before the reconnect of a client:

The clients give this message on trying to log in;
"The system cannot log you on to this domain because the system's
computer account in its primary domain is missing or the password on
that account is incorrect"

The event logs have a range of related errors.

The dcdiag result is large so I'm only sowing the failures for now.
The Starting test: frsevent
* The File Replication Service Event log test
There are warning or error events within the last 24 hours
after the SYSVOL has been shared. Failing SYSVOL replication
problems may
cause
Group Policy problems.
An Error Event occured. EventID: 0xC00034F7
Time Generated: 03/31/2009 08:14:06
(Event String could not be retrieved)
......................... SERVER failed test frsevent

The other failure is the Systemlog test
Every test failed in this with several Event IDs, the general format
is;
An Error Event occured. EventID: 0xC0001B58
Time Generated: 03/31/2009 08:15:23
(Event String could not be retrieved)

5 had info about kerberos client in the following format;

Event String: The kerberos client received a
KRB_AP_ERR_MODIFIED error from the server [client_name]
The target name used was
cifs/[client_name].[domain_name].local. This
indicates that the password used to encrypt the
kerberos service ticket is different than that on
the target server. Commonly, this is due to
identically named machine accounts in the target
realm (Domain_Name.LOCAL), and the client
realm. Please contact your system administrator.


The nltest result was;

I -NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN

If you want more detail then I post the whole output but I think this
gives the idea.
One cleint (W2k) is able to log onto the domain as administrator but
not as a user. No other clients can get on the domain.

Thanks everyone.
Barry


"nordberg" wrote:

On Sun, 29 Mar 2009 20:02:02 -0700, Bazzar
<Bazzar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

URGENT SBS2003 SP2 with Exchange and SQL. URGENT
I had a drive failure and used a bootable backup from a month ago. I
recovered the data and restored to the backup, so it's up to date
generaly. BUT the clients can't log in now. I can ping away both
ways, not a problem. I can access shared data on the server from a
client if I login to the client at the local login level on the
client, simply using \\server\documents\ etc. Various programs can
access their server based components and data. Outlook can access
emails. I am unable to log into the domain though, either as
administrator or user. I can log into the server at the server. I
can log in remotely with RDP using user and admin accounts.

1 NIC for LAN, 1 for Internet. DHCP is running. Ipconfig /all shows
the NICs as OK except that DHCP is not enabled. Not all clients
show up on the DHCP address leases. Network Neighbourhood shows all
the clients but not the server. I am running all the clients as
admin logins using the local computer, not the domain, and they are
able to operate their business today that way although I expect I
will have to do some data rework once this gets solved.

I need to sort this out urgently and get it back to normal.
Suffering headaches at present so not feeling very sharp or bright
so that doesn't help at all.

If you need more info let me know.

The error message you receive when trying to log on would be
helpful...

Presume you've checked the Event Logs on the server there's nothing
obvious?

--
/kj



.

Relevant Pages

  • Re: Email clients
    ... >>> relying on Microsoft. ... >> backed up instead of a myriad of clients. ... to restore was something that most folk would not understand, ... Now, I have a reputation for being fanatical about backups, ...
    (comp.sys.acorn.advocacy)
  • Windows 7 backup & SBS2008 Prem.
    ... I have an SBS 2008 network, with Windows 7 clients. ... on my server for the clients to use to do backups. ... Everything seems to work fine as far as the backups go, ...
    (microsoft.public.windows.server.sbs)
  • Re: Apple ready for mainstream enterprise use?
    ... can do Macintosh _or_ Windows tape backups using client/server. ... with Retrospect here at home and it works well. ... Depending on which you purchase, a different number of clients is supported. ...
    (comp.sys.mac.system)
  • Re: Medical Records loss
    ... My other two clients do not request any backups, ... takes a catastrophic event to make them "wise up." ... Then what happens if I have a fire, ...
    (sci.med.transcription)
  • Re: Backup Question
    ... Microsoft MVPs ... "kitchen sink" on that drive and their backups work out to be over 300gb ... I have been using BackupAssist quite successfully at other clients and I ... SQL databases (which are first backed up to ...
    (microsoft.public.windows.server.sbs)
Loading