Jump to content

Can't access a network share, regardless of user - used to be able to. Very weird one

Koocha

By Koocha
in Windows 7

 Share

Recommended Posts

Koocha

Koocha

Posted
Posted (edited)

Hi everyone

 

I'm tearing my hair out here with a problem we've been suffering.

 

We've recently got a new suite of 30 laptops. I've installed and configured Windows 7 Pro on them all using WDS.

 

Everything was fine for a few days...

 

Then users started getting errors when logging on because they couldn't access the shared desktop. (\\servername\share$).

 

All share permissions and things are fine. Here's the 2 things that make this error really strange:

 

1. The user can access the share via IP\sharename. I don't think it's a DNS issue because some of the other shares are available via servername\share. This doesn't last though - soon enough it tells the user they can't access the share from either servername or IP.

2. Trying to access the same share via \\servername\share$ doesn't work for admins either. Same error message about having access denied.

 

This isn't on all of the computers - just a few. But it affects ALL users, regardless of their permission level.

 

We've tried everything to sort it, but it appears to be something on the client machine. Because of this, I made a fresh install of Windows, joined it to the domain, installed packages and it was fine. I reluctantly reimaged all 30 laptops. Sure enough, 3 days later we're having the same issues. Also on our 30 netbooks, made with a separate image. Something isn't right here - it's like something is telling the computers not to work anymore.

 

Does anyone have any ideas how this can be sorted? I've tried all sorts of things I've found in forums - nothing works apart from a reimage of the computer, then that only works for a few days.

 

Thanks in advance

Edited by Koocha
typo
detjo

detjo

Posted
Posted

Is it possible the permissions haven't been applied correctly?

Recreate the share and double check share permissions and security permissions. I know you say they are fine ... but 'something' is stopping it working.

Koocha

Koocha

Posted
  • Author
Posted

Hi

 

Yeah, they're appearing in AD correctly. Doesn't matter whether it's wired or wireless - doesn't work. It's the shares for their documents, desktop and start menu that don't work. The one that does is the shared area.

 

Tim

Koocha

Koocha

Posted
  • Author
Posted
Is it possible the permissions haven't been applied correctly?

Recreate the share and double check share permissions and security permissions. I know you say they are fine ... but 'something' is stopping it working.

 

If I add a share to same folder (same name but with a 2 on the end) with the same permissions it works correctly. Can't say for how long though.

Garacesh

Garacesh

Posted
Posted (edited)

Check credential cacheing. Is it possible they're not actually logged on successfully?

Scratch that. The previous posts wouldn't work if this were the case.

That'll teach me to try and help without reading the other replies. D'oh!

Edited by Garacesh
Koocha

Koocha

Posted
  • Author
Posted
Check credential cacheing. Is it possible they're not actually logged on successfully?

Scratch that. The previous posts wouldn't work if this were the case.

That'll teach me to try and help without reading the other replies. D'oh!

 

Thanks for trying to help though!

Koocha

Koocha

Posted
  • Author
Posted (edited)
Your new 30 laptops haven't pushed you outside of your DHCP scope, have they?

Could the WAP they're using be damaged/faulty/be connected to a bad wire?

 

Checked the scope, They're sitting nicely in our DHCP address range.

 

We've got a Ubiquity Unifi system. 24 WAPs. Happens all over school. Also when wired.

Edited by Koocha
hallb15

hallb15

Posted
Posted

Is the share that does work on the same server as the shares that don't?

 

Do you have more than one GPO that controls the shares that don't work? Its possible you have a GPO conflict. Try running the Group Policy Modelling Wizard.

 

And here's a seemingly random one but if you've tried everything else then its worth a look: Is the time slipping on the laptops to a point where it is outside the tollerance of the server the share is on?

Koocha

Koocha

Posted
  • Author
Posted
Is the share that does work on the same server as the shares that don't?

 

Do you have more than one GPO that controls the shares that don't work? Its possible you have a GPO conflict. Try running the Group Policy Modelling Wizard.

 

And here's a seemingly random one but if you've tried everything else then its worth a look: Is the time slipping on the laptops to a point where it is outside the tollerance of the server the share is on?

 

We've just got the one server, so all the shares are on that.

 

The shares that don't work are the ones in the profile (documents, start menu and desktop). The share to the shared area is mapped as a drive via GPO and works correctly. All the profiles have been binned and recreated. The documents are also mapped to a drive, but they don't work.

 

The time is spot on with the server.

stm-tech

stm-tech

Posted
Posted

Where is the share? is it a Windows share or a Linux Nas box?

 

Have you enabled NLA?

 

If it is a Linux Box, try setting the following Reg key: HKLM/SYSTEM/CURRENTCONTROLSET/CONTROL/LSA/LMCompatibilityLevel REG_DWORD = 2

  • Thanks 1
Koocha

Koocha

Posted
  • Author
Posted
Check date, time and also time zones on both server and a few laptops ?

 

Also have you got another server you could set some shares on and see if you still get the same issue?

 

Yup, got another server. It's an old one running 2003 which is currently just a print server. I can access shares from that fine.

 

Timezones and time are the same on the server and laptop.

mac_shinobi

mac_shinobi

Posted
Posted
Yup, got another server. It's an old one running 2003 which is currently just a print server. I can access shares from that fine.

 

Timezones and time are the same on the server and laptop.

 

Wondering is there any point in updating the NIC driver on the server at some point and ensuring its got any power management options disabled. Then do the same on a few clients and try the clients on a physical connection for the time being

Koocha

Koocha

Posted
  • Author
Posted (edited)
What was it doing or what was happening ? Also I think its a registry edit to disable it

 

It was enabled. We disabled it and it started working ad expected.

 

We've stopped the service via GPO but need to disable it as stopping the service alone didn't do it

 

Edit: OK, may have spoken too soon

Edited by Koocha

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...