Essentially, you have two routers and are probably double natting. While not a good idea, it should still work. If you have the AT&T DSL router, you do not need the Linksys, it's redundant. If you want them both, there are two possible ways to do it: 1. Disable NAT on the linksys so it works as an access point or 2. bridge the AT&T router and use Linksys as you NAT device. The config should go like this: AT&T Router to Swicth -> Switch to computers This is not a netgear problem. Netgear cannot not offer an IT crash course with every $ 30.00 switch. Unmanaged switches either work or they don't. At this point, you have a pebcak error: multiple problems, double natting, ICS, all this is the likely result of tinkering around with the hopes that something untimately works. I'm not knocking you, this is the way you learn, getting dirty under the hood. Unfortunately, this unscientific approach usually leads to multiple misconfigurations and elongates the time to fix. If you are in a hurry, I would look for a tocal tech guy to come out and look at it. If you want to do it yourself, follow these directions: 1. Hook up the swicth to the working At&T router. Make sure Linksys is OFF and unplugged. 2. Hook up ONE computer to the switch. Make sure ICS is off on that computer. 3. Make sure the IP and DNS are set to automatically obtain. Turn off wireless LAN on that computer to make sure there is no interference from other networks. 3. Do an IPCONFIG /ALL. The computer's LAN ip's third octet (the x in 192.168.x.1) should be the same as the IP address you enter to get into the AT&T router's interface. The DNS should be the router's IP. 4. It should surf. If it does, go back to step 3 and add the next computer. Otherwise, double check all the steps have bee followed to the tee. Once finisshed adding your computers, call Linksys support and ask them how to configure it as a wireless swicth or access point only (no routing) if you want to have that device on your network. Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog

In the first IP config, the computer does not work because you do not have a valid IP address. 169.254.x.x is APIPA, a self assigning address when there is no DHCP server to assign you an address. In the second IP config scenario, your DNS server is on a separate private LAN subnet. That's usually not the case. What is the equipmet you have here? A modem/router from your ISP? Your own router? The switch? Also, make sure that all the PC's on the LAN have Internet Connection sharing turned off. Your router will be doing that job.Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog

OS: Windows 7 ISP: AT&T DSL modem Router: Cisco Linsys E2500 Switch: Netgear 8 port model FS108 I have to hook it back to the switch to check the Internet Connection Sharing & then switch back to respond...

I have ran a new ethernet line from my router to my small home office (3 computers), the ethernet cable is connected to a switch (netgear 8 port model fs108). All computers connected to the switch identify and connect to the network and report an internet connection. However, I cannot open a web page in my browser. If let alone long enough, I get the "ie cannot open web page". When I click the diagnose connection button, it reports that it cannot find a problem. When the ethernet cable from the router is connected directly to one computer (bypassing the switch), the internet works great. Please help, I need to have this resolved tonight!

If the switch was the problem then the other two computers would not work. Unless you only have that one problematic computer connected to the switch. Regardless, in the DNS IP address above, you have your primary DNS's IP as 192.168.1.254, it should be 192.168.0.1 which is your router. The router will proxy DNS using the ISP's DNS. Also, if the switch was defective then you would not get an IP address from the router. In the second IPCONFIG post, your PC obtained an IP address. Can you specify why you posted two IP configs?Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog

Essentially, you have two routers and are probably double natting. While not a good idea, it should still work. If you have the AT&T DSL router, you do not need the Linksys, it's redundant. If you want them both, there are two possible ways to do it: 1. Disable NAT on the linksys so it works as an access point or 2. bridge the AT&T router and use Linksys as you NAT device. The config should go like this: AT&T Router to Swicth -> Switch to computers This is not a netgear problem. Netgear cannot not offer an IT crash course with every $ 30.00 switch. Unmanaged switches either work or they don't. At this point, you have multiple problems, double natting, ICS, all this is the likely result of tinkering around with the hopes that something untimately works. I'm not knocking you, this is the way you learn, getting dirty under the hood. Unfortunately, this unscientific approach usually leads to multiple misconfigurations and elongates the time to fix. If you are in a hurry, I would look for a tocal tech guy to come out and look at it. If you want to do it yourself, follow these directions: 1. Hook up the swicth to the working At&T router. Make sure Linksys is OFF and unplugged. 2. Hook up ONE computer to the switch. Make sure ICS is off on that computer. 3. Make sure the IP and DNS are set to automatically obtain. Turn off wireless LAN on that computer to make sure there is no interference from other networks. 3. Do an IPCONFIG /ALL. The computer's LAN ip's third octet (the x in 192.168.x.1) should be the same as the IP address you enter to get into the AT&T router's interface. The DNS should be the router's IP. 4. It should surf. If it does, go back to step 3 and add the next computer. Otherwise, double check all the steps have bee followed to the tee. Once finisshed adding your computers, call Linksys support and ask them how to configure it as a wireless swicth or access point only (no routing) if you want to have that device on your network. Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog

