Server 2003 standard edition - lockout from all network file share

Hi

We cananot get any access via the share name on a windows 2003 server
standard edition. On the server we can get access to the folder through
explorer but not throgh the share - all permissions have been checked and
re-checed. There is no firewall running. It coudl be malware but have checked
for it and found a possible rouge svchost which has been removed.

Does any one know what registry entries may controll the access to shares.

The error message when accessing shares from the server is -
\\servername\sharename is not accessible. You might not have permissions
......

This happens immediately when creating new shares from the root of C as well.

It also means that group policy can't be applied at startup - as even the
SYSVOL share is locked out at startup.

The only other problem we have found is the the workstation service only
loads at boot - if you try and restart it doesn't load and you get error 1068
The dependancy service or group failed to start. In the System event log you
get could not load rdbss driver, similar for RDR driver. We have tried sfc
/scannow but no joy. This may be happening because of the share issue of
course - I don't know.

I have googled and tried everything I can find including msconfig etc. but
information on what registry entries may we worth looking at is hard to find
- so any thoughs or suggestions please.

It could be an SMB signing incompatibility or that the two don't have a
common authentication protocol configured.
See:
http://msmvps.com/blogs/kwsupport/ar.../02/40653.aspx
and
http://support.microsoft.com/kb/175641

"tongers" <(E-Mail Removed)> wrote in message
news:ABFEDFBF-DB4F-490E-9502-(E-Mail Removed)...
> Hi
>
> We cananot get any access via the share name on a windows 2003 server
> standard edition. On the server we can get access to the folder through
> explorer but not throgh the share - all permissions have been checked and
> re-checed. There is no firewall running. It coudl be malware but have
> checked
> for it and found a possible rouge svchost which has been removed.
>
> Does any one know what registry entries may controll the access to shares.
>
> The error message when accessing shares from the server is -
> \\servername\sharename is not accessible. You might not have permissions
> .....
>
> This happens immediately when creating new shares from the root of C as
> well.
>
> It also means that group policy can't be applied at startup - as even the
> SYSVOL share is locked out at startup.
>
> The only other problem we have found is the the workstation service only
> loads at boot - if you try and restart it doesn't load and you get error
> 1068
> The dependancy service or group failed to start. In the System event log
> you
> get could not load rdbss driver, similar for RDR driver. We have tried sfc
> /scannow but no joy. This may be happening because of the share issue of
> course - I don't know.
>
> I have googled and tried everything I can find including msconfig etc. but
> information on what registry entries may we worth looking at is hard to
> find
> - so any thoughs or suggestions please.
>
>

Hi

I think it is mor fundemental than that - even when I boot the DC in safe
mode with networking and tryn map the share say with net use K: \\IP
NUo.\sharename it can't access sharename.

I have use examinde the sahre using sharenum.exe from sysinternals and it
looks OK - although it does say I'm not a domain administrator - which I am
according to the administrator security settings - perhaps this is where the
problem lays - is there any way of resetting the defaults to all the built in
accounts and security groups.

Any advice appreciated - thanks

"Jeremy" wrote:

> It could be an SMB signing incompatibility or that the two don't have a
> common authentication protocol configured.
> See:
> http://msmvps.com/blogs/kwsupport/ar.../02/40653.aspx
> and
> http://support.microsoft.com/kb/175641
>
> "tongers" <(E-Mail Removed)> wrote in message
> news:ABFEDFBF-DB4F-490E-9502-(E-Mail Removed)...
> > Hi
> >
> > We cananot get any access via the share name on a windows 2003 server
> > standard edition. On the server we can get access to the folder through
> > explorer but not throgh the share - all permissions have been checked and
> > re-checed. There is no firewall running. It coudl be malware but have
> > checked
> > for it and found a possible rouge svchost which has been removed.
> >
> > Does any one know what registry entries may controll the access to shares.
> >
> > The error message when accessing shares from the server is -
> > \\servername\sharename is not accessible. You might not have permissions
> > .....
> >
> > This happens immediately when creating new shares from the root of C as
> > well.
> >
> > It also means that group policy can't be applied at startup - as even the
> > SYSVOL share is locked out at startup.
> >
> > The only other problem we have found is the the workstation service only
> > loads at boot - if you try and restart it doesn't load and you get error
> > 1068
> > The dependancy service or group failed to start. In the System event log
> > you
> > get could not load rdbss driver, similar for RDR driver. We have tried sfc
> > /scannow but no joy. This may be happening because of the share issue of
> > course - I don't know.
> >
> > I have googled and tried everything I can find including msconfig etc. but
> > information on what registry entries may we worth looking at is hard to
> > find
> > - so any thoughs or suggestions please.
> >
> >
>