|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Authentication problems on member server (file/print)We had a SERVER3 that was a NT4 BDC in a remote site. We installed after the upgrade a SERVER2 that was a Windows 2003 domain controller. We removed the SERVER3. Recently we installed a new File and Print server with the name SERVER3.... Some users however (strangely not all) have problems to authenticate towards this server. Event Viewer shows on SERVER3 : Logon Failure: Reason: Unknown user name or bad password User Name: <username> Domain: SERVER3 Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: PLJETFLY015 Caller User Name: - Caller Domain: - Caller Logon ID: - Caller Process ID: - Transited Services: - Source Network Address: xx.xx.xx.xx Source Port: 0 For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I presume this has to do with the ancient name.... Sorry, Found the problem :
Control panel : accounts-->advanced-->manage passwords" The user was listed as "servername\username" instead of "domainname\username". PS : you have to make the user member of administrators before this works... Show quoteHide quote "IgnaceQ" wrote: > We upgraded our NT4 network about 1 year ago to Windows 2003 AD. > We had a SERVER3 that was a NT4 BDC in a remote site. We installed after the > upgrade a SERVER2 that was a Windows 2003 domain controller. We removed the > SERVER3. > Recently we installed a new File and Print server with the name SERVER3.... > Some users however (strangely not all) have problems to authenticate towards > this server. Event Viewer shows on SERVER3 : > Logon Failure: > Reason: Unknown user name or bad password > User Name: <username> > Domain: SERVER3 > Logon Type: 3 > Logon Process: NtLmSsp > Authentication Package: NTLM > Workstation Name: PLJETFLY015 > Caller User Name: - > Caller Domain: - > Caller Logon ID: - > Caller Process ID: - > Transited Services: - > Source Network Address: xx.xx.xx.xx > Source Port: 0 > > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > I presume this has to do with the ancient name.... I'm not sure by what you mean you have to make the users members of
administrators before this works but you are creating a maintenance nightmare for yourself in your domain if you are granting users admin rights on there local machines. -- Show quoteHide quotePaul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA This posting is provided "AS IS" with no warranties, and confers no rights. "IgnaceQ" <Igna***@discussions.microsoft.com> wrote in message news:0E799C84-7FC2-4244-AC0B-F957B85B215F@microsoft.com... > Sorry, Found the problem : > Control panel : accounts-->advanced-->manage passwords" The user was > listed > as > "servername\username" instead of "domainname\username". > PS : you have to make the user member of administrators before this > works... > > "IgnaceQ" wrote: > >> We upgraded our NT4 network about 1 year ago to Windows 2003 AD. >> We had a SERVER3 that was a NT4 BDC in a remote site. We installed after >> the >> upgrade a SERVER2 that was a Windows 2003 domain controller. We removed >> the >> SERVER3. >> Recently we installed a new File and Print server with the name >> SERVER3.... >> Some users however (strangely not all) have problems to authenticate >> towards >> this server. Event Viewer shows on SERVER3 : >> Logon Failure: >> Reason: Unknown user name or bad password >> User Name: <username> >> Domain: SERVER3 >> Logon Type: 3 >> Logon Process: NtLmSsp >> Authentication Package: NTLM >> Workstation Name: PLJETFLY015 >> Caller User Name: - >> Caller Domain: - >> Caller Logon ID: - >> Caller Process ID: - >> Transited Services: - >> Source Network Address: xx.xx.xx.xx >> Source Port: 0 >> >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> >> I presume this has to do with the ancient name....  
Thread options
Other interesting topics
Upgrading to Windows 2003 from Windows 2000
AD replication after a year W2K3 server time slow Failed to open the group policy object Unable to assign TerminalServicesHomeDrive Letter using script. Least amount of privileges How to setup an account as non Domain admin to join comps to domai Set et "inherit from parent the permission" on multiple user objects at same time Problem File share access and Failure of domain controller replication User Name in AD |
|||||||||||||||||||||||
