Hi, This worked for me First, you need have a "Shared Folder" on your hard drive. If you haven't got one already, create a new folder on your hard drive called "Shared", then right-click it and select properties. Click the Sharing tab and tick the "Share this folder" box. Notice the little down-arrow next to the drive letter shown. Click the arrow to get a list of letters. Select the one you want to delete, then browse for your Shared folder and select it. By this means, you will assign the drive letter to a real folder.
Make sure the "reconnect at login" box is un-ticked. Click the Finish button to get a warning. Answer YES and the Shared folder will open. Close it. Schorr -bschorr. It disconnects on both computers? Is there a power-saving option on the LaCie that might be kicking in and putting it to sleep?
How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Jamie Bilinski. Are there any indications of problems? Have you tried moving the affected server s to a different port on the switch, if this is a possibility? I've got a few feelings on this. Typically, I like to find out WHY something is happening before resorting to a workaround. BUT in this situation, after seeing a server, I got turned off : Upgrade that domain to a new functional level then troubleshoot if problems persist.
Domain or work group? What permission level does user have in servers and client? Is client using a local account? I know on our Win7 computers, we get a red X over the mapped drive if we have been idle for some time, simply clicking on it reconnects immediately. I figured this was a feature of Win7.
Because each user have access to different folder. The users have user level access in windows xp computers and i've made them administrator on the windows 7 machines. When the drives are mapped manually, you checked the box that says automatically reconnect upon disconnect. There are issues with server and SMB3. FRS will keep retrying. Following are some of the reasons you would see this warning. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
I can restart my machine and the drives will be connected and working as they should. But after some time they will disconnect again. Win 7 is acting like it is losing the connection to the network, because I can't map another drive from one of the other PC's unless I reboot. But the internet access is still working fine. Any ideas? Moved by Chris. Friday, January 29, PM. This behavior is caused by the default policy setting in the Windows Server.
After doing these, the mapped drives should not disconnect. If your system is Windows 7 Home Premium, you may change it from Registry. Marked as answer by infinite15 Wednesday, February 10, PM.
Monday, February 8, AM. Do you know if this is an issue with server R2? We will be moving over in a month or two and just wondering if I should expect similar issues. It worked great. As soon as I changed the autodisconnect time it recognized the drives immediately and is working great. Wednesday, February 10, PM. Firewalls are off on both ends. Wednesday, May 5, PM. I am having same trouble with only windows 7 professional workstations.
They are having the mapped drives shade out and the only thing that gets them reconnected is restarted the computer. We even have the policy client side extensions GPO in place on a DC for mapped drives instead of using login scripts. We do have some DCs active, however the file shares reside on a file server where the mappings occur.
Anyone come up with a solution to this one? Friday, May 21, PM. Monday, June 14, PM. No luck - still losing access to local shares. Tuesday, June 15, PM. Problem: Drive mappings on the Win 7 machine are lost at every reboot. Fix: I added a password to the Win 7 machine, and the drive mappings are retained. Wednesday, June 23, PM. To All, Here is what I have found. Wednesday, July 7, AM. Thanks in advance, Bashy.
0コメント