unix wrote:
> I have a sort of funky setup I'm trying to get working.
>
> PC #1 has two NICs:
>
> NIC1 - Wireless card getting internet (DHCP) from a router using
> 192.168.0.x subnet
> NIC2 - Ethernet card I want to use for sharing NIC1 connection. (If I
> use ICS, it tries to assign this NIC 192.168.0.1 and THIS is a
> problem).
>
>
> PC #2 Has one NIC with a crossover cable to NIC2 on PC #1.
>
> In a nutshell, my cable router is NATing the real cable modem address
> to 192.168.0.0 and this conflicts with ICS setting for NIC2. Is there
> a way to force ICS to use some other network ???? Note, I don't have
> admin access to the wirelesws router and can't force it to use some
> other inside subnet. Since the router is in effect 192.168.0.1, the
> ICS wizard craps out and I need to trick it (if possible).
>
> Thanks in advance
> Ron
>
Short answer - no.
From MS KB 310563
http://support.microsoft.com/kb/310563/en-us
The following is a list of Internet Connection Sharing components:
• DHCP Allocator. A simplified DHCP service that assigns the IP address,
default gateway, and name server on the local network.
• DNS Proxy. Resolves names on behalf of local network clients and
forwards queries.
• Network Address Translation (NAT). Maps a block of private addresses
to a set of public addresses. NAT tracks private-source IP addresses and
public-destination IP addresses for outbound requests. It changes the IP
address information and edits the required IP header information
dynamically.
• Auto-dial . Automatically dials connections.
• Application Programming Interfaces (APIs). For configuration, status,
and dial control for programs.
In effect, ICS is acting as a second router in the path from your second
computer to the ultimate Internet connection, including its own DHCP
server and its own NAT. AFAIK, there is no way to configure these
components of ICS. That is, you can't change the IP it assigns to the
LAN-side NIC and you can't change the range of IP addresses that its
DHCP Allocator hands out.
Try doing it manually. Turn off ICS and bridge PC1/NIC1 and PC1/NIC2
from Network Connections. I don't know if PC2/NIC will be able to
obtain an IP address from the wireless router's DHCP server. If not,
assign it a static IP address in the 192.168.0.x segment, with a value
that's not likely to be used elsewhere in the LAN (e.g., 192.168.0.82)
and set values for Gateway and DNS server to point to the wireless
router (get these values from ipconfig /all for PC1/NIC1).
--
Lem MS MVP -- Networking
To the moon and back with 64 Kbits of RAM and 512 Kbits of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer