Can ICS handle 40+ connections no prob?

[thirdlegstump]

Just wondering.

 

[nweaver]

would depend on the box. If you are getting lots of connections, change the machine to something intended for routing, like an ipcop or smoothwall machine.

 

[thirdlegstump]

Box would be a 2500+ XP with 512MB with multiple NICs. I cannot actually change the OS due to the machine running a light database application requiring Windows so it'd have to be Windows 2000/XP ICS. Connection is a 1.5/1.5 SDSL with static IP.

 

[randal]

You won't be able to max out ICS on a 1.5mbps link. Use it and abuse it without worrying.

 

[Fardringle]

Windows XP Pro is limited to a total of 10 simultaneous connections. You will need a server OS or one of the firewall router options that nweaver mentioned in order to allow the 40+ connections that you want to use.

 

[skyking]

Originally posted by: Fardringle
Windows XP Pro is limited to a total of 10 simultaneous connections. You will need a server OS or one of the firewall router options that nweaver mentioned in order to allow the 40+ connections that you want to use.

:thumbsup:

 

[thirdlegstump]

Originally posted by: Fardringle
Windows XP Pro is limited to a total of 10 simultaneous connections. You will need a server OS or one of the firewall router options that nweaver mentioned in order to allow the 40+ connections that you want to use.

hm..how do you explain the current machine handling the database with 40+ clients connected at all times via tcp? Or is that just an ICS specific limit?

 

[syco83]

maybe they aren't all connected at the same time.
I heard that there is a max of 10 connections on a non server os.

 

[thirdlegstump]

hm...I guess it could be that it's switching connections between about 50 unique IPs in 1ms intervals or something otherwise yea man, they're ALL connected to it at the same time.

 

[Fardringle]

It's possible that the database application you are using is doing something to get around the Windows XP connection limit.

But Windows XP file and resource sharing and ICS are all limited to 10 simultaneous connections. You can set it up the way you described, you just won't be able to have more than 10 people using the Internet at a time.

 

[Agamar]

Add web server programs (including IIS and Apache) to the list of programs limited to 10 connections on a non-server Windows box. Could be that your database makes fast open/close connections, and you just haven't seen the problem.

 

[thirdlegstump]

Question about Server 2000 or 2003 then, would I need CALs for every user who wants to connect or is that just limited to AD users?

 

[EULA]

Originally posted by: deathkoba
Question about Server 2000 or 2003 then, would I need CALs for every user who wants to connect or is that just limited to AD users?

usually you're required to have CALs for every device capable of connecting to the server.

 

[bwnv]

ICS is simple passthrough. It doesn't mean 50 computers are connecting to the box, they're just using the nics to get to the web. Unless I missed something he didn't say how many users actually connected, ie. to the database at the same time? The box won't care how many are sending data through it unless they all try to log in.

 

[thirdlegstump]

All the computers are connected at the same time.

 

[mobilecommand]

Windows 2000 / 2003 is lic 2 ways

Per seat and per server

Per seat means you need a lic for every user that could connect to your server but your lic can get applied to all servers in your netowork
" 200 users and 10 server = 200 lics"

Per server means you need a lic for every concurrent connection to your server
"200 users and 1 server and you want 50 total concurrent connections = 50 lics"

In network where you have multiple servers per seat is the way to go..

 

[n0cmonkey]

If the machine is doing database work, it's unacceptable as a gateway.

 

[nweaver]

n0c is wrong, let it run the database, ICS, and midget pr0n server. XP can handle it!