2 win 7 systems require login

[1415]

I have a LAN with 4 systems: three Win 7 and one XP Pro. I have removed the Homegroup.
All the systems can see each other and access a shared folder with the exception of System1 and System (both Win 7), which require a user name/password to access the shared folder on the other system.
For example, if from System1 if I try to access System 2's shared folder, I get "Windows Security" login text entry window:
"Enter Network Password. Enter your password to connect to System2."
For "Username", I enter "\\system1".
For Password, I enter a password from the previous Home Group.
I can check "Remember credentias" but that works only until the next reboot.
Oddly, one sees under the "Password" text entry this: "Domain: System1" even though there is not domain, only a workgroup.
Likewise, from System2, I can access the shared folder on System1 by entering username "\\system2" with the same old homegroup password. Here I see "Domain: System2" even though there is no domain on System 2.
"Use usernames and passwords" is turned off in Advanced Sharing on all systems.
I want to get rid of this requirement to share between Systems 1 and 2.
Thanks in advance to the Windows experts.

 

[TheKub]

Guess I am a bit confused as to what is going on by your description and its been awhile since I ran XP at home but if you have a local account on each system with the same logon and same password you should not be prompted. Alternatively, you can simply map a drive using different credentials and make it persistent.

 

[1415]

The two systems having problems are both Win 7, Home Premium. How would I map a folder using different credentials and make it persistent. Even though I check the box to do that, on the next reboot the username/password are again asked for.

 

[TheKub]

I don't commonly use Home Premium but I doubt these features are unique to Pro/Ent/Ult. When you say you check the box "to do that" what box are you referring to? Use alternate credentials or save credentials?

If its the later and the credentials are not being retained perhaps creating a batch file with Net Use and your credentials to run as a logon script.

 

[1415]

Of the 3 Win 7 Systems, #1, 2, and 3, the shares on System 3 can be seen by all the other systems and System 3 can see all the other shares. However, between System 1 and 2 there is a problem: although no password is required (after reboot), for System 1 to see System 2, System 1 must log in with "\\System2" and vice versa. How can I get complete file sharing without logins?

 

[ViRGE]

Maybe I'm missing something, but why are you using double-backslashes in the username? Isn't that a special sequence in Windows?

 

[1415]

I was using double backslashes, as required, for the system name. Should I be using 1 backslash for the system name?

 

[mechBgon]

My suggestion:

1. create a Standard User account on each system, and give it a password

2. when you see that prompt use name of other system\name of its Standard User account as the username, and check the box for it to remember the credentials


That should get the job done. You can edit this credential on Win7 by clicking Start and typing Credential Manager. If necessary, adjust permissions on the stuff you want to access remotely, so the Standard User accounts can access what they need to.

The reason for using Standard User accounts is that if one system were to get compromised, it wouldn't have Admin-level privileges over the other system, so it would limit the damage.

I was using double backslashes, as required, for the system name. Should I be using 1 backslash for the system name?

In a Windows username/password prompt for a remote system, you only put a backslash between the name of the other system, and the name of the other system's user. That tells the other system that you're referring to one of its user accounts, not a user account from the system you're on. As soon as you type the other system's name and a backslash, you'll see the panel change to Domain: other system's name.

 

[1415]

Your solution appears to have worked when I entered from System1: "system2\.." and not "\\system2\.." nor "\system2\..."

BTW, if your methodology is still working tomorrow after reboots, then you are the only one on the net who has solved this thorny Win 7 share issue over the last 10 days.
I have rebooted several times: your solution works.
For a shared folder, who should have access: Everyone, Guest, or both or neither?

Now for the issue you raised. I went into User accounts on System1. I now remember the reason I never created a Standard user acccount. I will constantly have to switch into Admin account to do almost anything on the system. As it is, logged in as Admin, many programs, because of my UAC control level, constantly ask for Admin permission before the programs open.

 

[mechBgon]

Your solution appears to have worked when I entered from System1: "system2\.." and not "\\system2\.." nor "\system2\..."

BTW, if your methodology is still working tomorrow after reboots, then you are the only one on the net who has solved this thorny Win 7 share issue over the last 10 days.
I have rebooted several times: your solution works.
For a shared folder, who should have access: Everyone, Guest, or both or neither?

I'd give access to the system's local Users group to start with. The remote systems will be using one of the local Standard User accounts, and your Admin account is also normally toting User powers, so that should get the job done.

Now for the issue you raised. I went into User accounts on System1. I now remember the reason I never created a Standard user acccount. I will constantly have to switch into Admin account to do almost anything on the system. As it is, logged in as Admin, many programs, because of my UAC control level, constantly ask for Admin permission before the programs open.

I see. There are no up-to-date versions of these programs that can function without being granted a dangerous level of privilege? Those software makers better get with the program, it's not 2001 anymore.

Regardless, create that Standard User account anyway, and give it a password. Even if you don't use it locally, it still provides the other computers a set of non-Admin credentials they can use to authenticate with.

The \\computername format is used when you're browsing the network, that's where the double backslashes are used.

 

[1415]

I got that wrong about programs asking for Admin permission. The problem, which is just as bad, is the Windows UAC constantly asks to be allowed to open progams. I could drop UAC to the lowest level to avoid that, but then would not have any UAC protection.

 

[mechBgon]

I got that wrong about programs asking for Admin permission. The problem, which is just as bad, is the Windows UAC constantly asks to be allowed to open progams. I could drop UAC to the lowest level to avoid that, but then would not have any UAC protection.

They amount to the same thing: for some reason, the programs need (or think they need) Admin-level control over your system. I have a few programs like that, so I know where you're coming from.