Re: 2000 server "interactive login prohibeted"

anonymous_at_discussions.microsoft.com
Date: 07/13/04


Date: Tue, 13 Jul 2004 12:07:35 -0700

Now don't laugh, but we have one domain controller and 3
pc's. Not exactly a big network. I am using static IP and
no DNS. They can ping each other fine. They are all
Windows 2000 pc's. I did get my problem fixed though, by
downloading "ntrights.exe" from the 2003 Rsource Kit and
then running it with a few command switches. I still have
some other "non-critical" bugs to fix. I am going to check
on the priviledges that you mentioned earlier. I also can
not "browse" the 3 pc's from the server. The pc's can see
each other fine, and they see the server fine, but not the
other way. The pc's authenticate fine and server shares
works great. It just does not go the other way. I am
thinking I need to configure DNS. I am new at this so I am
still in the learning curve. Thanks again for the help. I
have so much to learn.
>-----Original Message-----
>
>"Anton" <Anton@discussions.microsoft.com> wrote in message
>news:F73DB031-16EB-428A-A334-0B6311AD7CFD@microsoft.com...
>> Thank you. I installed that adminpak.msi and then went
to load the various
>snapin's. Everyimte I went to connect to the domain
controller it said that
>it could not be found. I can aunthenticate to the domain
okay without any
>problems, but so far I have not been able to get into it
at all. Woud you
>have any other suggestions or am I missing something
obvious that you know
>of? I appreciate the help.
>
>Doesn't make sense, you are authenticated on the domain
but can't locate a
>domain controller? Are you running the MMC console with
appropriate
>privileges for DC access? Does pinging the DC name
succeed? How many DCs are
>present? Is DNS running on the network? etc
>
>>
>> "SaltPeter" wrote:
>>
>> >
>> > "Anton" <Anton@discussions.microsoft.com> wrote in
message
>> > news:F6B720DB-0064-4025-9205-
AC3800F4C453@microsoft.com...
>> > > I made a "small" mistake when configuring my local
user policy on my
>> > windows 2000 server with active directory. I seemed
to have prohibited
>any
>> > and all users from loging onto the server. Desktop
logins are working
>okay.
>> > I do not have it configured for terminal services so
I can not log in
>> > remotely and fix it. Is there anyway of fixing it
without re-installing
>> > windows? Is there a way of going back to the default
security policy
>without
>> > killing all my user accounts in active directory?
>> > > Any help or advice is very much appreciated.
>> >
>> > You don't need Terminal services to access the
server. Locate a W2K
>client
>> > on the network/domain and run adminpak.msi off the
server's CD (I386
>> > directory) and modify the domain or server security
with the MMC
>snap-ins.
>> >
>> > http://support.microsoft.com/default.aspx?scid=kb;EN-
US;216999
>> >
>> >
>> >
>
>
>.
>



Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Random Network Disconnects
    ... network and the only way I can seem to get it back up is to restart the box. ... Testing IpConfig - pinging the Secondary WINS server... ... DNS Host Name: itdspstest01.itd.edited.edited ... Provider Version:2 ...
    (microsoft.public.windows.server.dns)