I have 2 PCs in a workgroup. I have moved the My Documents folder to a NAS device (separate disk drive). These PCs are always connected to the network. There are multiple user accounts on each PC (they are the same accounts on both PCs).When I look at my "My Documents" folder via Libraries -> Documents -> My DocumentsI see the sub folders each with a gray x. If I try to select one of these folders, I get the following error message:\\NASDevice\Data\Bob\Folder is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. This file is currently not available for use on this computer.I have these same folders mapped with a drive letter (ie: N:\ = \\NASDevice\Data) and the path would be N:\My Documents (where Bob = My Documents in the path shown above). I have full access to all of the sub folders under "My Documents". These folders are the same folders on the same device except some times I do not have access to the folders when using the Libraries route. Occassionally, other users are on a VPN so I have mapped my N:\ drive with an IP address for the \\NASDevice above. Any ideas why I get gray x when accessed one way and full access the other way?

This issue can be caused by the incompatible Kerberos encryption types. How does it work if you do the same tasks on a Windows Server 2003 computer or Windows XP computer? How does it work if you redirect the My Documents folder to the network location on the other computer? Currently most of NAS us Kerberos authentication. The Kerberos is changed in Windows 7. Now it will not have problems when communicate with older versions of Windows systems, but there can be issues when access a network device if the Kerberos encryption level is incorrect. I suggest that you make the following changes on the Windows 7 computer: 1. Open gpedit.msc. 2. Find the policy Windows Settings -> Security Settings -> Local Policies -> Security Options ->Network Security: Configure encryption types allowed for Kerberos 3. Configure the policy. If it is not configured, actually both DES cipher suites are disabled. I suggest that you enable all the suits. Then please check the result. If the issue persists, please let us know the model of the NAS. Additionally, please capture network trace data and send to me. 1) Download NetMon3.3 from the following website and install it on the computer NetMon3.32) Launch NetMon3.3.3) In the Microsoft Network Monitor 3.3 window, click Create a new capture tab 4) In the new tab, select all the Network Adapters in the Select Networks window.5) Go to sync time page. Then, switch to Network Monitor, press F5 to start NetMon.6) Try to sync time.7) Go back to the NetMon window and press F7 to stop the NetMon.8) Press Ctrl+S to save the Netmon file named test. Please upload the file to the following path. Microsoft Service File TransferPassword: W_yMk{IZrXhFArthur Xie - MSFT

I sent you the test.cap file as well as test1.jpg, test2.jpg, test3.jpg. Test1.jpg shows the N: drive mapped to the same filer as the NAS device below it (under network). Note that it shows different folders. I believe what is happening is that for some reason when it connects with the mapped drive and then tries to connect with the Network, the network path does not connect and reverts to some drives probably on the c: drive. These are basically the drives that contain all of the user's documents.Test2.jpg and Test3.jpg show you what the folders look like in both methods. Test3.jpg shows the gray x. I think this looks like folders that are "Off line" and not synchronized. I don't believe that sync partnerships are set up on this PC. I'm not sure why it can't connect. Some times it can connect using the network path and later it appears unavailable.Thoughts?

By the way, I only have PCs with Windows7 on this network. It has worked for years when the same PCs were Windows XP and Windows Vista. One of the PCs is x64 and the other is x86. The x86 is the one having the problem. I have not seen this issue on thex64 pc. Could it be that somehow these directories were indexed on the x86 and now I have this turned off (and the index stored a local version of the files)?

Hi, I have received the attachments. However, from the NM report I cannot find the authentication process so I cannot find if the issue is caused by authentication. Please launch Network Monitor and start tracing, then open the NAS from Windows Explorer and access the folders, after error message is received please stop tracing and export the log. Did you change the Kerberos encryption type? If it does not help, try to change default NTLM authentication level. Please refer the following article. Network security: LAN Manager authentication level Please change the level to Send LM & NTLM - use NTLMv2 session security if negotiated.Arthur Xie - MSFT

I have uploaded two files (TestDidNotWork.cap, TestWorks.cap). These should be a network trace of both cases where using going through the network to get to my folders on the NAS device worked and did not work. I used the same process in both cases except I rebooted to get it to work. I did change the Kerberos encryption types andenabled all of the options available.I already had this setto Send LM & NTLM - use NTLMv2 session security if negotiated. This change was implemented when I used Vista as a client. Never had an issue like this.I did upgrade both Vista machines to Windows 7 (not a clean installation). This issue only happens on the 32 bit Windows 7 PC. I think this may have to do with this PC not seeing the NAS device on the network and then it reverts to an off-line scenario somehow. Perhaps these files were indexed when it was a Vista machine. I've tried not to use off-line files since these are PCs that are always connected to the network. My router died a few days ago. I replaced it with a new one but this problem remains. Perhaps the PC can't communicate with the DNS on the router but can find the device via IP address?

Did you get a chance to review the files?

Added the files per your request, haven't heard anything back. I would say the following seems to be true for this issue:EitherThere is a specific timeout set somewhere and then the PC switches over to off-line (gray folder) modeorThere is a lot of network traffic from other PCs and the PC switches over to off-line (gray folder) mode.Since these PCs are always connected to the network, is there a setting to keep the PC "on-line" or is there a timeout value that I can set to make it try longer before switching to off-line mode?Once upon a time, this PC must have gone into off-line mode. Is there a way to delete the cache, etc. and set it to on the network all of the time?

I can replicate this issue by downloading large files (basically making the network busy) from the other PC on the network. I guess this makes a slow connection on the PC with the gray x issue. So basically a slow connection causes the PC to go intooff-line mode where things are not synchronized. Again, off-line mode is off as these PCs are always connected.Is there some way to delete the off-line cache if itexists and set this to always on-line? Is there some wayto define a slow connection?

I have the same problem. W7-laptop connected via a slow connection over PPTP-VPN directly to a Win2003-server. Same setup worked fine when the laptop had XP and connected using a native NetGear VPN client to the company's firewall instead. Any updates? __ PC-Bjrn