Re: Client named on the network same as Server
- From: Justin Dean <JustinDean@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Mar 2006 22:29:26 -0800
Thanks mate
it would be
justin at comzone dot net dot nz
Thanks
Justin
--
Bits and Bytes Tech Centre
"kj" wrote:
post a munged address and I'll email you an address that you can reach me..
Munged in like;
/kj at nowhere dot com
...but if your credibility with them is questionable, I'd doubt my opinion
will carry any weight at all.
--
/kj
"Justin Dean" <JustinDean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D971DF9-7074-4B1C-A92B-2622F8BA9427@xxxxxxxxxxxxxxxx
KJ can I email you? I need to just get an email to backup what i say as
this
customer is very very amatuerish ! Blames first think later.
It would be greatly appreciated
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
- From: kj
- Re: Client named on the network same as Server
- Prev by Date: Roaming Profile Problem
- Next by Date: Re: DNS and email problem
- 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
|