• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Small Business Server and Licenses!!

B

Blammo300

Senior member
Could someone explain to me simply how Small Business Server 2000 works with licensing? The program comes with 5 licenses how does this relate to each client computer? Is 1 license worth 1 client computer?
 
If the OS license comes with 5 CALs (Client Access Licenses) it means literally that 5 clients can access it (5 users or computers) at any point in time. If you have more users or computers that will be accessing it you will need to buy more CALs.

Oh and BTW; get SBS 2003, it's well worth your while.

-Erik
 
So you install the Client Licenses on the server computer not the actual Client comp itself? And then it wouldnt matter which computers are used as long as not more then 5 are on right?

Also where can I purchase client license packs locally? I tried my frys electronics but they only carried small business server 2003 license packs.
 
Well you dont really "install" licenses per-se; you really just open up the licensing console and tell it how many you have. If you start using more connections than you have licenses it will log warnings in the event log so you know to go buy some more.

I dont even know where you are so it's kind of hard to know if you can pick them up locally. Wherever you are you're probably still better off ordering them online (froogle small business server cal).

-Erik
 
Thanks for the help. I checked my Event Log and the only thing that stood out was this warning,

"Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available. "

It appears quite often but nothing about Licenses. Ill post my problem and maybe you or someone else will have an idea of whats goin on.

At my work we have 2 offices, on 1 side we have all the main work computers with Windows XP and on the other side we have a computer with. Windows 2000 Advanced Server. Now we connect to the Advanced server using a Remote Desktop Connection so that we can access certain programs and information.

Everyone is able to connect to this server using the Remote desktop except for 2 computers. We have 5 Desktops and 1 Laptop connecting via the Remote Desktop using 2 linksys routers (1 is Wireless) and a switch, the laptops are using the wireless and can connect fine.

On the 2 Laptops that do not work it gives this error

?The Client could not establish a connection to the remote computer.

The most likely causes for this are:
1)Remote Connections might not be enabled at the Remote Computer.
2)The Maximum number of connections was exceeded at the remote computer.
3)A network error occured while establishing the connection.?

I have tried connecting them to the remote desktop using both wireless and direct Ethernet cord. I have been over all the settings and cannot figure out whats going on. I know the remote server is not out of available connections. It is very important that those 2 computers are able to access the remote server.
 
Terminal Server is an entirely differant beast when it comes to CALs; for them you need TSCALS, I think they come with the windows OSes but I'm not really sure. Someone else may want to comment on that. However you're on the right track by simply following the directions you posted.

1) You can rule this out because you are able to connect with other machines.
2) Just to ensure this is the case try logging off with one of the machines that have a current connection and than try logging on with one of these laptops. If you are able to connect than you will know it is a conntection limit you're hitting. If you still cannot connect from these machines than:
3) A network error occured while establishing the connection. - Perform standard network troubleshooting, can you ping, etc. If you can than try telnetting on the terminal services port (3389) and see if you can telnet to it.

So I take it your problem has nothing to do with SBS like your title and origonal post indicated?
 
Thanks again for the help, I am not sure if it is the laptop causing the problem or SBS but I was leaning towards SBS but now im not sure.
 
Nick, what about windows clients? I dont run an application TS so I havent looked too deeply into the licensing but I was under the impression that 2k and xp pro client oses were allowed to connect and that you only needed additional TS CALs for legacy and embeded clients.
 
Originally posted by: spyordie007
Nick, what about windows clients? I dont run an application TS so I havent looked too deeply into the licensing but I was under the impression that 2k and xp pro client oses were allowed to connect and that you only needed additional TS CALs for legacy and embeded clients.
Click to expand...

Does that mean it would be diffrent of Windows XP Home Edition?
 
That licensing changed with the release of Server 2003. Windows 2000 Server family allowed 2000 Professional or XP professional clients to connect without requiring they have a TS CAL. They still needed their normal Windows CAL, but they didn't need the TS CAL.

With the release of Server 2003, that was removed, and ALL clients require both the Windows CAL (same as before) and a TS CAL. The reason for the change was prior to Server 2003, there was no option for User CALs, so if you had a large group of TS-based workers, there was no easy way to license them if they connected from client locations, etc. With User CALs, that problem goes away.

Users with XP Professional client devices were grandfathered into the new licensing (in a way) by being granted TS CAL licenses for any client device they had prior to the release of Server 2003 (April of 2003 I believe the date was).

Windows XP Professional hosting a Remote Desktop session is a different beast, and requires no licenses because you can only have one active session at a time.

For Server 2003 hosting Remote Desktop sessions (equivalent to the old TS Admin mode), you can still have 2 admin connections without needing licenses. You don't need to even install TS in Server 2003 unless you plan to run in the old Application Mode (basically, hosting TS sessions).
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top