Windows SBS 2003 - SMB Shares not working after AD corruption

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
DataplanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

oBdACommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DataplanAuthor Commented:
I actually did fear that it was the only solution.

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

Thanks anyway!
0
DataplanAuthor Commented:
(see answer in thread)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.