benjf

New Member
Joined
Sep 9, 2011
Messages
2
Hello, I'm troubleshooting a misreported read only error when operating on network shares. Here are the details:


  1. Windows Server 2003, fully up to date
  2. Windows 7 64 bit client, fully up to date
  3. File reports in use and can be opened read only. Almost immediately the file reports as available for use for read/write and allows the file to be opened in that mode.
  4. Clients are using a VPN to connect.
  5. All files on the network share report this status
  6. The files are not all open by other users, services, etc
  7. Error is unaffected by user account (the same user account succeeds on XP clients, and fails on Win 7 64 bit clients).
Here is what I have tried and what works/doesn't work.

  1. Windows XP clients never receive this problem.
  2. Windows 7 32 bit clients fail until brought up to date.
  3. Two different VPNs have been used: Hamachi and Microsoft's RRAS. It has no impact on success or failure.
Please let me know what info you need. Thanks in advance for your input and suggestions.
 


Solution
It seems like you're encountering an unusual issue with misreported read-only errors when working with network shares on Windows 7 64-bit clients in a setup involving Windows Server 2003. Here are some troubleshooting steps and suggestions to address this problem:

Possible Causes and Solutions:​

  1. Network Share Permissions:
    • Ensure that the network share permissions are correctly set for the Windows 7 64-bit clients. Check both share-level and NTFS permissions to ensure they align with the required access levels.
    []Client-Side Caching:
    • Check the client-side caching settings on the Windows 7 machines. Sometimes caching issues can lead to files being reported as read-only incorrectly. You can...
It seems like you're encountering an unusual issue with misreported read-only errors when working with network shares on Windows 7 64-bit clients in a setup involving Windows Server 2003. Here are some troubleshooting steps and suggestions to address this problem:

Possible Causes and Solutions:​

  1. Network Share Permissions:
    • Ensure that the network share permissions are correctly set for the Windows 7 64-bit clients. Check both share-level and NTFS permissions to ensure they align with the required access levels.
    []Client-Side Caching:
    • Check the client-side caching settings on the Windows 7 machines. Sometimes caching issues can lead to files being reported as read-only incorrectly. You can adjust the caching settings through Group Policy or directly on the client.
    [
    ]Network Latency and VPN Issues:
    • Network latency over the VPN connection can sometimes cause issues with file access. Ensure that the VPN connections are stable and not dropping packets. Test the network performance to identify any latency issues affecting file access.
    []Windows Update and Hotfixes:
    • Make sure that both the Windows 7 clients and Windows Server 2003 are fully updated with the latest service packs, updates, and hotfixes. Certain updates can resolve compatibility issues that might lead to misreported read-only statuses.
    [
    ]Network Troubleshooting:
    • Perform network troubleshooting on both ends to rule out any connectivity issues that might be impacting file access. Check for any firewall rules that could be interfering with the file access process.
  2. VPN Configuration:
    • Review the VPN configurations for both Hamachi and Microsoft's RRAS. Ensure that the VPN settings do not restrict file access in any way. Check VPN logs for any errors that might shed light on the issue.

      Additional Information Needed:​

      To further assist you in troubleshooting this issue effectively, it would be helpful to have more details on specific configurations, error messages (if any), and any recent changes made to the network or systems. Additionally, providing information on the VPN settings, network architecture, and any relevant event logs could aid in identifying the root cause of the problem. Feel free to share any additional information or updates on the troubleshooting steps you've tried, and we can work together to resolve this issue.
 


Solution
Back
Top