|
#1
|
|||
|
|||
|
I recently changed ISPs to a local provider called i29.net. Thinking myself smart, and saving a few bucks by changing ISPs, I trotted out to pick up a router so as to connect all three of our household's computers to our new service. And that's when the headaches started...
I have no problem getting the router set up, and the other computers can connect to it, we're all on the network, etc. However, it seems the router cannot connect to the Internet. If I connect the modem to the computer and take the router out of the eqation, everything connects fine. It seems the issue is in getting the modem and router to "talk" to each other. I tried to get some help from the new ISP's only two tech guys (lol) and got nowhere. They were unable to tell me any settings such as DNS (because the modem is "automatic setup, it does it all itself"), nor did they even know the provider that supplies them (I tracked it through WhoIs - they go through AT&T Worldnet). It has to be some stupid setting I'm missing somewhere, and I think I'm getting tunnel-vision on this. Anyone have any ideas for me? Internet options/settings' boxes are all unchecked, everything's set up to automatically detect settings, etc. I am using a Belkin G Wireless Router, IP 192.168.2.1. Network Adaptor is a RealTek RTL8139 Family PCI Fast Ethernet NIC. The modem, supplied by i29, is a Ripwave wireless broadband access modem from Navini Networks, model # 2.5-2.6 LMX E, if that helps. The info I get from ipconfig/all while connected directly through the modem is: Physical Address........................................... ....: 00-20-18-DB-60-17 DHCP Enabled........................................... ........: Yes Autoconfiguration Enabled...................................: Yes IP Address........................................... .............: 12.15.100.238 Subnet Mask.............................................. .......: 255.255.252.0 Default Gateway........................................... .....: 12.15.100.1 DHCP Server............................................ ..........: 12.31.252.1 DNS Servers........................................... ...........: 12.28.104.254 .................................................. ....: 12.28.104.253 These settings using the the router change to: Physical Address........................................... ....: 00-20-18-DB-60-17 DHCP Enabled........................................... ........: Yes IP Address........................................... .............: 192.168.2.1 Subnet Mask.............................................. .......: 255.255.255.0 Default Gateway........................................... .....: 192.168.2.1 DNS Servers........................................... ...........: 12.28.104.254 .................................................. ....: 12.28.104.253 I've tried playing with the settings to match what I get when connected directly through the modem, using them to try to connect when using the router, tried using the setup CD that came with the router and letting THAT determine the settings, etc. I've tried just about every setting configuration I can think of, and none of it gets me to the Internet through the router. So far, the only solution I've been offered is to go out and buy either a Linksys or Netgear router but since I'm broke and just bought this stupid Belkin a few days ago, I'd REALLY like to get that working if I could. All of my tech knowledge has been from trial and error here on my home system, so I'm pretty sure it's just some setting I'm not seeing. Thanks in advance for any and all advice and suggestions!! The Zookeeper |
|
#2
|
||||
|
||||
|
From my limited knowledge you should NOT have DHCP enabled on both - let the modem sort it out and disable DHCP on the router.
__________________
GEM |
|
#3
|
||||
|
||||
|
depends what we're looking at,. if the above are ipconfig /all output from the PC when connected to each of the modem + router that's fine since it's just saying we have dhcp (client) turned on for the PC
the trick is to make the router talk to the modem., what is on the i'net (WAN) side of the router - it is ethernet? when you connect the router to the modem you might need to use a cross over cable between them rather than a patch cable - though most devices these days are auto sensing if the modem is ethernet and the router is ethernet on the WAN side then it should be a matter of putting them together, you can / should turn on dhcp (client) on the router (for the i'net side) are there diagnostic / setup screens on the router, when connected to the modem it should show settings similar to the PC when it was connected direct to the modem, i.e. IP Address........................................... .............: 12.15.100.238 Subnet Mask.............................................. .......: 255.255.252.0 Default Gateway........................................... .....: 12.15.100.1 DHCP Server............................................ ..........: 12.31.252.1 DNS Servers........................................... ...........: 12.28.104.254 |
|
#4
|
|||
|
|||
|
I'm negotiating a similar setup -- similar modem, different router.
I disabled NAT on the router, and DHCP as suggested above, restarted everything and I was in business -- the modem seems happy to take over the DHCP duties. It's still not perfect: my Mac seems to be able to kick my Windows computer off the net and I have to restart the modem and router again but we're getting closer. |
|
#5
|
||||
|
||||
It's still not perfect: my Mac seems to be able to kick my Windows computer off the net and I have to restart the modem and router again but we're getting closer. dhcp should be turned on for both the modem and router, the dhcp will give the router an i'net address on it's WAN side (i'net side) and the dhcp on the router will give out LAN (private address space) IPs on it's home network side, which requires NAT to be on for the router make sure if there's a setting on the router that DHCP pass-through is turned off (if it has that setting) and then the DHCP server on the router should give out LAN IPs and use the NAT to translate between the two networks (unless of course the modem has NAT built in and hands out private address space IPs - but that doesn't look to be the case) |
![]() |
| Tags |
| belkin, broadband, cable, computer, dhcp, dns, happy, home, internet, make, modem, nat, netgear, network, realtek, router, settings, talk, vision, windows, wireless |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Make Your Own Router - secrets revealed | silver | Networking | 356 | 09-February-2010 00:13 |
| tesco ADSL broadband router config setup and settings | silver | Tesco ADSL Broadband | 12 | 27-March-2009 19:26 |
| New Router Issue | yellit | P2P File Sharing | 1 | 03-November-2007 01:27 |
| Wireless router will not issue new IP address | mmartin | Networking | 3 | 17-January-2005 11:56 |
| Netgear MR814v2 wireless router won't talk to BT Broadband | David.Castell | Broadband Internet Access | 7 | 23-December-2004 23:05 |