2000 server and 2000 pro network

  • Thread starter Thread starter Leo
  • Start date Start date
L

Leo

Hi everyone.
I recently setup a 2000 server pc with 2- 2000 pro pcs
networked to it. I set up accounts from the server using
active directory and disabled local accounts from all
machines. these are in a workgroup called CMT. I have
another workgroup called SMON. I wanted to have access to
all computers from any of the two workgroups, so I changed
the IP addressing scheme of CMT to match those in SMON
(except the domain controller 2000 Server). Then I
changed my mind and changed the IP addresses back to the
original. Now when I try to log in to my 2000 pcs in CMT,
it comes back saying to make sure I have the right login
name, password and domain controller. I can see the three
computers networked when I log in to any of the three as
admin, but a regular user cannot login using network
accounts created in the domain controller.

Please help!!
 
In
Leo said:
Hi everyone.
I recently setup a 2000 server pc with 2- 2000 pro pcs
networked to it. I set up accounts from the server using
active directory and disabled local accounts from all
machines. these are in a workgroup called CMT. I have
another workgroup called SMON. I wanted to have access to
all computers from any of the two workgroups, so I changed
the IP addressing scheme of CMT to match those in SMON
(except the domain controller 2000 Server). Then I
changed my mind and changed the IP addresses back to the
original. Now when I try to log in to my 2000 pcs in CMT,
it comes back saying to make sure I have the right login
name, password and domain controller. I can see the three
computers networked when I log in to any of the three as
admin, but a regular user cannot login using network
accounts created in the domain controller.

Please help!!


I apologize, but I'm trying to follow your train of thought, but I'm having
a some trouble doing so. You have two machines that were in a workgroup and
you joined them to a domain? Is the domain SIMON or CMT or is it another
name? If you wanted to have access or not have access, why change the IP
scheme? Just remove them from the domain, unless I'm missing something
really basic here. Are they on two different physical subnets or are they on
the same wire and just decided to use different IPs and subnets to stop
communication?

The first question I have, are the DNS addresses in the machines' IP
properties in the domain (not sure what your domain is called, but you did
mention the two workgroups, which aren't domains) ONLY using the internal
DNS you setup for AD? You can't use another DNS or you'll get numerous
errors in regards to AD, including lack of logon ability.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top