@anonymous: "I recently set up a trust between a new Server 2003 and 
an existing NT server.  This morning when users were 
trying to log on to the NT domain they were denied access-
-they had not needed passwords previously but they now 
need one.  I imagine the Server 2003 and  Active 
directory has changed the password for security 
pyrposes.  I removed the trusts and
I have changed the password  for each user in the Users 
Manager on the NT, but they are still being denied acess.
I am remotely tying to resolve the issueI may try and 
get on-site to handle this but in the meantime if anyone 
has information with regard to solving this issue, it 
would be greatly appreciated."
    @MichaelGiorgio: "Can you describe your setup in detail?  The W2k3 server
is a domain controller for a newly created W2k3 domain or
a member server?  When you broke the trusts were you able
to re-establish the trusts successfully?  The W2k3 server will
not change the user accounts or passwords at all it will pass
the credentials back to the NT 4.0 domain for authentication
assuming it can find an NT 4.0 DC for authentication.
<quote>"
    @anonymous: "The Server 2003 is new and was set up for a new domain.  
I have not tried to re-establish the trusts.
The exact message when a user from the NT domain tries to 
log on to the domain is:  
"Domain password you supplied is not correct or access to 
logon server is denied".
I was not planning on setting up trust between the two 
serversthe NT is being removed form the network as soon 
as a customized application is ready for a go live.  I 
created the trusts to try and share printers on the 
network.  Once a trust is created and then removed, does 
the authentication not just go back to the domain PDC?
Also, why is it after never having to supply a user 
password to access the NT server, we must enter one now?  
I created the trust a week ago and this morning was when 
the first problem occured. If I change the password for a 
user on the NT, the password always seems to change to a 
14 character password.
  Thanks
<quote>
server will
pass
authentication
message
access-
acess.
anyone"
    @MichaelGiorgio: "I apologize for somewhat of a stupid question but could
the netbios name of the new domain be the same e.g.,
existing domain abc and the W2k3 domain name
e abc.com?  Immediately after the unsuccessful logon
attempt open a dos prompt and run nbtstat -c then verify
the domain name 1b and 1c names are pointing towards
the existing NT server and not the new W2k3 server.
<quote>"
    @anonymous: "The domain names are different: abc and abcmi.local 
I have shut down the new Server 2003 for the moment.  We 
renamed the user accounts on the NT from user to user1 
and added a new user for each client with the original 
user name, created a password and we can now log on to 
the NT server.
They are okay for the moment, I will be on-site over the 
weekend and will take a better look at the situation.
I still don't know why, after all these years of not 
having to use a password, a password was needed to access 
the NT today.
<quote>
to
to"
    @MichaelGiorgio: "Hi Shelley
Answers inline.
<quote>
Well they are kind of similar.  The netbios name of the
W2k3 domain should have defaulted to abcmi.  You
can check the netbios name by opening a dos prompt
on the server and running nbtstat -n then check the 1b
netbios name.
After shutting down the W2k3 server the users still had
problems?
It looks as if the clients were attempting to logon
to the W2k3 server and not the NT 4.0 domain
controller."
{'source': 'USENET', 'other_information': '{"reply_count": 5, "forum_name": "microsoft.public.windowsnt.domain.20140401.mbox"}', 'file': 'data/output/usenet-microsoft.public.parquet'}