10 replies
by bfilmfan
Are these systems members of a domain?
Are NTFS permissions beign applied to the systems?
If either of these are true, you are not going to be able to use blank passwords, which is a truly bad idea.
by bfilmfan
By the way, could you rate the answer given here?
https://www.techrepublic.com.com/5208-11184-0.html?forumID=47&threadID=167496&start=0
by sgt_shultz
by olojtd4
by grebon
by xt john
Have you tried running a net use command with the option of persistent:yes at the end? this will enable the pc to always connect. The syntax for the net use is:
Type net use x: \\computer name\share name, where x: is the drive letter you want to assign to the shared resource.
At a command prompt type net use/? for more attributes. We were successful using this on a public account that didn't have a password, that public account was locked down tight by group policy editor and third party software.
The following discussion is from the Windows XP Resource Kit (http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/windows/xp/all/reskit/en-us/prdp_log_tyry.asp). While I haven't confirmed it, I'm sure the same applies to Windows Server 2003 and is the source of your problem.
To protect users who do not password-protect their accounts, Windows XP Professional accounts without passwords can only be used to log on at the physical computer console. By default, accounts with blank passwords can no longer be used to log on to the computer remotely over the network, or for any other logon activity except at the main physical console logon screen. For example, you cannot use the secondary logon service (RunAs) to start a program as a local user with a blank password.
Assigning a password to a local account removes the restriction that prevents logging on over a network and permits that account to access any resources it is authorized to access, even over a network connection.
If you want to disable the restriction against logging on to the network without a password, you can do so through Local Security Policy. The policy setting that controls blank password restriction can be modified using the Local Security Policy or Group Policy MMC snap-ins. You can use either tool to find this policy option at Security Settings\Local Policies\Security Options. The name of the policy is Accounts: Limit local account use of blank passwords to console logon only. It is enabled by default.
by richard
by noly_big_boy
by pritchards
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending