General discussion


SMB Problem in Windows NT 4.0 Server DCs

By Mehul Bhai ·
We are facing problem as explained/described in the discussion at the URL given below:

Does any one or microsoft have solution to the same.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to SMB Problem in Windows NT ...

To resolve this problem:

1. Check the number of installed licenses:

Start / Manage Server / About Microsoft BackOffice Small Business Server

2. Use Regedt32 to navigate to:


Edit or Add Value name ConcurrentLimit, a type REG_DWORD entry, and set the data value to the number of licenses from step 1, using the Decimal Radix.

3. Use Control Panel / Services to Stop and Start the License Logging Service.

Collapse -

by Mehul Bhai In reply to

Poster rated this answer

The settings in the registry are as you mentioned. It has to be because if that were not the case the server would not have worked fine till now. Why should the problem come now and not previously???????? Why should the problem start on 9th February 2005, which was when the newly released latest microsoft patches were applied (specifically the MS05-011) to all the Windows 2000 Servers & Professional and Windows XP Profesional client Machines which are members of the domain.
Any Answers anybody???
This type of problem is reported by many.
Microsoft are you listening/watching????

Collapse -

by BFilmFan In reply to SMB Problem in Windows NT ...

I didn't think my technical suggestion was going to resolve the issue. I did want to confirm that Microsoft's fix didn't change those registry settings.

Based on the information in the article, Microsoft is clearly stating that issues with out of life-cycle products is not their problem and you must upgrade as seen in this part of the article:

"Customers who require additional support for Windows NT 4.0 SP6a must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office."

Frankly, I think your only choice for resolution is to either:

Upgrade your servers to the latest Microsoft supported products.

Migrate from Microsoft OS to something else.

Roll-back that security update.

If any of the peers can recommend some other course of action, I'd like to be made aware of it for general knowledge purposes.

I am sure that my answer above isn't what you would like to tell your users and management, but the real truth is that no manufacturer of anything keeps making and supporting a product for 11 years. They are always rolling out a new and improved version be it cars, laundry detergent or toilet paper.

My advice, roll back the security update and then plan an upgrade or migration, whichever meets your needs best. Otherwise, you are going to face this issue over and over.

Collapse -

by BFilmFan In reply to

Just a secondary thought, that was the best rejection comment I've seen in ages. Be nice to see your technical and discussion commentary more!

Collapse -

by Mehul Bhai In reply to

Poster rated this answer.

You are right about the support but you dont leave holes (Security Holes) in your product & stop support.
Anybody else is having suggestions or work arround for this problem.

P.S.: Sorry I cannot submit comments without rejecting your answer.

Collapse -

by Mehul Bhai In reply to SMB Problem in Windows NT ...

This question was closed by the author

Related Discussions

Related Forums