Re: Security log chaos - could not get dsclient.exe to install on any 9x boxes

From: Travis Kwekkeboom (totoro_orotot_at_hotmail.com)
Date: 07/28/04


Date: Wed, 28 Jul 2004 17:11:16 -0400

Well in the kernel end of things .. I know two kernels.
NT kernel (NT, win2k, XP Home, and XP Pro) and 9x kernel
(95,98/se,WinME) Usually it is assumed that 9x consists of
95/98,se/WinME. So, the ME box is dead. Dandy, well we are pushing
the ME boxes towards XP Pro, so that will help. I will re-OS this box
and everything should be happy, cept me. heheh.

See, the only boxes that were giving me trouble were the WinME boxes,
I thought I had put that in a previous post, however, if I did not I
apologize. Any ideas how I can rip that DSclient.exe out?

On Wed, 28 Jul 2004 20:21:53 +0200, "Erik Veenhuijsen"
<erikv70@hotmail.com> wrote:

>Travis, i don't know how big your knowledge is, but you really created a
>problem with this one.
>
>In your post you spoke about Win9x machines, not about WinME machines (you
>know that ME cannot be used in a domain environment? adclient or not.)
>If all your machines are WinME, then no adclient or WINS will help you,
>cause you have to wrong OS for a network domain. You should use win98se or
>higher (expect WinME and WinXP Home edition).
>
>See also:
>http://support.microsoft.com/default.aspx?scid=kb;en-us;276472&Product=winme
>
>One positive thing, probably your SBS box is ok, but the OS on the client
>absolutly isn't. Hopefully it's on just one box and all others are ok.
>
>See also:
>http://support.microsoft.com/default.aspx?kbid=288358
>
>Greets,
>Erik.
>
>
>
>"Travis Kwekkeboom" <totoro_orotot@hotmail.com> wrote in message
>news:15idg0p6l6mh47oq06vjl6hkvvemu9rprc@4ax.com...
>> Well I installed the dsclient9x.exe on the one WinME box and now I
>> can't log into the domain. I tried uninstalling the client, it says it
>> completes, restart then I get the SAME non-network login and I can't
>> access anything. Dandy client there. ruined everything.
>>
>> Anyways, I am out of the office tomorrow all day and I will have to
>> RE-OS THAT box, probably the SBS2000 server and set everything up this
>> weekend .. not a task I was prepared to do. I am a little peeved over
>> this.
>>
>> Travis Kwekkeboom
>>
>> On Mon, 26 Jul 2004 23:33:03 +0200, "Erik Veenhuijsen"
>> <erikv70@hotmail.com> wrote:
>>
>> >Strange error, did you make sure you used the dsclient.exe in the win9x
>> >directory?
>> >Also you should setup a WINS server on your network and put the ip adress
>of
>> >your WINS server in the TCP/IP protocol on your workstations, otherwise
>they
>> >won't be able to find a Domain Controller for account logon.
>> >
>> >
>> >"Travis Kwekkeboom" <totoro_orotot@hotmail.com> wrote in message
>> >news:vvrag0lvpdnvgranj252sdabii12sl6lic@4ax.com...
>> >>
>> >> run the dsclient and I get a message telling me that the application
>> >> has not found WinNT SP6a and will exit. That is it.
>> >>
>> >>
>> >> On Mon, 26 Jul 2004 11:23:04 -0400, Travis Kwekkeboom
>> >> <totoro_orotot@hotmail.com> wrote:
>> >>
>> >> >This one has been bugging me for quite some time. I have people on
>> >> >Win9x boxes who keep getting their accounts locked out for reasons
>> >> >beyond me. 1st I thought it might be a timing server issue (which it
>> >> >might still be)
>> >> >
>> >> >Event Type: Failure Audit
>> >> >Event Source: Security
>> >> >Event Category: Account Logon
>> >> >Event ID: 681
>> >> >Date: 7/20/2004
>> >> >Time: 1:09:28 PM
>> >> >User: NT AUTHORITY\SYSTEM
>> >> >Computer: SLS-SERVER
>> >> >Description:
>> >> >The logon to account: XXXX XXXXXXXXX
>> >> > by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
>> >> > from workstation: \\XXXXXXXXXXXXXXX
>> >> > failed. The error code was: 3221225578
>> >> >
>> >> >and then
>> >> >
>> >> >Event Type: Failure Audit
>> >> >Event Source: Security
>> >> >Event Category: Logon/Logoff
>> >> >Event ID: 529
>> >> >Date: 7/20/2004
>> >> >Time: 1:09:28 PM
>> >> >User: NT AUTHORITY\SYSTEM
>> >> >Computer: XXXXX-SERVER
>> >> >Description:
>> >> >Logon Failure:
>> >> > Reason: Unknown user name or bad password
>> >> > User Name: SSSSSSSSSSSSSSSSSS
>> >> > Domain: DomainName
>> >> > Logon Type: 3
>> >> > Logon Process: NtLmSsp
>> >> > Authentication Package: NTLM
>> >> > Workstation Name: \\XXXXXXXXXXXX
>> >> >
>> >> >and then
>> >> >
>> >> >Event Type: Success Audit
>> >> >Event Source: Security
>> >> >Event Category: Account Management
>> >> >Event ID: 644
>> >> >Date: 7/20/2004
>> >> >Time: 1:14:53 PM
>> >> >User: Everyone
>> >> >Computer: XXXXX-SERVER
>> >> >Description:
>> >> >User Account Locked Out:
>> >> > Target Account Name: XXXXXXXXXXXXXX
>> >> > Target Account ID: XXXXXXXXXXXX\XXXXX
>> >> > Caller Machine Name: \\XXXXXXXXXXXXXXXX
>> >> > Caller User Name: XXXXXX-SERVER$
>> >> > Caller Domain: DomainName
>> >> > Caller Logon ID: (0x0,0x3E7)
>> >> >
>> >> >
>> >> >and then
>> >> >
>> >> >Event Type: Success Audit
>> >> >Event Source: Security
>> >> >Event Category: Account Management
>> >> >Event ID: 642
>> >> >Date: 7/20/2004
>> >> >Time: 1:14:53 PM
>> >> >User: Everyone
>> >> >Computer: XXXX-SERVER
>> >> >Description:
>> >> >User Account Changed:
>> >> > Account Locked.
>> >> > Target Account Name: XXXXXXXXXXXXXXXX
>> >> > Target Domain: Domain Name
>> >> > Target Account ID: XXXXXXXX\XXXXXXXX
>> >> > Caller User Name: XXXXXXX-SERVER$
>> >> > Caller Domain: Domain Name
>> >> > Caller Logon ID: (0x0,0x3E7)
>> >> > Privileges: -
>> >> >
>> >> >then the account has to be unlocked.
>> >> >
>> >> >Anyone have any ideas?
>> >> >It is a bothersome event.
>> >> >
>> >> >TK
>> >> >
>> >> >Follow-up: ******************
>> >> >
>> >> >I have scanned the server for viruses from MANY sources and have come
>> >> >up with negatives everywhere. This only happens to 9x series
>> >> >machines. I have a time script running on startup to synch the time
>> >> >to the server, that is about all I have done to these things besides
>> >> >stock and SP's.
>> >> >
>> >> >Help.
>> >> >
>> >> >TK
>> >>
>> >
>>
>