OK, I wish I had read that before buying a new switch, which I did today. LOL I posted two IP configurations because my computer connected to a different network, one that doesn't seem to really exist. I should be connecting to the "Home Network" which is the 2nd IPCONFIG I posted, the first is the "Network" and is labeled as a "work" connection (it seems to only be a connection between the 3 computers on the switch, no internet, no access to my home network). I think the DNS is set to automatic. I'm really lost here.

I got the same result from the new switch, so I'm taking it back and have hooked up my original one. Why won't this work? It is supposed to be plug & play with everything done automatically.

ICS was enabled, I disabled it... still nothing. I took the switch & hooked it up to my xbox, worked immediately - so I'm assuming that the problem is a setting or someting on the computer.

Hello, What type of router do you have? When you are experiencing this problem, please open a command prompt. Type IPCONFIG /ALL and post the results back here. Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog

OK, thanks for the reply and soory for the delay. Now - for some reason - it didn't connect to my network. Instead it connected to "NETWORK" and was labeled a work connection with no internet access. Before I do a restart and try again... My router is a linksys E2500... Here is the IPCONFIG/ALL report... Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\***>IPCONFIG/All Windows IP Configuration Host Name . . . . . . . . . . . . : ***-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Mixed IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Wireless LAN adapter Wireless Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Dell Wireless 1397 WLAN Mini-Card Physical Address. . . . . . . . . : 90-4C-E5-3A-FA-3B DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connecti on Physical Address. . . . . . . . . : 00-24-E8-F9-28-61 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::9cb0:aba4:ebf3:676e%10(Preferred) Autoconfiguration IPv4 Address. . : 169.254.103.110(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : fe80::6dd7:7bb8:dfec:d805%10 DHCPv6 IAID . . . . . . . . . . . : 234890472 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-6A-FB-EC-00-24-E8-F9-28-61 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{F652C48B-8020-470D-9CE7-CDD728E79BCB}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.{AA85E914-C227-4B24-9D73-2021BF8C29DB}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

OK, now it's connecting & doing as it was before... Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\****>IPCONFIG/ALL Windows IP Configuration Host Name . . . . . . . . . . . . : ****-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Mixed IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Wireless LAN adapter Wireless Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Dell Wireless 1397 WLAN Mini-Card Physical Address. . . . . . . . . : 90-4C-E5-3A-FA-3B DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connecti on Physical Address. . . . . . . . . : 00-24-E8-F9-28-61 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::9cb0:aba4:ebf3:676e%10(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.124(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Sunday, August 19, 2012 9:11:04 PM Lease Expires . . . . . . . . . . : Monday, August 20, 2012 9:11:03 PM Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 234890472 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-6A-FB-EC-00-24-E8-F9-28-61 DNS Servers . . . . . . . . . . . : 192.168.1.254 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{F652C48B-8020-470D-9CE7-CDD728E79BCB}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:24b4:2fd4:3f57:ff83(Pref erred) Link-local IPv6 Address . . . . . : fe80::24b4:2fd4:3f57:ff83%12(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{AA85E914-C227-4B24-9D73-2021BF8C29DB}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

Somebody help me PLEASE! Netgear "tech support" is trash, I can't even get a response from them, and there "community forum" is just as bad. The "help" I've gotten has not been productive.

Looks like the problem is DNS. Try this: ping www.google.com (should not reply) ping 8.8.8.8 (should reply) If the above is correct, then the problem lies in DNS Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 234890472 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-6A-FB-EC-00-24-E8-F9-28-61 DNS Servers . . . . . . . . . . . : 192.168.1.254 192.168.0.1 You DNS server (192.168.1.254) is on a separate, private subnet. Unless you have two subnets with local DNS servers, then likely culprit is that you have a static DNS entry in your NIC. Set you NIC card to automatically obtain DNS the restart that PC. Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog

8.8.8.8 got me nothing, and my DNS is set to automatic. I wonder if my switch is the problem, I have had it for a while and it's just been sitting in storage for about a year.

Thanks for the condescending tone, it really helps. The AT&T DSL MODEM only has one ethernet port and it does not broadcast wireless, which is why I need the linksys router. I cannot hook the switch directly into the modem, one - because it is about 80 feet away from my office and I only have one ethernet cable ran from there to my office, so I wouldn't be able to hook up the other 2 computers in my office unless I installed a second switch I suppose. Two - without the linksys, I wouldn't have wireless.