Strange thing....

Eric

Distinguished
Dec 31, 2007
1,373
0
19,280
Archived from groups: microsoft.public.windowsnt.domain (More info?)

Hello. I have a Windows NT4 Server running for many years.
It's a member of a workgroup called "Workgroup". 3 days
ago, I've rebooted it but when I tried to log on it
displays the message 'A domain controller couldn't be
found for the specified domain'. I can access to the
server from others stations using the usual login account.
When I tried to access to this server with a Server
Manager running on another server in the same workgroup I
have a message telling that "A Domain controller not
found, some features will be desactivated". So I have a
lot of questions about that : Why does this server cannot
log in ? Why does windows speak about domain instead of
workgroup ? If the PDC is missing, I can't understand
because no machines were removed from the network. If it
is necessary to put a PDC in this network, is it possible
to insert it without damages ?
I'm not an expert in Windows NT Networking because all of
our management is Novell Based. Usually, each Windows NT
server is standalone.

Does someone have an idea of what happens ?
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

When physically logging on to this machine do you
get a drop down box for domains? If so does the
computer name show up in the list? If you get a
drop down list for domains the machine is either a
domain member or a domain controller. If the
computer name is listed in the list the machine is a
member server and you should be able to choose
the computer name and logon locally to the machine
using the local SAM instead of a domain SAM. If
the computer name is not listed it is most likely a DC
and you'll need either the domain administrator password
or a domain account with domain administrator access.
If you don't get a drop down list for domains the machine
is indeed a standalone server which makes the error
message very confusing.

"Eric" <eperney_nospam@parisot-mvm.com> wrote in message
> Hello. I have a Windows NT4 Server running for many years.
> It's a member of a workgroup called "Workgroup". 3 days
> ago, I've rebooted it but when I tried to log on it
> displays the message 'A domain controller couldn't be
> found for the specified domain'. I can access to the
> server from others stations using the usual login account.
> When I tried to access to this server with a Server
> Manager running on another server in the same workgroup I
> have a message telling that "A Domain controller not
> found, some features will be desactivated". So I have a
> lot of questions about that : Why does this server cannot
> log in ? Why does windows speak about domain instead of
> workgroup ? If the PDC is missing, I can't understand
> because no machines were removed from the network. If it
> is necessary to put a PDC in this network, is it possible
> to insert it without damages ?
> I'm not an expert in Windows NT Networking because all of
> our management is Novell Based. Usually, each Windows NT
> server is standalone.
>
> Does someone have an idea of what happens ?
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

>When physically logging on to this machine do you
>get a drop down box for domains?

No I don't have drop down box for selecting either domain
or anything else.

>If you don't get a drop down list for domains the machine
>is indeed a standalone server which makes the error
>message very confusing.

I don't have drop down box, so it's a standalone server. I
can connect to is disk using an account but can't login on
the server itself with the same account. In this case I
have the message 'A domain controler....'....

I will go crazy !
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

Can you open the local user manager e.g., user manger
with a focus towards the machine name. From any server
click start / run and type usrmgr \\machinename.


<anonymous@discussions.microsoft.com> wrote in message
> >When physically logging on to this machine do you
> >get a drop down box for domains?
>
> No I don't have drop down box for selecting either domain
> or anything else.
>
> >If you don't get a drop down list for domains the machine
> >is indeed a standalone server which makes the error
> >message very confusing.
>
> I don't have drop down box, so it's a standalone server. I
> can connect to is disk using an account but can't login on
> the server itself with the same account. In this case I
> have the message 'A domain controler....'....
>
> I will go crazy !
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

>-----Original Message-----
>Can you open the local user manager e.g., user manger
>with a focus towards the machine name. From any server
>click start / run and type usrmgr \\machinename.
>

Yes it runs. I can edit/remove/create accounts on this
server. I can also remotely manage services running on
this server. When I try to access with the server manager
a message informs me that there is no CPD on the network
and then some features will be unavailable.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

I create a new account. I've tried to log on the server
with this new account. Same thing again : "No domain
controller found...."

What happens with domains or workgroups on this server...
As a summary I can say that I can connect to it from
another machine but I can't on the server itself.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

This is quite odd. I have no idea why a standalone
server would attempt to pass user credentials to a
DC for local logon. It may have something to do
with NDS or Netware Directory Services but I
don't have a lot of experience. I believe there is
a dll file which redirects logons towards the netware
server. You'll need to delete that file.
<anonymous@discussions.microsoft.com> wrote in message news:
>
> >-----Original Message-----
> >Can you open the local user manager e.g., user manger
> >with a focus towards the machine name. From any server
> >click start / run and type usrmgr \\machinename.
> >
> Yes it runs. I can edit/remove/create accounts on this
> server. I can also remotely manage services running on
> this server. When I try to access with the server manager
> a message informs me that there is no CPD on the network
> and then some features will be unavailable.
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

Found an info at novell.com : Rename NWGINA.DLL to
NWGINA.OLD and MSGINA.DLL to NWGINA.DLL. It seems to be a
known probleme from Novell clients. I will try this. Have
a good Week End. Thanks for your help
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

>-----Original Message-----
>Found an info at novell.com : Rename NWGINA.DLL to
>NWGINA.OLD and MSGINA.DLL to NWGINA.DLL. It seems to be a
>known probleme from Novell clients. I will try this. Have
>a good Week End. Thanks for your help
>.
>

New Novell client installed. OK. Thanks for help
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)

Good to hear. Thank you for the update.

<anonymous@discussions.microsoft.com> wrote in message
> >.
> >
>
> New Novell client installed. OK. Thanks for help