Re: Unable to authenticate to untrusted domain NTLM v2 related issue

followups are in the other subthread in reply to Steve's post

"lwoody7110" <lwoody@xxxxxxxxxxxxx> wrote in message
news:1158140168.688893.233410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Member server eventvwr security logs are as follows....

Method. Net use \\%servername\share
Server challenges me for username and password

The eventlog generates three events on the member server in Domain B.
(There are no events on the DCs)

#1

Successful Network Logon:
User Name:
Domain:
Logon ID: (0x0,0x179FE1)
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: Domain A XP SP1 PC
Logon GUID: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 10.***.***.***
Source Port: 0


#2

User Logoff:
User Name: ANONYMOUS LOGON
Domain: NT AUTHORITY
Logon ID: (0x0,0x179FE1)
Logon Type: 3


#3

Successful Network Logon:
User Name:
Domain:
Logon ID: (0x0,0x17A07B)
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: Domain A XP SP1 PC
Logon GUID: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 10.***.***.***
Source Port: 0




I can successfully map from XP SP1 to domain B member server using a
local account on the member server.

I agree with your assesment that member servers are not apparently
apparently supporting the NTLM requirements of the clients.



.

Relevant Pages

  • Re: ISA SERVER NOT STARTING
    ... I delete the nat/basic firewall and stop and started the RRAS an tried to ... There were no critical events in the DNS Server Log in the last 24 hours. ... An error occurred during logon ... Caller User Name: - ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 529
    ... First is a hardware firewall that sits on the perimeter of your network and requires that your users give user names and passwords, different from those for the network. ... Sometimes the Logon Type is different, also the User Name can be ... Computer: <SERVER NAME> ... Caller User Name: $ ...
    (microsoft.public.windows.server.sbs)
  • Re: Another security question/issue.
    ... Time to audit your server and workstations with AV, Malware, and installed ... Logon Process: Advapi ... Caller User Name: servername$ ... Source Port: - ...
    (microsoft.public.windows.server.sbs)
  • Re: Logon 529 Errors
    ... Default SMTP Virtual Server properties-Access tab-Relay ... Connection filtering is different from what inna is attempting, ... These are almost surely SMTP logon attempts, ... Caller User Name: DELLSERVER$ ...
    (microsoft.public.windows.server.sbs)
  • Re: Logon 529 Errors
    ... connection has been found on the black list, my DNS server ... Connection filtering is different from what inna is attempting, ... These are almost surely SMTP logon attempts, ... Caller User Name: DELLSERVER$ ...
    (microsoft.public.windows.server.sbs)