Ed,
This is definitely outside of the content scope of the list, but there are
some issues with old NT 4.0 domain controllers and Windows 2000 AD after a
migration. If in fact that is your setup. Your event log on either the
client or the server will be littered with Event ID: 1000 Source: Userenv.
First verify that the blank username isn't causing the problem. If it isn't
then, stop the netlogon service on all of the downlevel DCs. Upgrade the
Windows 2K controllers with either SRP1 or SP3 (I suggest SRP1). Then have
users and controllers reauthenticate with the W2K DC. This goes for any
services or apps that depend on domain account information. You can use the
SET command at the clients/servers to verify which DC authenticated the
user/service. Leaving the netlogon service as manual or disabled on the NT
4.0 DCs won't hurt anything unless the W2K box has a problem and is the only
entity left on the network that authenticates users.
I've run into this problem several times. I hope this helps.
Guy Goodenough
Dataprise, Inc.
-----Original Message-----
From: Ed Murphy [mailto:Ed.Murphy@xxxxxxxxxxxxx]
Sent: Thursday, September 19, 2002 12:59 PM
To: 'ethereal-users@xxxxxxxxxxxx'
Subject: [Ethereal-users] Netlogon failure - possibly emtpy username?
Hi,
I'm seeing a SAM response indicating a netlogon failure "user unknown" in my
ethereal output. I've seen a small reference in another mailing list that
this may be due to the user name being blank on WIN2K in the MS Windows
Logon Protocol block. I checked and it is blank.
I haven't been able to find any more information about whether this is a bug
or not, nor any advice on exactly where to begin to fix it if it's a
problem. Can anyone shed some more light on this, at least to let this
network newbie know if I'm way off base?
Regards,
Ed Murphy
504-293-2527 (office)
504-237-4369 (cell)
ed.murphy@xxxxxxxxxxxxx
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users