Windows Forum

Ask something
Discussion Locked

licensing fubar

0 helpful
6 replies

by freetech

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

i have 7-10 machines (depending on how may i have hooked up) on a win2k server network. the machines are win2k, win98se and winxp pro. there are 20 cals purchased as per-server. however, the server stops accepting connections at 6. after that, i get a "no more connections can be made..."
i have played with the licensing MMC till i've run out of possibilities. this one has me stumped. any suggestions would be appreciated.
thanks,
freetech

6 replies

by cg it

how many servers on the network that clients have to access? clients can access 1 server per license in server mode. clients can access multiple servers with 1 license in seat mode. you should be able to connect 20 workstations to 1 server in server mode with 20 cals, unless the CALS didn't load right.

by freetech

Poster rated this answer.
thankyou for trying to help. as i said, i have been through the "easy" fixes and it should have worked, but did not. i'll probably end up re-loading the server os. if that doesn't cut it , i'll be back with a new post. take the points as my way of saying thanks.

by freetech

i have one server operating win2k server as wins, dns, dhcp, file and print server. the licensing may not be correctly entered but is listed in the licensing mmc as per-server

by cg it

heres some more on licensing. The licensing tool in the control panel will allow you to add/remove client access licenses for the local server in server mode. The licensing manager utility allows you to do just about anything enterprise wise with CALS except changing from per seat to per server. One opens up the licensing tool from the control panel and the licensing manager is opened via administrative tools , licensing. Try opening up the licensing manager from admin tools and verify that the CALS are listed.

That's about all I can suggest. Joe Moore might have further info for you and I suggest you contact him on more detailed trouble shooting.

This discussion is closed to new replies.