Autorep:
That is a mighty darn impressive first post. Welcome to the group!
What you were doing was definitely different than what this post was originally about, but equally difficult. What you have set up is a wireless bridge. Some WAPs (Linksys' WAP - not their wireless router, mind you, but their straight WAP,
the WAP54G) have a wireless bridge function built in. It turns out that you got lucky and the Belkin (sort of) supports that. Did you use the
Belkin wireless bridge addendum to help you set that up? (I guess it's in the
latest manual, too.) Interestingly, it claims that "... you can only bridge your Wireless G Router (model F5D7230-4, F5D7231-4) to a Belkin Wireless G Range Extender/Access Point (model F5D7131, F5D7130)," but you managed it with two F5D7230-4s by putting the secondary one in Access Point Mode. As you mentioned, that turns off the routing (NAT IP sharing) and the DHCP server. That also changed the default IP address to 192.168.2.254. I'm fairly impressed with Belkin's router. My Netgear and Linksys routers don't have the Access Point mode or Bridging feature. (Yeah, I have two. Don't ask.)
Set up all computers either DHCP enabled (Dynamic IP addresses / IP addresses automatically get assigned to the computers during each session) or Static IP addresses (set the IP address once and forever). As I suspected that part of the problem was IP addresses (because I had seen connections terminated due to �another computer on the network already has the same IP address�, I elected to go static even though I had a dynamic IP account with my ISP.
I suspect this has nothing to do with your IP account with your ISP. It's probably the fact both of the Belkin wireless routers originally had active DHCP servers for your inside LAN network. Your computers were broadcasting requests for an IP address but sometimes the primary router answered and sometimes the secondary answered. Since the two routers are on the same network, but don't know about each other's DHCP server and aren't cooperating with each other, they both start handing out addresses at the same starting IP (probably 192.168.x.2 through 192.168.x.100 or .255). Therefore, more than one computer gets 192.168.x.2 (where x appears to be "2" by default for Belkin equipment [0 in Netgear and 1 in Linksys], but anything in the range 0-255 is valid) so there probably were conflicting IPs.
You should be able to go back to using DHCP for the PCs, but leave the DHCP server off in one of the two routers. You'll still want the secondary router at a fixed IP address so that you know what it's address is for administration purposes. I would set it's LAN IP address to 192.168.x.2 (where the primary Belkin router is using 192.168.x.1 - again where x is probably "2"). You would also need to change the DHCP server range on the primary router to not serve the .2 address and to serve less than the entire range of available IP addresses. Linksys' DHCP server serves 192.168.1.2 through 192.168.1.100 by default. Belkin appears to do the same but using the 192.168.2 subnet. Netgear does the whole range, which I find a bit stupid.
Congrats on getting this all set up even if you did find it a bit hairy.