Your computer is now connected, or mapped , to the network drive. Using windows 7 I have a NAS drive that I need to manually log into everytime my machine us started up - I want it to remember the login details and do it automatically when the machine starts as my wife also uses it and I want the auto backup to run.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. I've not tested it on old boxes like this, but if you want to avoid using credentials, then the share and it's computer you want to use should be within the same Kerberos realm as the client system.
Unfortunately this is in a workgroup environment and not a domain, I should have included this in my original post. A login script is going to run on login, but the drive needs to be mapped before login so that RemoteApp will work as the application will only launch if there is no user currently logged in to the Win XP machine. Just map the drive normally and make sure "reconnect at next logon" is checked and use different credentials if you so wish. Mapped driver are going to be authenticated in the user not computer context and I don't know of any way to override this.
Not ideal I know, but if you grant the everyone group read only access that'll obviously give you access to the data without creds. If its read only unless theres some big secrets in there no one can do any harm. You can use the net use command mentioned above. If I remember right, I think new connections are remembered automatically. Or if you suspect the machine is being logged on before network connections are ready, you can try a local group policy:.
I think the issue I have here is that I need the drive to be mapped without logging in as the RemoteApp relies on the user of the Win XP being logged off in order to launch the application. Reconnect at login option does not seem to work because I assume the RemoteApp is looking for the application before the mapped drive has successfully reconnected on login.
I did put the script into the startup folder via Local Computer Policy under Computer configuration but this did not work and when I ran it up manually it requested a username and password, and we would prefer not to include these details in the script if possible.
There is the option of using different credentials to authenticate, but this would involve creating a secondary account on the Win 7 machine which might confuse the user on startup when they see a second account visible.
I did also try giving the group ' Everyone ' full control in the hope that this wouldn't request credentials when the script was launched but it still did unfortunately. If that makes sense.. I might try this Local Policy setting - I have used this for software deployment via GP in the past to good success. If you want to turn off password protected sharing you need to ensure the guest account is enabled on both boxes as this is what it will use, by default it tends to be disabled.
I don't think I enabled the Guest account on either when I turned off password protected sharing - I would like to try this, but it will still create a second user account that is visible on login to the user on the Win 7 machine which is something we was trying to avoid if possible. With regards to the Everyone group, I think I gave Full control on the folder permission and likewise, or owner on the share permissions. I am not sure our RemoteApp configuration is working correctly. If the Win XP machine is not logged on, then the application launches as expected but if there is someone logged into this machine, the Win 7 user has to expand the RemoteApp window, and choose to disconnect the user currently logged on.
Or give the "password" out to everyone. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. None of the 3 computers have passwords no need in my environment , they are all on the same workgroup, and each has had the sharing turned on with full permissions I am not worried about someone getting at the files. I have never used or setup home groups on any of them. In the past all 3 computers could access each others files except for windows and program files folders.
Recently, I added a biometric fingerprint reader to one computer not the server so that I could have certain programs 'start' with a fingerprint scan versus typing in a password e. When installing the reader, I was forced to create a Windows Login password on the one computer that has the reader. It does work fine, but now every time I try to go to ANY folder on ANY of the other two computers including the server , a requester pops up asking for user ID and password. So, I enter in the user ID which is the same on each computer , leave the password blank and click OK.
Until I reboot, I have no problem going to that computer. Can someone explain which of the above fixes I should use on the computer that now has the scanner, so that when I go to my 'server' computer I do not have to enter in 'credentials' after every reboot? Well, I found the solution to my specific scenario after re-reading the above posts and other forum posts.
Computer 3 is my basement computer, has user ID basement, has no password. Finally I left the password empty since there was not one on that computer if there was a password, it would be entered here. Click OK. Since making this change, I have not been asked for any information - it connects up like before I had the password enabled on my computer. After doing this, I am back all computers being able to get to each other, without any need to log in. Hi, thank you for the hint.
What is "username LocalMachine"? Is it ". When I set it up directly in C. I put the name of my server without any slashes, then the logon name, again no slashes, and then the password. Saved it and went back and it said Enterprise. That was the key for mine. Hope it helps someone Just in time for WIndows 10 to come mess it up again!! We have moved to the cloud with no server - this item is an external drive - a NAS. We are operating in a workgroup environment now. If you can't understand that, anything we say won't help either.
You are an idiot. Go pay someone to fix your shit. In case you run into errors Test again with above command Things to do when in trouble direct copy pastes without source because I'll probably be not allowed just to copy paste links in this comment Do a "net use" command and see what is there. To remove the incorrectly labeled mapped drive, follow these steps:.
Sometime Windows gets confused. After a power outage, switch failure, crazy network card packets, dhcp availability or for no reason at all, you can have network drive letters that conflict with needed drive letters and you can't get rid of these orphans. In one case after a power issue, I saw the usual drives from logon scripts get remapped as 'removable drives'.
This netbios naming conflict resulted in home drives not mounting and no access for users. Needless to say, they were annoyed. Locate the mapped network drive that you want to clear. Right-click on the drive entry and select the "Delete" option from the contextual menu, then confirm your decision to remove the mapped drive letter assignment.
Restart your Computer to reread the Registry. Office Office Exchange Server. Not an IT pro? Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Windows 7 Networking. Sign in to vote. Changed type Mark L. Ferguson Thursday, February 5, PM bug , sent feedback.
Friday, January 16, AM. My laptop is domain-joined, btw. Friday, January 16, PM. It does the same for me. Forgets the drives every reboot. So I simply map them then dont restart, lol. Yeah, same issue here, it won't remember them forever, just for that session.
Thursday, January 22, AM. Friday, January 23, PM. Is this a bug then? Does anyone know any other work-arounds? Tuesday, January 27, PM. Wednesday, January 28, PM.
0コメント