<article style="outline:none;"> On Windows 7: A: First network: public wireless network with internet access B: Second network: home network for sharing files around the house -- connected by ethernet to my principle server and then a wireless network for other computers in the house. As soon as I connect B, internet stops working on the ethernet connected computer. Gateways for both networks are different: 192.168.1.1 versus 192.168.0.1. I don't understand why I can't have internet AND connection to my private network. Help! </article>

It is not clear how this is all configured, but you should not need to use two different IP subnets to achieve that. There is no reason why the machines cannot all be in either 192.168.0 or 192.168.1 . They should all have local connectivity and Internet access. Neither of those is really a public network - they are both reserved private IP subnets. What device actually connects directly to the Internet and gets a public IP? Do you have a modem/router?Bill

Install Remote access and Routing service on your server (Second network) to bridge this two seperate networks together.

The public network is one my building provides for wifi internet. It works fine until I connect my router...

Bill_____ wrote: <article style="outline:none;"> On Windows 7: A: First network: public wireless network with internet access B: Second network: home network for sharing files around the house -- connected by ethernet to my principle server <http://www.techspot.com/community/#> and then a wireless network for other computers in the house. As soon as I connect B, internet stops working on the ethernet connected computer. Gateways for both networks are different: 192.168.1.1 versus 192.168.0.1.  I don't understand why I can't have internet AND connection to my private network. Help! </article> If you have 2 standard gateways, that can not really work. You need only one standard gateway and that should connect to the internet. If you need additional routes for for home network you have to configure them via the "route add" command and avoid using a standard gateway, which does not connect to the internet. BTW if you need further assistance a post of the output of "ipconfig -all" and "route print" would be quite helpful. Wolfgang

This link is for XP but the principle is the same: http://support.microsoft.com/kb/299540 The reason why your Internet cuts off when you connect your Ethernet cable is because the wired network has an automatic lower metric (meaning it has a higher priority). Since you are probably running DHCP on both the wireless and wired networks, your wireless will have a higher metric meaning that it is a slower connection. By default, Windows will assume Internet is on the faster metric. As you can guess, this is not always the case. If you want to investigate your IP metric, open an administrative command prompt and type: netsh interface ipv4 show addresses. You will see not only your DHCP provided address, but the InterfaceMetric assigned. You will notice that your wired connection has a lower metric, thus forcing all Internet traffic to that route. The real question is how to fix. Under your adapter settings and Advanced TCP/IP Settings, unselect the Automatic metric and manually assign a number on your wireless connection so that it is lower than your wired connection. This will give you both Internet and local network access. (I would attach screen shots, but the TechNet forums have not been rendering them correctly recently)