Windows 2008 shares not accessible

I have been able to access these shares for a long time with no problems. Recently however it stopped responding. I first noticed when my mapped drive to it stopped connecting and wouldn't reconnect.

I am on a domain. I can ping and perform an nslookup on it without any problems. I can RDP to it. It is running a FileZilla Server and that works perfectly. However even creating new Network shares I am unable to access it.

From the server itself i can see all my shares running the previous commands. But from machines on my domain I can't. I did that a week ago. It was actually one of the first things I had done. I removed the shares then the File Server Role and rebooted. I then Re-installed the File Server Role and re added the shares. No difference. Activated and working fine. I can see and access it perfectly. Thank you all for you suggestions. Sometimes I wish I had everyone on spice works inside a giant building and we can all gather around broken equipment and just gang fix it lol.

I agree with everything Jeff said especially looking at the logs on both the server and your machine at about the time the problem started. Are others having the same issue or just you?

I agree to make sure that it is across the board for everyone on the network. If others are unable to access the file shares, it could be a variety of things wrong. Assuming that it is across the board, you can try a couple of things as follows. Here is my troubleshooting steps:. If you do not already have it setup, I recommend setting the Share security to Everyone Read and propagate it from the parent folder down through the sub-folders.

After that is completed, you control the security to these locations using NTFS as it provides you more flexibility on the permissions. As much as I want to trouble shoot this device I am not going. I truly thank you all for you prompt support suggestions on this. Normally I would have reported my findings as I love beating a challenge however this isn't a high use for Real Production level machine.

For now rebooting is my only fix. Fortunately, I haven't run into this in a couple weeks. We've seen the same symptoms with Server network shares running on boxes with older revisions of Symantec anti-virus products.

So, for troubleshooting purposes, mostly in an environment that has mixes operating systems, you might want to consider disabling SMB 2. You need to do so on both the "client" and the "server" operating systems. To disable SMB 2. To enable back SMB 2. Sign up to join this community. The best answers are voted up and rise to the top.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 12 years, 2 months ago. Active 10 years, 9 months ago. Viewed 7k times. I set up a share in Windows Server , giving full rights to my domain account. A reboot fixed the problem for WinXP, but I'd really like to avoid this if possible. Improve this question. Can you help us improve?

Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? Submit feedback. Thank you for your feedback!