ICS conection limit

[Guest]

How many connection can ICS handle at a given time ? I am running SP2 with
all the patches installed, Windows Firewall.

 

[Tony]

How many connection can ICS handle at a given time ? I am running SP2 with
all the patches installed, Windows Firewall.

.....and your operating system/version is????

Assuming your are using XP, there is a limit to the number of concurrent
connections that can be made (not specifically to ICS) which is 10 for XP
Pro and 5 to XP home

 

[Ron Lowe]

....and your operating system/version is????

Assuming your are using XP, there is a limit to the number of concurrent
connections that can be made (not specifically to ICS) which is 10 for XP
Pro and 5 to XP home

I don't think the 5- and 10- connection limit applies to ICS.
It applies to File and Print shared resources.

I don't think there is a hard coded limit for ICS, I guess it could perform
NAT for the entire 192.168.0.x subnet, which would theoretically allow for
253 clients: 192.168.0.2 thru 192.168.0.254.

I don't know how well it holds up in practice as the number of clients
increases. It may well be hardware-dependant. Probably the best thing to do
is 'suck it and see'.

 

[Guest]

Ok its WinXP Pro.

I am basically asking this question because I am using one gateway for 2
subnets (192.168.0.x and 192.168.1.x). My 192.168.0.x subnet has 50 clients
(all running WinXP Pro and Win 98 SE). It also has a Win 2K machine running
SQL on which ERP is being developed. My 192.168.1.x subnet has 10 machines
all running WinXP Pro.

Now the problem is that 192.168.0.x subnet can access the data on SQL server
without any problems, but 192.168.1.x machines are giving me problems.
Randomly, I loose access to SQL server. I can ping the gateway (192.168.0.1)
but not the SQL server and after some time everything is normal. This happens
2-3 a day and I cannot find the cause of this.

 

[Ron Lowe]

Ok its WinXP Pro.

I am basically asking this question because I am using one gateway for 2
subnets (192.168.0.x and 192.168.1.x). My 192.168.0.x subnet has 50
clients
(all running WinXP Pro and Win 98 SE). It also has a Win 2K machine
running
SQL on which ERP is being developed. My 192.168.1.x subnet has 10 machines
all running WinXP Pro.

Now the problem is that 192.168.0.x subnet can access the data on SQL
server
without any problems, but 192.168.1.x machines are giving me problems.
Randomly, I loose access to SQL server. I can ping the gateway
(192.168.0.1)
but not the SQL server and after some time everything is normal. This
happens
2-3 a day and I cannot find the cause of this.

I can't follow your description of the layout.
You havn't said where the ICS machine is,
or which side of ICS is in which subnet.
I'll try to guess..

192.168.1.x subnet ( 10 machines )
|
ICS machine 'External' side ( NIC 1, 192.168.1.1 )
ICS machine 'Internal' side ( NIC 2, 192.168.0.1 )
|
192.168.0.x subnet, ( 50 machines + SQL )

Is that correct?
So the 50 machines are all ICS clients?
And you want XP to route between these subnets?
You want the 192.168.1.x machines to be able to connect in to the
192.168.0.x machines?

It seems to me that you are using the wrong tool.
ICS will block connection attempts from the external side.
ICS is a NAT function.
I'm amazed this worked at all.

If you simply want XP to behave as a simple router to forward packets
between the 2 subnets, then you need to use IP Forwarding, not ICS.
Disable ICS, and turn on IP forwarding in the registry:
http://support.microsoft.com/?kbid=315236

Point each PC to the XP box as its default GW. ( or add a static route to
the other subnet. )