User Environment Logging

home | blog | Teh Internet | guest blog |rants | placeholder | political | projects | Gwen and Liam | Citadel patched | Tools | Scouts


- Careful Chrome users, this search box might be "Not secure"


Do you have failures in your domain logins with roaming profiles?

This is the one that fixed it for my last battle with this crap:

Control Panel -> User Accounts -> Advanced tab -> Manage Passwords, and removed the user from the list (and of course reboot). 
5719 event id netlogon in syslog? (cached creds)...

http://support.microsoft.com/default.aspx?scid=kb;en-us;242536

Check for basic connectivity (can you ping the server, do you have a valid ip address from the dhcp server?)

If this is a remote office, check to see that the dhcp server is not handing out the isp dns records as this will be an epic fail if the dns records at the isp don't contain your internal host addresses - (which they should not!)

Run dnsdiag to determine other issues with name resolution.

Check date and time (cmos and system time) - skewed clock values can break Kerberos

Update drivers (nic and wifi cards!)

Check for firewalls (turn off, test, and turn back on if no difference) -check for blocking on tcp port 389

Uncheck "Enable IEEE 802.1x authentication for this network" if you are not using it.

Control Panel -> User Accounts -> Advanced tab -> Manage Passwords, and removed the user from the list (and of course reboot).

Remove machine from domain, and then re-join it.

Overlapping i/o and 1030 errors? http://support.microsoft.com/kb/555651/en-us (Also see stored password stuff below)...

Enable logging:

http://support.microsoft.com/kb/221833

Reg file on this page should do it, but if your machine breaks, you are on your own....

udebug.reg - winxp only! - Thanks eku.edu!

Parse this error set:

http://technet.microsoft.com/en-us/library/cc786775.aspx

or this handy tool:

http://www.sysprosoft.com/policyreporter.shtml

Ensure you are not wifi and impatient:

http://support.microsoft.com/kb/873485

Start > Run > gpedit.msc and press enter.

When the policy editor has loaded go to Computer Configuration > Administrative Templates > System > Logon, then option the option "Always wait for the network at computer startup and login" set to "enable", then exit.

let "Windows manager" manage your wireless connection (WZC)

-- Or --

Wish the user just nfs mounted home and used Linux :-)




[æ]