RE: Access server and prompted to logon with old domain

I'm not familar with SBS but is the old domain name the NETBIOS name of the
new domain?

Not a solution but a quick workaround, disable NTLM authentication option?
--
Steve G.
MCSA 2003 +M


"irtheman" wrote:

> Greetings!
> There is this one server that works well for most people but then there
>
> are a few, myself included, that can only logon without trouble at
> random times. I might be using the server just fine and then bam!
> Logon failure. When the logon fails the user is prompted to enter a
> password and the associated logon name is <old domain>\<user name>.
> Changing to the proper domain logon fails though. There are no
> machines here using that old domain and the domain controllers for it
> are long gone. I don't know where these XP Pro machines are getting
> this old logon name from. I can see the failure in the security log on
>
> the problem server. Good logons use Kerberos while all of the failed
> logons are using NTLM. If the user uses "net use" to delete all
> references to the problem server then they can logon again. But that
> is a serious pain in the neck. There are at least two users who have
> to reboot.
>
> We have been running on a new SBS 2003 domain for about a month now.
> The problem server was on the old domain and it migrated just fine.
> Since then, I have moved it to a workgroup and added it back to the new
>
> domain. I have also moved the server to a workgroup, removed the
> server account from SBS, deleted the SBS information on the server, and
>
> rejoined the server to the domain. No fix. I have also tried the same
>
> for the problem PCs.
>
>
> Any suggestions?
>
>
> Thanks!
> Matthew Hanna
>
>
> Event Log Entries (Note same user name and same day!)
>
>
> Event Type: Failure Audit
> Event Source: Security
> Event Category: Logon/Logoff
> Event ID: 529
> Date: 11/14/2006
> Time: 11:25:08 AM
> User: NT AUTHORITY\SYSTEM
> Computer: LIMA
> Description:
> Logon Failure:
> Reason: Unknown user name or bad password
> User Name: mhanna
> Domain: appsci
> Logon Type: 3
> Logon Process: NtLmSsp
> Authentication Package: NTLM
> Workstation Name: MATTHANNA
> Caller User Name: -
> Caller Domain: -
> Caller Logon ID: -
> Caller Process ID: -
> Transited Services: -
> Source Network Address: 192.168.100.50
> Source Port: 0
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type: Success Audit
> Event Source: Security
> Event Category: Logon/Logoff
> Event ID: 540
> Date: 11/14/2006
> Time: 10:36:55 AM
> User: ASA\mhanna
> Computer: LIMA
> Description:
> Successful Network Logon:
> User Name: mhanna
> Domain: ASA
> Logon ID: (0x0,0xAD803B2)
> Logon Type: 3
> Logon Process: Kerberos
> Authentication Package: Kerberos
> Workstation Name:
> Logon GUID: {c541bb95-4c50-845c-cdc1-4d2c94637bfe}
> Caller User Name: -
> Caller Domain: -
> Caller Logon ID: -
> Caller Process ID: -
> Transited Services: -
> Source Network Address: 192.168.100.50
> Source Port: 0
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>