usernam@domain_name vs domain_name\username

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm wondering why I have a problem logging in to an AD (win2k) network using
the username@domain_name format. I get a message stating that the the account
is unknown or bad password. If I use the older domain_name\username format,
login is successful. I'm hitting on a backup domain controller when I have
this problem, but if I point the default gateway for the server to allow
connection to the primary DC, I'm then able to connect using the
username@domain_name format.

I'm sure this is just a matter of the backup DC not being set correctly in
some manner, but I don't know what that would be.

TIA,
Ken
 
kmkrause2 said:
I'm wondering why I have a problem logging in to an AD (win2k) network
using
the username@domain_name format. I get a message stating that the the
account
is unknown or bad password. If I use the older domain_name\username
format,
login is successful. I'm hitting on a backup domain controller when I have
this problem, but if I point the default gateway for the server to allow
connection to the primary DC, I'm then able to connect using the
username@domain_name format.

I'm sure this is just a matter of the backup DC not being set correctly in
some manner, but I don't know what that would be.
Click to expand...

In a single domain forest every DC should be a GC.

Every DC should also be able to pass a "DCDiag /c" (complete) clean
without FAIL or WARN messages.
 
Thanks both for your responses. I kinda thought it was going to be something
rather elementary for AD.

Ken
 
kmkrause2 said:
Thanks both for your responses. I kinda thought it was going to be
something
rather elementary for AD.
Click to expand...

Usually it (replication and authentication) is DNS related, but also GC,
time sync, firewalls/fitlers, routing, and hardware problems.
 
Back
Top