• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 292
  • Last Modified:

What are the Capacity Restrictions of Windows Server 2003 Web Edition?

Hi,

Apart from the application restrictions, such as not being able to run SQL server, are there any restrictions in the Web Edition that will restrict the web serving capacity of the server?

I have seen that "Web Edition is limited to 10 in-bound server message block (SMB) connections for content publishing." however I do not understand what that means in real terms.

I will be running ASP pages against an MS Access database through ODBC (this may be updated to MSDE). The web users will be "signing in" and being controlled using ASP session states. Will there be any capacity restrictions such as the maximum number of users signed on at any one time or the number of hits being served (hardware capacity etc. being up to the task)?

Thanks
0
IanBryer
Asked:
IanBryer
  • 2
1 Solution
 
Chris DentPowerShell DeveloperCommented:
Hi,

The limitation in question is to stop people using Web Edition as a cheap File Server. In-bound SMB connections refers to accessing the server via its UNC, like \\server\share, this includes access through mapped drives.

The other limitations are 2Gb or RAM maximum and 2 Physical CPUs maximum.

This MS page has a few more details, although the 10 user limit isn't mentioned.

http://www.microsoft.com/windowsserver2003/evaluation/overview/web.mspx

HTH

Chris
0
 
IanBryerAuthor Commented:
Thanks Chris

I appreciate that the SMB connections are to stop people from obtaining a cheap file server but the web page you directed me to states;

"10 in-bound server message block (SMB) connections for content publishing"

which implies that this is also a restriction that will impact the web serving capabilities. My question is really to do with what does this restriction impose on the web access not file/print sharing capabilities.

Regards

Ian
0
 
Chris DentPowerShell DeveloperCommented:

Hi Ian,

It doesn't impose any restrictions on web access. SMB is not HTTP / HTTPS / FTP.

Content Publishing, in the context of the statement above, refers to uploading new files to the website via a network share which uses the SMB protocol - via File and Printer Sharing.

There's a short description of SMB here:

http://www.webopedia.com/TERM/S/SMB.html

Chris
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now