Adding to per server concurrant connections 2

[Samantha]

I have a problem with adding per server concurrant connections in License Manager using per server licensisng mode.

This is in a school. They purchased a licence for 15 users, but when Server was installed, only 10 workstations were present and so only 10 connections were specified in setup. They now have extra machines, but when I add to the number of connections in License Manager, only 10 computers are still able to connect.

Any help would be much appreciated

 

[syndicate47]

Have you tried a re-boot?

I am not too sure if you need to, but its worth a try.

 

[Samantha]

Yes

 

[mikes999]

What is the error mesaage? I've yet to see an NT server that refused connection due to a license violation; it emerely notifies you that number of valid licenses is exceeded.

It might have nothing to do with licensing.

Did you join the new PCs to the domain?

 

[Samantha]

The PC's are in a workgroup, but I didn't set any of it up. It was done before I was around. The message in event viewer says something along the lines of 'No license was available for product SMBServer 4.0'. These computers can interact on the network in every other way. eg. Print, log on, Internet etc, but not access the server.

If I disconnect from the server from one of the working PC's, I am then able to connect from one of the others.

The error message on the PC says 'The network resource unavailable' and 'Extended error'

Help

 

[stillsmiling]

I have the same problem, we originally set up the system for 10 users, we now have more people so we purchased another 10 licenses. We installed them on the server and we can still only connect 10 users.

HELP

 

[Zelandakh]

Assuming you really are legal and can prove it with pieces of paper, just stop the licence logging service.

It is a workaround rather than a cure!

There are actually 2 places you need to add the licences as I recall and you don't need a reboot. Been a while since I played with that, but if you don't want to stop the service, I'll have a play for you.

 

[stillsmiling]

Thanks

Turning the licence server manager off means that I can at least keep going!

You mentioned 2 places to enter the licence, what do you mean? I know that there are two types of licence (per seat and per server) but they both go in the same place.

I have been told that the cause of the problem is that we originally set up as per server. We now have two servers and so the server with problems is unhappy because the per client model is more appropriate. Is this likely? I thought that either could be used.

 

[kjonnnnn]

Did you do per seat or pe server?

 

[stillsmiling]

We are running per server. Although, we have no strong prefrence for either model.

 

[Zelandakh]

I use per seat as it is more economic when running more than one server.

Go to Admin Tools and use licence manager to add in the new licences you have bought. You also need to do a similar thing in control panels licensing.

 

[NetTech24]

Are you running Exchange Server or other product that requires licenses on this same machine?

 

[Zelandakh]

Exchange can be done the same way - don't stop the licence service on a SQL server though!

 

[stillsmiling]

Thanks again for your help Zelandakh. I think that this has isolated the problem.

The contol panel/ licensing comes up with the message "not available in the not for resale version". But only on the server that we are having problems with - the other server is fine.

 

[ShaithisDanoveur]

You're seeing that because you're on a user-limited NFR copy meant for dealers to deploy as a demo. It wasn't intended for use as a live server

 

[mikes999]

That explains it

 

[stillsmiling]

I am still smiling ... just :-|