how-to block ads
|
MDEO
join:2008-05-08 | reply to Bill_MI
Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:
Okay, my PC/Netgear FA311 is set to obtain everything automatically.
Is that the info you requested? | |
Bill_MI
Bill In Michigan
Premium,MVM
join:2001-01-03
Royal Oak, MI
 ·EarthLink
| Yep. So the BEFSR41 WAN looks like another PC connecting "automatically" (also known as DHCP). Usually, the modem shouldn't care whether it's your PC or the BEFSR41 getting the address.
You might try »Linksys FAQ »The Loooooooong Reset to the rescue and reconfigure the BEFSR41.
If it still doesn't pull an address, the reason could be a lot of things ranging from a bad port or cable (hardware) to needing the right hostname when pulling the address. Cable modems/systems use network card MAC address and the BEFSR41 can clone a MAC (»Linksys FAQ »How and Why Do I Clone a MAC?).
Sometimes a power cycle resets things. In the old days some customers actually had to call in their MAC address for their cable modems to work. I doubt you have anything this drastic. | |
Bytebender
Bytebender
Premium
join:2008-02-12
Canada
edit:
May 12th, @07:06PM
| reply to MDEO
WinXP SP2 OS
Verizon (West Coast) ISP
Router set to "Obtain IP address automatically"/"Obtain DNS server address automatically"
Netgear FA311 Lan Card
Firewall OFF
If you're west coast - you don't need to worry about PPPoE - you connect via DHCP.
Yes, the Westell B90-210015-04 modem and the LinkSyS BEFSR41 router should get along quite nicely.
I checked your other post - OK - that Westell modem is just a bridge, (or a dumb modem), meaning that it has no user interface to access, so the 192.168.1.1 thing doesn't apply here at all, so don't worry about that.
To start - when you connect your XP machine directly to your modem, can you get online?
IF so, all you need to do is open the DOS command prompt and release your IP address with the command "ipconfig /release", (this is the key step that I didn't see mentioned in any previous replies, if you don't release the IP, then it will remain "bound" to the MAC of the XP machine, meaning only the XP machine will recieve an IP from VZ, and the Linksys will not be able to), at this point your PC should have an IP af 0.0.0.0 - then disconnect the power cable from that modem, (so the IP cannot renew). Then reset that Linksys so it's back at the factory defaults, (the Linksys is set to do DHCP by default, and this is what you want it to do), Then connect the Linksys WAN port to the modem and your PCs to the LAN ports. Then power up the modem, when it's Ready or DSL light stops flashing, power up the Linksys, then the PCs - at this point the Linksys should pull a public or WAN ip from VZ and deliver private IP's (the 192.168.x.x) to the PC's. - If it doesn't pull a public IP from VZ - go to the Linksys Status page and click renew. If it still doesn't get a public IP, and the cabling is correct, the IP release may not have worked, in which case you may need to call for tech support, tell them you're adding a router and have them release the IP for you, (should only take a few minutes), or something may be wrong with the Linksys. If it does get a public IP, then you're online, and as long as the PC's are also set to communicate by DHCP, (or automatic), then which Operating Systems are in use, (Windows, Linux, MAC, Sony, X-Box, etc.), doesn't even matter.
Hope this helps some.
| |
MDEO
join:2008-05-08
| ByteBender, I cannot thank you enough. Seriously.
This router stuff has been boggling me on/off for several days now... and you come along and resolve the issue in one fell swoop.
Thank you again.
The "ipconfig /release" has it! (Sorry, bad government joke)
Indeed, it was the "ipconfig /release" command which resolved my impasse issue here.
Thanks again Byte! And thanks to the rest of you for helping as well!
P.S. Funny how LinkSYS themselves couldn't resolve this issue after two days of thorough (or is that not-so-thorough?) Tech Support.  | |
Bytebender
Bytebender
Premium
join:2008-02-12
Canada
| You're definitely welcome anytime.
It's actually an ISP thing, yours uses strict MAC filtering on the DHCP connections, meaning they capture and record the MAC of whatever device you connect with, binding that MAC to the IP address issued. Thereafter, until the DHCP lease expires, only that MAC can receive an IP on that circuit. Releasing the IP unbinds it from that MAC, allowing a new MAC to then be captured and recorded.
Any way you're quite welcome
enjoy.
--
reboot, reset, reconfigure, then recycle. | |
|
