If your computer's not a member of the domain go into control panel, user
accounts. Select your account, select manage network passwords. Add an
entry for *.<domain>. For example: *.foo.com
For id put in your domain\userid and your password where expected.
Next open up internet explorer and go into tools/options
Select the security tab
Select Local Intranet
Hit the sites button
Unselect "automatically...."
Hit Advanced
Make sure your domain is listed under the "websites" area. Example
*.foo.com
Uncheck "require server verification (https)"...
Hit close, ok
Select the "custom level" button
Scroll down to "user authentication"
make sure "automatic logon only in the intranet zone" is selected
press ok
press ok
If your DHCP server isn't properly handing out the domain name (in other
words if \\server isn't automatically being resolved as \\server.domain)
then go into network and sharing center.
click on manage network connections
Select the network connection in question and properties
Select tcp/ip (v4)
Select properties
Select advanced
Go to DNS tab
Add foo.com in the list of domain suffixes to automatically append
When you map the drive, use the FQDN of the server (example:
\\server.foo.com instead of \\server)
Or, to avoid all of the above, add your machine correctly to the domain.
Reboot.
"Eric Marinko" <(E-Mail Removed)> wrote in message
news:C9927BDF-48F8-435C-8A81-(E-Mail Removed)...
> Hi,
>
> I'm running Windows Vista Business with a network drive mapped to a server
> running Windows 2000 SP 4, admin share d$. If I do not check "Remember
> Password" my account on the server gets locked out EVERY TIME I reboot my
> Vista PC and log back in.
>
> Even with "remember password" checked, the account gets locked out
> occasionally when rebooting, it seems perhaps, after installing some
> software
> or making a change that required reboot.
>
> I've seen a posting that suggested Vista repeatedly tries to log in with a
> blank password which causes the lockout. Even if a user forgets to
> check
> off this box, it doesn't make any sense to try repeatedly to login with a
> blank password. That is surely a problem. In that event, there should
> be
> a prompt after the first failure rather than blasting away at the server
> until the the account is locked out.
>
> Anyone know of a solution? Fixes coming?
>
> This is a major annoyance. Fortunately I have admin access on the server
> so
> I can "remote in" and unlock my account. Otherwise, this would be a show
> stopper.
> --
> Eric Marinko
|