Re: A couple log entries...

It almost sounds as if your domain got "reinstalled" ... very weird ...
indeed ...

Good luck.

BTW: some hardware tips

Always install - if budget allows - the system on a hardware mirror. before
major upgrades I shutdown the system and boot from one disk ... if it goes
wrong big time I can boot from the other disk and then rebuild the mirror
.... a very fast way to get the original config back. It does not remove the
need for backups or images but it's a good trick.


"KBB" <kbb@xxxxxxxxxxxxxx> wrote in message
news:Oj6V3ql4GHA.3644@xxxxxxxxxxxxxxxxxxxxxxx
Hi - thanks for your followup. I went ahead and opened a ticket with
Microsoft. They couldn't find a cause, but since DCDIAG is almost
perfect, we are just disjoining & rejoining to the domain.

This works, althouhg it creates a different set of folder (new
profile,i.e. user.domain.0000). I have to unhide the old profile folders
and copy them over to the new profile to get the user back to normal.

I am going to spply the fully SBS 2003 SP1 on Friday....!

Thanks!
KBB

<workinghard@xxxxxxxxxxxxxx> wrote in message
news:%23VFpbNl4GHA.1496@xxxxxxxxxxxxxxxxxxxxxxx
I can't help but fear that your AD has become corupted, replaced or
otherwise has been messed with.

Do all the PC's and servers have their time synching in order.

Is your DNS on all machines configured as it should be?

Cheers


"KB" <kb@xxxxxxxxxxxxxx> wrote in message
news:OxiLdfj4GHA.3644@xxxxxxxxxxxxxxxxxxxxxxx
Just ran DCDIAG (from Server 2003 sp1). It ran with no errors, other
than at the end when it cannot find a time server. This is the only DC
on the network.

Any suggestions on a "proactive" repair process for AD, instead of a
restore?

I have a new symptom - one user's password is not accepted, even when I
reset it. Otherwsie, things seem to have stabilized.

KB


<workinghard@xxxxxxxxxxxxxx> wrote in message
news:uTAIjeb4GHA.3444@xxxxxxxxxxxxxxxxxxxxxxx
run dcdiag on the server ==> what is the result?

Sounds like you have a serious AD corruption, lost the DC ... do you
have any backups and do you know about AD restore using DSRM ... google
on these terms ...


"KB" <kb@xxxxxxxxxxxxxx> wrote in message
news:eyRZMxa4GHA.3376@xxxxxxxxxxxxxxxxxxxxxxx
Heck no! There isn't anyone else here but me & the users :)

Interestingly, I am finding the lost rights are speicifc to certain
shared folders; I've been able to reassign rights to the several main
folders that people are reporting.

Do you think this could be some kind of error due to the fact I am
running the original OEM release of SBS 2003 (not SP1)?

Do you think it might be a very good idea, or a very bad idea, for me
to go ahead and apply the SP1 updates? I was planning to do this on
Friday anyway...

THanks!!
KB
<workinghard@xxxxxxxxxxxxxx> wrote in message
news:uBywSea4GHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
Did anyone reinstall the domain controller /SBS server?


KB wrote:
Here are two log entries around the time of the server "crash";
could a dump
of a shadow copy cause this??

The oldest shadow copy of volume C: was deleted to keep disk space
usage for
shadow copies of volume C: below the user defined limit.

The computer BUSINESSSYS_DS tried to connect to the server \\PKY1
using the
trust relationship established by the LDPI domain. However, the
computer
lost the correct security identifier (SID) when the domain was
reconfigured.
Reestablish the trust relationship.

"kj" <kj@xxxxxxxxxxx> wrote in message
news:OeJQKuZ4GHA.2144@xxxxxxxxxxxxxxxxxxxxxxx
Can't imagine a scenerio as you describe without substantial events
in the
event logs.

You probably want to call Microsoft Support for something like
this.

To continue here, try running ipconfig/all , netdiag, and dcdiag /c
/v on
the server and posting the results.

--
/kj
"KB" <kb@xxxxxxxxxxxxxx> wrote in message
news:%233RsnhZ4GHA.2208@xxxxxxxxxxxxxxxxxxxxxxx
Also, the Administrator cannot access many/most folders on the
server,
from the server desktop. Access Denied.


"KB" <kb@xxxxxxxxxxxxxx> wrote in message
news:uWk%23CdZ4GHA.3444@xxxxxxxxxxxxxxxxxxxxxxx
Help! I have an SBS 2003 Prem server (OEM version - not yet
applied
SP1). Suddenly, a bunch of users lost their SID = I had to
reassign them
a new password to even get them logged in. The Administrator
password
wasn't being accepted, even at the console. I logged in as an
admin-equivalent IT login, and reset the Admin password. Also,
some
users can't get into sub-folders in network shares.

The server apparently crashed and rebooted, but I found nothing
in the
logs to explain. I don't even know where to begin as their does
not
appear to be any smoking gun....it's as if something happened to
the DC,
where some users are messed up, others are not. some can access
cetain
files, others cannot.

I just took over this site two weeks ago and still have not
figured out
the group policies etc...anyone heard of anything like what I'm
experiencing?

Thanks!
KB














.

Relevant Pages

  • Re: Single server enviornment migration to 2003
    ... (I lost connection my old way, ... I tried to use the file server Migration Toolkit. ... I copy and pasted the folders. ... I don't have permission to that folder. ...
    (microsoft.public.windows.server.migration)
  • Re: A couple log entries...
    ... I am finding the lost rights are speicifc to certain shared ... folders; I've been able to reassign rights to the several main folders that ... the server and posting the results. ...
    (microsoft.public.windows.server.sbs)
  • Re: A couple log entries...
    ... I have to unhide the old profile folders ... I am going to spply the fully SBS 2003 SP1 on Friday....! ... than at the end when it cannot find a time server. ... Sounds like you have a serious AD corruption, lost the DC ... ...
    (microsoft.public.windows.server.sbs)
  • Re: A couple log entries...
    ... I have to unhide the old profile folders and copy them ... I am going to spply the fully SBS 2003 SP1 on Friday....! ... than at the end when it cannot find a time server. ... Sounds like you have a serious AD corruption, lost the DC ... ...
    (microsoft.public.windows.server.sbs)
  • Re: A couple log entries...
    ... Sounds like you have a serious AD corruption, lost the DC ... ... running the original OEM release of SBS 2003 (not SP1)? ... The oldest shadow copy of volume C: was deleted to keep disk space ... the server and posting the results. ...
    (microsoft.public.windows.server.sbs)