upgrade pc to windows server 2003

hi

i have a program and databse running on windows xp pro.

as xp pro iis only takes 10 connections i think its time to upgrade.

is it possible to buy windows server 2003.
which will run my applications in the same way as xp pro only allowing more connections.

please excuse me if this seems an obvious question but i have no real hands on experience with servers and just want to make sure before i buy the software.

thanks in advance

When you say connections, are you meaning some database connections or FTP connections?

i basically want more connections to a webpage i have sitting in my inetpub folder.

at the moment xp pro only allows 10 connections, to view the webpage.

NOTE:my wep page app does infact communicate with the database
NOTE: there is also a windows program running on the same machine which communicates with the same db

Well I'm running XP Pro SP-2 and I dont see any limitations on web page connections at all. The only place is for FTP connections.

There are no limitations in XP Pro or Server 2003 for websites.

http://support.microsoft.com/?id=314882

i seem to have a limitaion of people viewing the website.

For Windows XP Professional, the maximum number of other computers that are permitted to simultaneously connect over the network is ten. This limit includes all transports and resource sharing protocols combined. For Windows XP Home Edition, the maximum number of other computers that are permitted to simultaneously connect over the network is five.

I read that too but I also read the end ...

Quote:

---

Per development: The connection limit refers to the number of redirector-based connections and is enforced for any file, print, named pipe, or mail slot session. The TCP connection limit is not enforced, but it may be bound by legal agreement to not permit more than 10 clients

---

I dont think they are talking about website connections but remote or network connections?

Either way, if your wanting to run IIS for a website you really should be running Server 2000 or 2003. No limits on web connections but device or user connections do require CALs (Client Access Licenses) which you have to purchase separetly.

You might want to lower the inactivity timeout disconnect from 15 minutes to 5 or 10 minutes. When a connection times out you release another connection and make it available for someone else to use.

Code:

---

net config server /autodisconnect:time_before_autodisconnect

---

thanks robdog

i need to look into it more,
as i have never used windows server 2003 i wanted to know if it would take more connections and not have a bad effect on my programs. ( before i buy it )

i am unaware of client access licenses and will also do a but of reading up on that.

You will only need them for any computers you attach to its domain basically. If your using SQL Server then you can install it on the same machine or if its on a second system then a CAL will be necessary (for if your website uses a db conn). It can handle as many website visitors as the hardware can support the resources of the system. If the pages are served slow it could either be system resources or your internet connection, etc.