Re: Client named on the network same as Server
- From: "kj" <kj@xxxxxxxxxxx>
- Date: Wed, 15 Mar 2006 20:22:05 -0700
Unfortunately this is the problem with multiple people using the same
account. There's just no longer any accountability even if you have all the
log files. One user, one account. One user needs to perform administrative
tasks, User=Admin1. I avoid logging in as Administrator unless absolutely
necessary. 7 different concurrent administrative logins? That's just lunacy.
Oh, and always attempt to salvage log files. They represent potential
substantiation. Also, a PSS call probably would have been in order before
you rebuilt or restored without an obvious hardware failure. (hindsight, but
lessons for next time perhaps)
--
/kj
"Justin Dean" <JustinDean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:748776E2-78B0-40F3-A73F-452BFE40874C@xxxxxxxxxxxxxxxx
Yes
I also think that they had multiple machines that were using administrator
username and passowrd for different functions.
Some for just file and print sharing
Others were fully logged in . PLus there was one remote session (from us)
logged in at same time doing script file updates.
It is possible that inclding the XP home machine there were a total of 7
administrator logins going that day.
Justin
--
Bits and Bytes Tech Centre
"kj" wrote:
I'm pretty certain that the source of your AD problems were with this;
See my other post about XP Home using Administrator passwords as well.
Duplicate names on the network will foul up the works, but not
permanently.
--
/kj
"Justin Dean" <JustinDean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4CC79B09-0B70-41DE-B15C-599EE14C8E62@xxxxxxxxxxxxxxxx
Yes but how
I am certain SBS 2003 is strong enough not to allow a client with the
same
name that is not on the domain to destroy its critical functions.
There must be another reason for this?
--
Bits and Bytes Tech Centre
"Marina Roos [SBS-MVP]" wrote:
Hi Justin,
Check the eventlogs on the server. Is it still a domain controller? If
not,
you are looking for a complete restore from backup because AD has been
badly
hosed.
--
Regards,
Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53
"Justin Dean" <JustinDean@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in
bericht
news:FFBF2193-DC05-42A8-B9AE-40834FDB781E@xxxxxxxxxxxxxxxx
Hi thereserver
Can someone with experinece maybe detail what things ould happen to
a
that had a client with the same name (diiferent IP) added to theWORKGROUP.
network.
It was not added to the domain--it was still on WORKGROUP called
messages
I have looked in KB for stuff but it all points around the same
thing.
The Client will spit out an error that a "Duplicate Name exists on
the
network". The tehhnician changed the name to a good name. No error
were seen on the server.problems
The client was then successfully added to the domain under its new
name.
NO one forced the client to be added---new name or old.
2 hours later the server was restarted and then developed on restart
major
Kerberos + AD + DNS failures.
The clients had been experiencing random server share disconnection
and not being able to access shared folders previous to this machine
being
installed.
I hope this helps
Justin
--
Bits and Bytes Tech Centre
.
- References:
- Re: Client named on the network same as Server
- From: Marina Roos [SBS-MVP]
- Re: Client named on the network same as Server
- From: Justin Dean
- Re: Client named on the network same as Server
- From: kj
- Re: Client named on the network same as Server
- From: Justin Dean
- Re: Client named on the network same as Server
- Prev by Date: Re: pop3 connector not delievering messages to users
- Next by Date: SBS 2003 beginner
- Previous by thread: Re: Client named on the network same as Server
- Next by thread: Re: Client named on the network same as Server
- Index(es):
Relevant Pages
|
