Perhaps the simplest way to get your Amiga on the network is to bridge the ethernet and wireless adapaters in your PC. You do not need to enable internet connection sharing.
With bridging enabled, you'll manage a single virtual interface in your PC, which should be configured to use DHCP if you have a router or other device acting as a DHCP server.
Configure Miami to use DHCP as well. With bridging enable on the PC, all frames sent from your Amiga will be relayed through the bridge to the rest of the network. The bridge knows which devices are on which physical link and will relay frames between the segments as required.
Note, you can use static addresses if you want. With bridging enable, all devices are on the same subnet, e.g. 192.168.0.0/24. In that case, your router might be 192.168.0.1, your PC might be 192.168.0.2, and your Amiga might be 192.168.0.3. The subnet mask is 24 bits, 255.255.255.0. The default gateway is the router, 192.168.0.1. If you router provides DNS forwarding, your primary DNS server would be 192.168.0.1, too. (The router itself would use your ISP's DNS servers.)
All traffic between the Amiga and the PC will stay on the link between the Amiga and the PC. Any broadcast traffic from the Amiga, e.g. DHCP requests, will be forwarded to the router's segment.
All traffic from the Amiga destined for the router or a local host on the router's segment will be forwarded by the PC to the router's segment.
All traffic from the router or the router's segment destined for the Amiga will be forwarded by the PC to the Amiga.
(Internet connection sharing is convenient if your PC is connected directly to the Internet or another "public" network and you want to share that connection with other systems. Bridging is not used in thise case, and instead, the PC acts as a router. The local interface selected during the configuration of connection sharing will be assigned a static IP address by Windows and will host a small DHCP service. At any rate, it shouldn't be necessary in your case.)
(Some folks have also mentioned using the system's IP address as its default gateway, e.g. an IP of 192.168.0.3 and a gateway of 192.168.0.3. What this does is send all frames out to the local segment unmodified. It provides a convenient way to logically subnet a network without a router. It's particularly useful when using virtual networks in Virtual Server, VMware, and other products when it's not possible to set up virtual segments or you don't want to waste resources running a virtual host as a router. Note that it doesn't actually do what segmenting and subnetting were intended to do, which is reduce congestion on a local segment.)
Trev
