| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 96621 | 2009-01-16 21:56:00 | Linksys WAG160N Static IP Trouble | Phil B (648) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 739532 | 2009-01-16 21:56:00 | I got the above router & cannot connect to the internet with a static computer ip address. The router's got 2 computers connected to it, 1 with dhcp which connects to the internet ok, the other with a static ip that doesn't. Both computers can see each other via pinging the ip adresses. This same setup worked well with a Belkin router. The Belkin is now being used at work due to the demise of the alcatel speetouch. Ubuntu 8.04 is dhcp. Ubuntu 8.10 is static ( after some messing about to get it so) This setup has worked with either Ubuntu on both pc's or Ubuntu on 2 pc's & XP on another when 3 were connected to it, all with static ip's, so I know it's something to do with the router. I've googled & so far I can't find a solution Any Ideas??? |
Phil B (648) | ||
| 739533 | 2009-01-16 22:25:00 | Oops forgot to say. Wireless disabled, connected via ethernet | Phil B (648) | ||
| 739534 | 2009-01-16 23:09:00 | Is the static IP within the DHCP range? Can you ping google? I have the same prob (although working to my advantage) - my server's IP is 192.168.1.3 and my DHCP pool starts from .1.5 - I use this to block access to the internet to my server, while still allowing local network access. |
jwil1 (65) | ||
| 739535 | 2009-01-16 23:23:00 | I've tried it inside & outside the dhcp range with no luck. I can't find anywhere to set the range I want, as you can with the Belkin | Phil B (648) | ||
| 739536 | 2009-01-16 23:38:00 | What is the IP of the router? Try setting the static ip to 192.168.X.99 |
jwil1 (65) | ||
| 739537 | 2009-01-17 00:28:00 | The router ip is 192.168.1.11 The dhcp range is from 100 to 140. It doesn't matter if I go above or below, only one computer can connect to the internet at a time. I've got them both on dhcp now & still 1 connects. I'm going to try swapping the ethernet cables to different ports & reboot the router & I'll get back in a few mins |
Phil B (648) | ||
| 739538 | 2009-01-17 00:58:00 | Ok, now I've got both connected to the internet with dhcp enabled. I forgot to re-edit the interfaces file. But that still means that this router seems to be no good for static ip addresses. There's a facility for you static ip address from your ip, but not on the network. Mmmm, I think I'm going to have a go at getting my money back, as it doesn't work properly as far as I'm concerned. | Phil B (648) | ||
| 739539 | 2009-01-17 20:37:00 | Something very weird is going on, here. The router couldn't give a rats whether the client's IP is static or provided by the DHCP server. How would it even know? A valid IP address is a valid IP address. Presume you have set the correct gateway address and DNS addresses? On another note, if you can get your money back, do it. Google for the number of 160N's that have the wireless transmission stop. |
linw (53) | ||
| 739540 | 2009-01-17 21:19:00 | That's what I thought. The router doesn't have the facility to set the ip range. It only allows you to set the dhcp range. The default is 50, starting at 192.168.1.100 If you set your static ip to in or out of that range it wont allow internet connection, although you can network with other computers through the router. I've googled till the cows come home & there's plenty of people in the same boat. They don't tell you that in the magazine write ups | Phil B (648) | ||
| 739541 | 2009-01-17 23:06:00 | When you are setting a static IP are you also putting in the router's IP as the gateway and DNS server? | CYaBro (73) | ||
| 1 2 | |||||