Domain AD WS login problem...

Mrpush · Guest

Hello,

Running MS 2003 server. On a specific WS, If I change from my local
workgroup and join my domain, it asks me to provide user and password from AD
to let me join. After joining the domain, it asks to re-boot the WS.

When I re-boot, I login as AD member, and all is well. However, upon a
second re-boot and/or power off the WS, when I try to log back into the
domain as the same user (or other users as well), it does not work. I get
the error message that "user name, password, or domain info is incorrect."

If I "un-join" the domain and re-join the workgroup, then re-join the domain
, I can repeat this process all over again.

Does anyone have any clue what could be casuing this?

Thanks much,

Mark

Jorge Silva · Guest

Hi

Is the Dns properties of the new member server ponting to your local Dns
Server?

--
I hop that helps

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Mrpush" <Mrpush@discussions.microsoft.com> wrote in message
news:A2FC2E06-775E-4502-B99F-55D617061B2D@microsoft.com...

Mrpush · Guest

Hi,

Actually, the workstation TCP/IP DNS is not pointing to my DC for its DNS.
Its pointing to my Firewall/router IP for its DNS.

The DC's DNS is set to point at itself locally, and has forwards set to
point to my ISP for lookups.

I would think that this might be the issue (and it could be), however my
current workstation's DNS is set up the same way but does not experience the
same problem. I can log on and off without problem.

I will change the problem WS TCP/IP DNS setting to point to our network DC's
DNS IP and see if that makes a difference.

If this is a DNS issue, why would it allow login the first time afterjoining
the domain at all?

Any other possible causes?

Thank for the help,

Mark

"Jorge Silva" wrote:

Jorge Silva · Guest

Hi

- Make sure that every domain controller has its DNS properties under NIC
configuration pointing to itself. (If DC IP Address is 10.0.0.1 then Dns
should be 10.0.0.1).

- Make sure that every DNS server can resolve all domains in the forest.
(Use Forwarding, Stub Zones or Secondary Zones).

- Make sure that all clients Only uses the local(s) Dns Server.

- If you want to resolve internet names, just configure the forwarding on
your Dns server (Point to your local router or to your local ISP)

Active Directory uses DNS as a locator service, resolving Active Directory
domain, site, and service names to an IP address. To log on to an Active
Directory domain, an Active Directory client queries its configured DNS
server for the IP address of the Lightweight Directory Access Protocol
(LDAP) service running on a domain controller for a specified domain.

For more info:

How Domain Controllers Are Located in Windows

http://support.microsoft.com/kb/247811/

DNS Conditional Forwarding in Windows Server 2003

http://www.windowsnetworking.com/articles_tutorials/DNS_Conditional_Forwarding_in_Windows_Server_2003.html

DNS Stub Zones in Windows Server 2003

http://www.windowsnetworking.com/articles_tutorials/DNS_Stub_Zones.html

How To Create a Child Domain in Active Directory and Delegate the DNS
Namespace to the Child Domain

http://support.microsoft.com/kb/255248/

--
I hop that helps

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Mrpush" <Mrpush@discussions.microsoft.com> wrote in message
news:103AC210-21EE-4DF5-B665-037A2BD72BF4@microsoft.com...