On Win7 host when configuring ICS how can I set so the NIC that is used for ICS would be in the IP ranges of 10.0.0.x instead of 192.168.x.x?

Hi, Can you say why you want to do it please ? Saln go foill, Paul

Hopefully a better explanation to my original post: On the HOST WIN7 I have 2 NICs. NIC 1 - internet NIC 2 - LAN When setting ICS on NIC1 for NIC2, NIC2 gets a static IP of 192.168.x.x so the client machines which get their IP by DHCP from Win7 host will also get the IP from the 192.168.x.x range. I would like it so that NIC2 would be assigned a static IP of 10.0.0.x when turning ICS on and thus the client machines will get their IP by DHCP in the IP range of 10.0.0.x.

Hi, Change the NIC-1 to 10.0.0.1 instead of 192.168.0.1 does this help or I am confused . Slan go foill, Paul

Hi, Change the NIC-1 to 10.0.0.1 instead of 192.168.0.1 does this help or I am confused . Slan go foill, Paul You mean NIC2 right? And also the problem is that Win 7 always assigns the static IP of NIC2 when enabling ICS to 192.168.x.x. And if I manually change it latter the client machines don't get the DCHP address' anymore.

Hi, Your NIC-1 is it connected to a modem. Where it get its IP address.

Hi, Your NIC-1 is it connected to a modem. Where it get its IP address. so what?

Hi, what I mean is you have NIC-1 as the internet connection how does it get to the internet is by a router modem.

NIC1 gets its IP from the ISPs DHCP. I do not understand what does NIC1 matter here?

Hi, Yes I should have said NIC-2 which you have already tried. I think to do what you want you would have to connect the NIC-2 to a router wan connection then put the other computers on the routers lan connections configuring the router with 10.0.0.1 it would then give the computers the 10.0.0.x Slan go foill, Paul

To get back to the original question, the answer is no. You cannot change the IP subnet which ICS uses. ICS is a cutdown, non-configurable version of NAT. When you enable ICS, it sets the private NIC to 192.168.x.1 (it used 192.168.0.1 before Win 7). It also enables an allocator (mini DHCP) which will give the machines on the private network an IP address in the same IP subnet as the NIC in the ICS machine and will also give them this NIC's IP address as default gateway and DNS address). The client machines connect to the Internet through the ICS machine using address translation and DNS relay. They do not get IP addresses in the same IP subnet as the machines on the public side of the ICS machine. It would not work if they did. The machines behind ICS must be in a different IP subnet. (That is why they changed the IP address. Some routers use 192.168.0.0/24 and ICS would not work with them). Internet | public IP router 10.0.0.1 | LAN machines 10.0.0.x dg 10.0.0.1 | 10.0.0.x dg 10.0.0.1 ICS 192.168.x.1 | 192.168.x.y dg 192.168.x.1 If you want the machines in the second segment to use the same IP subnet as the segment connected to your router you do not need ICS. You need to bridge the two NICs.Bill

Bill do you know of any good lightweight programs that give me better NAT control, so that I may be able to set scopes and dhcp ranges and optionally MAC reservation? btw. NIC1 has a PUBLIC IP ps. would it not be possible through a registry or some sort of a hack to use the address 10.0.0.1 on NIC2 instead of 192.168.x.1 and have the so called mini DHCP give out IPs in the range of 10.0.0.x?

Why not use a hardware device instead of a computer? ICS is very limited. If you run a server OS you can use RRAS. On a client OS you would need to use a third party NAT program like Wingate. www.wingate.comBill

In HKLM\System\CurrentControlSet\services\SharedAccess\Parameters change 3 string parameters: ScopeAddress, ScopeAddressBackup and StandaloneDhcpAddress - to 10.0.0.1.

Finally an answer. Thank you SlimShaggy.