Re: Client named on the network same as Server

Tech-Archive recommends: Fix windows errors by optimizing your registry

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 there

Can someone with experinece maybe detail what things ould happen to a
server
that had a client with the same name (diiferent IP) added to the
network.
It was not added to the domain--it was still on WORKGROUP called
WORKGROUP.

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
messages
were seen on the server.

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
problems
and not being able to access shared folders previous to this machine
being
installed.

I hope this helps

Justin

--
Bits and Bytes Tech Centre






.

Relevant Pages

  • Re: Problem with connect computer wizard
    ... You mentioned that you're using Anonymous access with Administrator ... Open ConnectComputer properties in IIS. ... And there is only the DNS server be configured on client ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW no longer working for client desktops
    ... client and run http://>/remote and see if the behavior is the ... So you get the Web Edition banner; after that, can you log in, and if so, do ... If you log in to RWW as the Administrator, ... when given the choice between logging into the server ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 ConnectComputer
    ... Are you logged on locally as an administrator and using the domain admin to ... Microsoft SBS Product Support ... | client machine and proceeds. ...
    (microsoft.public.windows.server.sbs)
  • RE: Server does not send faxes for non-administrators
    ... This has been the situation since I set the server up in April. ... a fax as an administrator from any client and from the console. ... I understand that only Administrator can fend fax the other users cannot. ... word to the Newsgroup for accurate research. ...
    (microsoft.public.windows.server.sbs)
  • Re: HELP! Updating a global variable in a chat application
    ... I'm assuming the administrator is using a client program, ... since the server is accessed by ... of permanent user data, perhaps another of logged in user data [or the two ...
    (comp.lang.java.help)