Relevant Pages

  • Re: Security log chaos - could not get dsclient.exe to install on any 9x boxes
    ... the WinXP Home of 9x kernel. ... redhat box and 7 ME boxes. ... Sat for the Win2k Pro exam and did not pass. ... WinME is based on a win9x kernel, ...
    (microsoft.public.backoffice.smallbiz)
  • Re: problems with latest smbfs changes on 2.4.34 and security backports
    ... something different on my samba server or similar, ... the client is an IBM NetworkStation 1000 (a PowerPC ... seems a security problem and I don't think is desirable, ... It is possible that you booted a wrong kernel during one of your tests. ...
    (Linux-Kernel)
  • Re: NFS EINVAL on open(... | O_TRUNC) on 2.6.23.9
    ... Thanks to Chuck's help i finally decided to proceed to a git bisect and found the bad patch. ... What isn't quite clear to me is whether this commit causes your user- space server to start failing suddenly, or it causes the client to start sending the special non-standard time stamps in the SETATTR request. ... it would be helpful if you could run this test with a constant kernel version on one side while varying it on the other. ...
    (Linux-Kernel)
  • Re: Debian replicator boot disk problem
    ... I can connect from an other client in the LAN 192.16.0.12 pretty good. ... How could the server write this in its syslog, ... the mount request. ... to keep the kernel image small, and have trouble determining what to include ...
    (comp.os.linux.misc)
  • "CIFS VFS: server not responding" with some client/server combinations
    ... As it might be kernel related and others ... A Samba server running Debian Etch with latest updates. ... I don't know what's different with Etch on the client, ...
    (Linux-Kernel)