WINDOWS XP vs WINDOWS 2003 server
WINDOWS XP vs WINDOWS 2003 server
For a mailserver with hmailserver + squirrelmail + php + perl + web server (not IIS but Key Focus),
why I would have to choose xp rather than win 2k3 server?
(and viceversa..)
conzi
why I would have to choose xp rather than win 2k3 server?
(and viceversa..)
conzi
not only the OS is cheaper (XP instead of Win 2003 server) but tools for it too - things like Partition Magic, or backup utilities. They often charge way more for server versions.
I'd say the real question is: do you need Windows 2003 server instead of XP or Windows 2000 ?
I don't have any metrics to make a decision with though - I'm running Apache and hMailServer on an oldish machine with Win2k, but I'm only doing 4 or 5 emails a minute (receiving; not sending...
- Al Weiner -
I'd say the real question is: do you need Windows 2003 server instead of XP or Windows 2000 ?
I don't have any metrics to make a decision with though - I'm running Apache and hMailServer on an oldish machine with Win2k, but I'm only doing 4 or 5 emails a minute (receiving; not sending...

- Al Weiner -
I use 2k3 Web Edition rather than the Server Edition. Its a hell of a lot cheaper and if all you are doing is hosting websites then this will be a better choice over XP IMO. It's not that much more expensive than XP Pro.
If you still want to go with XP you would need to use Pro over Home as Home edition does not have any of the network security permissions you would need for running web services etc.
HTH.
-Jon.
If you still want to go with XP you would need to use Pro over Home as Home edition does not have any of the network security permissions you would need for running web services etc.
HTH.
-Jon.
If at first you don't succeed, bomb disposal probably isn't for you! ヅ
Since he is using a 3rd party web server the 10 connection issue for xp pro is of no consequence. Im not aware of xp home having a connection limit as it does not have a web server.
There are registry hacks to raise the 10 concurrent limit to 50.
Michael
There are registry hacks to raise the 10 concurrent limit to 50.
Michael
Missing Hmailserver ... Now running Debian servers
I'm using apache and have noticed the constraint in my application log (i'm using xp pro).
From my understanding, it's the number of tcp/ip connections regardless of what port they come in on?
A consideration for business users: I *think* that the patches available to get round this limit break the licence agreement you accepted with MS when you installed windows
From my understanding, it's the number of tcp/ip connections regardless of what port they come in on?
A consideration for business users: I *think* that the patches available to get round this limit break the licence agreement you accepted with MS when you installed windows
ric melia, you are right.
I read about the connection limit a couple of years ago. But after rereading this just now
http://support.microsoft.com/?scid=kb;en-us;314882
it seems that Mircosoft have changed what they consider 1 connection.
It says "All logical drive, logical printer, and transport level connections combined from a single computer are considered to be one session; therefore, these connections only count as one connection in the ten- connection limit. For example, if a user establishes two logical drive connections, two Windows sockets, and one logical printer connection to a Windows XP system, one session is established."
Before 1 computer could use more then 1 connection. So there might be a good reason to use 2003 rather then XP pro after all. Or use the mentioned hacks. So perhaps it should be called "Max number of Computers" not "connections".
Michael
Edit: I dont know how strict Martin is but for those interested in changing the max connections have a look here.
http://www.winxpcentral.com/windowsxp/xpsp2speed.php
It also seems the max connections is only for file & printer shares etc. So we are back to my original interpretation. If a program eg Hmailserver or a third party webserver is happy to accept more then 10 connections does the 10 connection limit for XP/2000 apply? I dont think so
I think Martin can answer this.
Michael
I read about the connection limit a couple of years ago. But after rereading this just now
http://support.microsoft.com/?scid=kb;en-us;314882
it seems that Mircosoft have changed what they consider 1 connection.
It says "All logical drive, logical printer, and transport level connections combined from a single computer are considered to be one session; therefore, these connections only count as one connection in the ten- connection limit. For example, if a user establishes two logical drive connections, two Windows sockets, and one logical printer connection to a Windows XP system, one session is established."
Before 1 computer could use more then 1 connection. So there might be a good reason to use 2003 rather then XP pro after all. Or use the mentioned hacks. So perhaps it should be called "Max number of Computers" not "connections".
Michael
Edit: I dont know how strict Martin is but for those interested in changing the max connections have a look here.
http://www.winxpcentral.com/windowsxp/xpsp2speed.php
It also seems the max connections is only for file & printer shares etc. So we are back to my original interpretation. If a program eg Hmailserver or a third party webserver is happy to accept more then 10 connections does the 10 connection limit for XP/2000 apply? I dont think so
I think Martin can answer this.
Michael
Missing Hmailserver ... Now running Debian servers
-
- Senior user
- Posts: 886
- Joined: 2005-11-28 11:43
Slug, I'm not sure what you want me to answer. As far as I can remember, the "technical speed limit" introduced in SP2 only applies to outgoing connections. Say that your computer tries to open 30 outgoing connections at one time. Windows will let 10 through immediately. Then the next second, it will let another 10 through, and then the next second another 10.
So with the above senario, would XP still be able to host Hmailsever with a few hundred users ? Just trying to answer the original posters question.martin wrote:Say that your computer tries to open 30 outgoing connections at one time. Windows will let 10 through immediately. Then the next second, it will let another 10 through, and then the next second another 10.
Michael
Missing Hmailserver ... Now running Debian servers
From what i have read, SP2 just added to the limits by limiting outbound as well as inbound:
"Similar to the inbound connection limit Microsoft imposed on Windows 2000 Professional and Windows XP (where these platforms are limited to 10 simultaneous inbound connections), Windows XP SP2 now limits outbound connection attempts to no more than 10 at one time."
http://forum.shavlik.com/viewtopic.php?t=1291 (topic of the thread is about a network scanner that won't work anymore but i think it's relevant)
"Similar to the inbound connection limit Microsoft imposed on Windows 2000 Professional and Windows XP (where these platforms are limited to 10 simultaneous inbound connections), Windows XP SP2 now limits outbound connection attempts to no more than 10 at one time."
http://forum.shavlik.com/viewtopic.php?t=1291 (topic of the thread is about a network scanner that won't work anymore but i think it's relevant)
These two limits are not the same, the incomming is 10 connections using file or printer services (10 concurrent connections total), the second is 10 connections per second outgoingric melia wrote:From what i have read, SP2 just added to the limits by limiting outbound as well as inbound:
"Similar to the inbound connection limit Microsoft imposed on Windows 2000 Professional and Windows XP (where these platforms are limited to 10 simultaneous inbound connections), Windows XP SP2 now limits outbound connection attempts to no more than 10 at one time."
The incoming connections are only for windows services, not for programs running on the machine, outgoing connections by the above definition are limited to 10 per second. So using XP pro should not be a problem.
Michael
Missing Hmailserver ... Now running Debian servers
I agree, Win 2003 is more stable and have better performance than XP.CraigHarris wrote:I would without question, use Windows 2003 R2 - it's a rock solid OS with every feature you may need.
XP is not designed for hosting servers, but it will suffice if you cannot afford 2003.
Here is a quote from a guy in newsgroup microsoft.public.virtualserver:
The XP operating system is tuned for different workloads than Server 2003.
First of all, XP allocates it's various memory regions differently than
Server 2003. On a large system running many virtual machines, some of the memory pools may be exhausted before the system's physical memory limit is reached.
Second of all, Server's network stack is tuned such that it is capable of
handling higher throughput and more connections than XP.
Third of all, the execution quanta (the time a thread spends executing when it is granted processor time) is significantly higher on server than on XP. This means that less processor time is wasted on context switches on server, at the cost of reduced responsiveness on the console when the server is under load.
regarding win2k3
this is exciting reading...
now I have a little question here from little Denmark..
for a win2k3 r2 server, that should run apache and hmailserver
lets say the hmail has 3 domains - with 30 accounts on each domain
how big a license do I need for my windows 2003 R2 server ?
best regards from troels

now I have a little question here from little Denmark..
for a win2k3 r2 server, that should run apache and hmailserver
lets say the hmail has 3 domains - with 30 accounts on each domain
how big a license do I need for my windows 2003 R2 server ?
best regards from troels
Re: regarding win2k3
I would recommend the Standard Edition.troels_dk wrote:this is exciting reading...![]()
now I have a little question here from little Denmark..
for a win2k3 r2 server, that should run apache and hmailserver
lets say the hmail has 3 domains - with 30 accounts on each domain
how big a license do I need for my windows 2003 R2 server ?
best regards from troels
I dont think the web edition can run apache.
You can also compare here:
http://www.microsoft.com/windowsserver2 ... tures.mspx
Troels, study here for licensing and features:
http://www.microsoft.com/windowsserver2 ... t.mspx#E1C
http://www.microsoft.com/windowsserver2 ... ition.mspx
http://www.microsoft.com/windowsserver2 ... tures.mspx
http://www.microsoft.com/windowsserver2 ... t.mspx#E1C
http://www.microsoft.com/windowsserver2 ... ition.mspx
http://www.microsoft.com/windowsserver2 ... tures.mspx