http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382
Windows 2003 Server by default also requires SMB signing which sometimes causes
problems. It may be worth to disable it at least temporarily in either the Domain
Controller Security Policy for domain controllers or the Local Security Policy [or
OU ] for a non domain controller in security settings/local policies/security options
where you want to disable digitally sign communications(always) for network
erver. --- Steve
"DonD" <dier...@cox.net> wrote in message
news:15pnj0dakveaqjudo...@4ax.com...
"DonD" <dier...@cox.net> wrote in message
news:60aqj0h1ieh12120u...@4ax.com...
When I first switched from 2000 to 2003 I eliminated this
logon problem within 5 minutes of someone complaining, but I forgot to write
down what I did.
"Steven L Umbach" <n9...@n0-spam-for-me-comcast.net> wrote in message
news:tJv%c.51863$3l3.17528@attbi_s03...
-- Make sure on the Windows 2003 Server that the guest account is enabled and that
the everyone group is in the user right for access this computer from the network in
Local Group Policy. Everyone permissions are needed for both share and ntfs
permissions. Also for the server in Local Group Policy in security settings/local
policies/security options make sure the security option for Network Access: Let
everyone permissions apply to anonymous users is set to enabled, Network Access: Do
not allow anonymous enumeration of sam accounts and shares is set to disabled. If
you make changes on the server then run gpupdate /target:computer /force on it and
reboot a client computer and try again.
-- If still a no go change the security option for Network Access: Sharing and
security model for local accounts to be "use guest only" if it is not that
already. --- Steve
"DonD" <dier...@cox.net> wrote in message news:w9H%c.172980$Lj.5055@fed1read03...