Solved

Windows SBS 2003 - SMB Shares not working after AD corruption

Posted on 2008-10-31
3
408 Views
Last Modified: 2013-12-24
Hello,

Yesterday one of our SBS 2003 Domain controllers broke down. No valid backup was available, the database was broken beyond repair, and being SBS it was ofcourse the only controller in the domain. I can't reinstall, as my only install media is scratched.

So what we did was demote the server, and then create a new domain with the same name. That's when the real nightmare started.

Now I can't seem to be able to access network shares on the server in any way. (This ofcourse means i can't add computers to the domain either, as the sysvol/netlogon shares cant be accessed)

I get the famous network path not found while trying to browse \\servername from other computers.

I can browse \\servername from the server itself, but can't view any of the shares. (network location cannot be reached)

It seems that the server doesn't even respond on tcp ports 139 and 445. In my little head that means either i'm getting firewalled away or some critical service stopped working. (Please confirm?) I doubt firewalling is the case - it's disabled both on server and test clients.

It responds to port 445 locally, which might explain why i can see shares but not browse them while browsing from the server itself.

I did double check that both DNS and WINS is pointed to the server on clients.
I suspect that the wins service is broken on the server. The service starts without a problem, and reports nothing suspicious in logs, but i can't connect to it from the wins management console. I don't know wether or not it is related to my main problem though.

I also did check permissions - both on the shares and on filesystem. Permissions are correctly reset to to the groups of the new domain.

Does anyone have an idea on what to try?

Thank you for your time.

bjorn
0
Comment
Question by:Dataplan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 84

Accepted Solution

by:
oBdA earned 250 total points
ID: 22849090
You can basically forget that server; it has to be reinstalled from scratch, and all the clients joined to the new domain.
SBS is *very* particular when it comes to the default file and OU structure, and with the remnants of the old domain (and the permissions of the old domain) all over the place, you will not be able to recover that system manually (same name or not, what you have at the moment is a completely new domain).
You might be able to buy only the SBS media set from your dealer, or try to contact Microsoft directly.
0
 

Author Comment

by:Dataplan
ID: 22850355
I actually did fear that it was the only solution.

Reinstall w/2003 Std! *sigh* on a friday afternoon..Goodbye weekend...

Thanks anyway!
0
 

Author Closing Comment

by:Dataplan
ID: 31511976
(see answer in thread)
0

Featured Post

Major Incident Management Communications

Major incidents and IT service outages cost companies millions. Often the solution to minimizing damage is automated communication. Find out more in our Major Incident Management Communications infographic.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Active Directory security has been a hot topic of late, and for good reason. With 90% of the world’s organization using this system to manage access to all parts of their IT infrastructure, knowing how to protect against threats and keep vulnerabil…
Had a business requirement to store the mobile number in an environmental variable. This is just a quick article on how this was done.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question