Network logon issues

[Guest]

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

Hi,

I hope someone can help on this, as I'm stumped.

We have a Win2k SQL Server on our network that simply cannot log on at the
moment.

You can log onto the machine itself using the local administrator account,
but if you try logging onto the domain with any user you get the following
error:

The system could not log you on because the system's computer account in its
primary domain is missing or the password on that account is incorrect.

When logged in on it's local account, it's picking up its static IP address
and DNS entries fine by DHCP, and can see the network okay (although you get
prompted for login details when trying to access any resource - which works
when given). However the network cannot see it. If viewed through explorer,
you can see the system in the list of networked machines, but that's as good
as it gets. Not irrational as it's not logged onto the network, but it does
at least show that it's capable of talking to other machines and yet failing
to do so when trying to log on.

Any thoughts anyone? I'm unable to change it to belong to Workgroup rather
than the domain for some reason, and there's no wizard option with which to
force it to run through all of the setup again, which I've found works before
in this sort of scenario on 2k pro machines.

Jon

 

[Guest]

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

"Quexlia" <Quexlia@discussions.microsoft.com> wrote in message
news:18D5E95D-F7A7-4C16-A750-35BDB3260279@microsoft.com...
> Hi,
>
> I hope someone can help on this, as I'm stumped.
>
> We have a Win2k SQL Server on our network that simply cannot log on at the
> moment.
>
> You can log onto the machine itself using the local administrator account,
> but if you try logging onto the domain with any user you get the following
> error:
>
> The system could not log you on because the system's computer account in
its
> primary domain is missing or the password on that account is incorrect.
>
> When logged in on it's local account, it's picking up its static IP
address
> and DNS entries fine by DHCP, and can see the network okay (although you
get
> prompted for login details when trying to access any resource - which
works
> when given). However the network cannot see it. If viewed through
explorer,
> you can see the system in the list of networked machines, but that's as
good
> as it gets. Not irrational as it's not logged onto the network, but it
does
> at least show that it's capable of talking to other machines and yet
failing
> to do so when trying to log on.
>
> Any thoughts anyone? I'm unable to change it to belong to Workgroup rather
> than the domain for some reason, and there's no wizard option with which
to
> force it to run through all of the setup again, which I've found works
before
> in this sort of scenario on 2k pro machines.


It sounds like you're running Active Directory. Don't change it to
Workgroup - you'll get in worse strife.

Disconnect the SQL server from the network, Run ADUC on one of your DCs,
right-click on the Computer account for the dodgy server and click "Reset
Account". Restart the server and reconnect and you should be able to get
going again.

HTH,
Cameron

 

[Guest]

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

Didn't help alas. Now to compound things, I've got another server on the
network (also 2k server, and also as it happens running sql if that makes any
odds to this) that's done exactly the same thing! Any other thoughts anyone?
I'm tearing my hair out at this.

I think that a third machine yesterday had the same issue, but that box was
running 2k pro, and I was able to force that to renew it's network related
system settings, which worked fine. Is there any way of doing this sort of
thing in 2k server (which I have very limited experience of in this sort of
context)?

"Cameron Dorrough" wrote:

> It sounds like you're running Active Directory. Don't change it to
> Workgroup - you'll get in worse strife.
>
> Disconnect the SQL server from the network, Run ADUC on one of your DCs,
> right-click on the Computer account for the dodgy server and click "Reset
> Account". Restart the server and reconnect and you should be able to get
> going again.
>
> HTH,
> Cameron

 

[Guest]

Archived from groups: microsoft.public.win2000.advanced_server (More info?)

I had the same issue today, and I logged onto the local profile and
rejoined it to the domain and then logged back into the domain and the
problem was fixed.

Hope this helps you.

Quexlia wrote:
> *Didn't help alas. Now to compound things, I've got another server on
> the
> network (also 2k server, and also as it happens running sql if that
> makes any
> odds to this) that's done exactly the same thing! Any other thoughts
> anyone?
> I'm tearing my hair out at this.
>
> I think that a third machine yesterday had the same issue, but that
> box was
> running 2k pro, and I was able to force that to renew it's network
> related
> system settings, which worked fine. Is there any way of doing this
> sort of
> thing in 2k server (which I have very limited experience of in this
> sort of
> context)?
>
> "Cameron Dorrough" wrote:
>
> > It sounds like you're running Active Directory. Don't change it
> to
> > Workgroup - you'll get in worse strife.
> >
> > Disconnect the SQL server from the network, Run ADUC on one of your
> DCs,
> > right-click on the Computer account for the dodgy server and click
> "Reset
> > Account". Restart the server and reconnect and you should be able
> to get
> > going again.
> >
> > HTH,
> > Cameron *



--
AustinITMgr
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message1132455.html