I have an SBS 2008 machine which is causing me headaches.
For Windows shares, it seems to be living in its own little isolated world. It can browse a list of network shares just fine (NET VIEW
), but it refuses to connect to any, with:
\\storage\shared 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.
The specified network name is no longer available.
And the same goes for every other computer on the network. They can view the shares on the SBS 2008 server, but they cannot connect to any. they get the same message.
I don't know how long this has been going on for, and it may have been going on since the server was first deployed.
Additional information:
There is a concerning part of DCDIAG
which I've outputted below (we only have one DC in one site, so I'm not sure if NTDS issues would be affecting this problem):
Starting test: Services
Could not open NTDS Service on EPPINGDC, error 0x5 "Win32 Error 5"
......................... EPPINGDC failed test Services
Starting test: SystemLog
An Error Event occurred. EventID: 0x00000457
Time Generated: 08/22/2010 07:40:19
EvtFormatMessage failed, error 15100 Win32 Error 15100.
(Event String (event log = System) could not be retrieved, error
0x3afc)
An Error Event occurred. EventID: 0x00000457
Time Generated: 08/22/2010 07:40:27
EvtFormatMessage failed, error 15100 Win32 Error 15100.
(Event String (event log = System) could not be retrieved, error
0x3afc)
......................... EPPINGDC failed test SystemLog
Any suggestions?
I just had another thought. I've seen a server in the past where the IPC$ share somehow disappeared. Check your shares to make sure it's still there. If it isn't, run net use IPC$
Also let us know how the BPA changes worked out for you.
EDIT
All right. I have another suggestion. Reset winsock and TCP/IP. You'll probably want to be onsite for this. You have to reset the IP address afterwards (A good idea is to rerun the "Connect to internet" wizard when you're done). Here's the commands:
netsh winsock reset c:\winsockreset.log
netsh int ip reset c:\ipreset.log
I'll offer two possibilities that may or may not be helpful:
When you say that there is only one domain controller, I take it that this SBS machine is the only domain controller? This may be familiar territory for you, but I want to be sure because so many people aren't fully aware of the enforced limitations of SBS.
Is there any possibility that this machine's clock is out of sync with the rest of your LAN?
Unfortuantely after following everyones advice here, the issues came back after about a week. We just lived with it whilst preparing to rebuild the server.
Whilst we were preparing for the rebuild, the PSU in the server died. I took the oppertunity to upgrade it to a 1kw PSU and low and behold, all the problems went away!
I suspect that a recent upgrade from 4 to 16Gb of RAM drew too much power and didn't leave enough for the system to function correctly.
Some random suggestions:
In registry check:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
(DWORD) LMcompatibility to be 1 (reboot upon modification).
---Update1:
Can it these links be helpful?
This can be caused by incorret nework / dns entries.
Please try this:
ipconfig /registerdns
net stop netlogon
If you have dhcp server - please delete all leases pointing to your server. Check if all DNS A records for your server are pointing to it's current ip.
net start netlogon
User contributions licensed under CC BY-SA 3.0