Wired problem

From: Ray (ray_at_utah.edu)
Date: 10/05/05 

Date: Tue, 4 Oct 2005 20:59:55 -0600

Hi there,

I still have problem when Macintosh tries to access shared folder on Windows
2k3, which is a member server of our domain but not a domain controller. The
user can access the shared folder without any problem on Windows XP, but he
also can browse other windows computers but it cannot access the shared
folder after clicking "Connect". The wired problem is that he just tried
once, but event viewer said three times and he's locked out at once. Here is
what I found in event viewer, exactly same for the three times,

Logon Failure:

Reason: Unknown user name or bad password

User Name: chris

Domain: CS

Logon Type: 3

Logon Process: NtLmSsp

Authentication Package: NTLM

Workstation Name: \\CSLYONLAP1-

Caller User Name: -

Caller Domain: -

Caller Logon ID: -

Caller Process ID: -

Transited Services: -

Source Network Address: xxx.xxx.xxx.xxx

Source Port: 0

I appreciate any suggestion.

Ray

Relevant Pages

  • Re: Domains
    ... > to the domain on Windows XP Logon, but there are times that when the ... > that has a shared folder. ... internal/AD-integrated DNS server's IP address in their network settings. ...
    (microsoft.public.windows.server.general)
  • Re: Domains
    ... > to the domain on Windows XP Logon, but there are times that when the ... > that has a shared folder. ... internal/AD-integrated DNS server's IP address in their network settings. ...
    (microsoft.public.windows.server.networking)
  • NTLM
    ... It seems that I have a problem with NTLM in my Windows 2003. ... access a program located in Windows 2003 server using my Win2K Professional. ... An error occurred during logon ... Caller User Name: - ...
    (microsoft.public.win2000.security)
  • Re: Thousands of Event Log Entries
    ... I've got a Windows 2003 Server, Standard Edition, ... | Successful Network Logon: ... | Caller User Name: - ...
    (microsoft.public.windows.server.general)
  • Re: NTLM
    ... Forged SID Could Result in Elevated Privileges in Windows ... > Logon Failure: ... > Substatus code: 0x0 ... > Caller User Name: - ...
    (microsoft.public.win2000.security)