<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router: in Linksys</title>
<link>http://www.dslreports.com/forum/r20464527</link>
<description></description>
<language>en</language>
<pubDate>Wed, 11 Nov 2009 02:10:54 EDT</pubDate>
<lastBuildDate>Wed, 11 Nov 2009 02:10:54 EDT</lastBuildDate>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20473414</link>
<description><![CDATA[<A HREF="/useremail/u/1528515"><b>Bytebender</b></A> : You're definitely welcome anytime. <br>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.<br><br>Any way you're quite welcome<br>enjoy.<br> <br><small>--<br>reboot, reset, reconfigure, then recycle.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20473414</guid>
<pubDate>Tue, 13 May 2008 00:39:12 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20473170</link>
<description><![CDATA[<A HREF="/useremail/u/1550207"><b>MDEO</b></A> : ByteBender, I cannot thank you enough.  Seriously.<br><br>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.<br><br>Thank you again.<br><br>The "ipconfig /release" has it!  (Sorry, bad government joke)<br><br>Indeed, it was the "ipconfig /release" command which resolved my impasse issue here.  <br><br>Thanks again Byte! And thanks to the rest of you for helping as well!<br><br>P.S. Funny how LinkSYS themselves couldn't resolve this issue after two days of thorough (or is that not-so-thorough?) Tech Support.  ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20473170</guid>
<pubDate>Mon, 12 May 2008 23:29:57 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20470019</link>
<description><![CDATA[<A HREF="/useremail/u/1528515"><b>Bytebender</b></A> : WinXP SP2 OS<br>Verizon (West Coast) ISP<br>Router set to "Obtain IP address automatically"/"Obtain DNS server address automatically"<br>Netgear FA311 Lan Card<br>Firewall OFF<br><br>If you're west coast - you don't need to worry about PPPoE - you connect via DHCP.<br><br>Yes, the Westell B90-210015-04 modem and the LinkSyS BEFSR41 router should get along quite nicely.<br><br>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. <br><br>To start - when you connect your XP machine directly to your modem, can you get online?  <br>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 <b>key step</b> 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), <b>or </b> 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.<br><br>Hope this helps some.<br><br> ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20470019</guid>
<pubDate>Mon, 12 May 2008 13:46:24 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20468569</link>
<description><![CDATA[<A HREF="/useremail/u/277471"><b>Bill_MI</b></A> : 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.<br><br>You might try &raquo;<A HREF="/faq/linksys">Linksys FAQ</A> &raquo;<A HREF="/faq/4020">The Loooooooong Reset to the rescue</A> and reconfigure the BEFSR41.<br><br>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 (&raquo;<A HREF="/faq/linksys">Linksys FAQ</A> &raquo;<A HREF="/faq/2739">How and Why Do I Clone a MAC?</A>).<br><br>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.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20468569</guid>
<pubDate>Mon, 12 May 2008 07:53:30 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20468437</link>
<description><![CDATA[<A HREF="/useremail/u/1550207"><b>MDEO</b></A> : Okay, my PC/Netgear FA311 is set to obtain everything automatically.<br><br>Is that the info you requested?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20468437</guid>
<pubDate>Mon, 12 May 2008 05:46:10 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20467467</link>
<description><![CDATA[<A HREF="/useremail/u/277471"><b>Bill_MI</b></A> : Well, if the Linksys WAN cannot pull a 71.102 address same as the PC then something is missing.  I wondered if you had a very old (8 years+) type of DSL that used a PPPoE client in the PC but apparently not.  Pulling a public address via DHCP on a DSL system is not the norm (it's more like most cable systems run).<br><br>Exactly how is the PC set... You answered how the networking is setup on the PC: "obtain address automatically".<br><br>I'm still trying to decode what "LAN card shows reciprication" and "I see communique being made" means.  Are you reporting blinking lights?  making a web connection?  opening the modem page?<br><br>Looks like only the Verizon forum may the best shot to find the missing link.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20467467</guid>
<pubDate>Sun, 11 May 2008 22:25:01 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20466144</link>
<description><![CDATA[<A HREF="/useremail/u/1550207"><b>MDEO</b></A> : 1) Verizon ISP I've had for ~5 years.<br><br>2) Desktop is connected directly from Netgear LAN card to 2100 modem.  <br><br>2A) Desktop/Router connect A-okay... I think (I'm just a layman).  I see communique being made from Desktop -> Router -> through to Modem... so I would think my Router/Desktop connection is okay.  Am I right?<br><br>3) I'm not sure what ya mean by "PC set"... it's a stand-alone Desktop/WinXP SP2/3 LAN connections (Wireless (Disabled) - Netgear FA311 (DSL Connection/Router Connection) - Onboard LAN (Disabled)).<br><br>4) PC ISP is variable... assigned by DHCP... currently 71.102.XXX.XX (and obviously retains the 71.102.XXX.XX format).<br><br>5) Verizon ISP... the only place I recall having setup my Verizon ISP User Name/PW has been in my default email program - MS Outlook (where I have to input Usernames/PW's for each of my email accounts).  My Verizon ISP service was installed via an auto-installation disk provided to me when I purchased this ISP ~5 years ago.  Therefore, I'm not sure if my ISP account Username/PW has been setup somewhere else.  I simply know my DSL connection (via my Netgear LAN card) has not faultered when configured to "obtain an IP address automatically" and "obtain DNS server address automatically".<br><br>6) I monitor my Netgear card using WinXP Network Connections.  Nothing fancy.<br><br> ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20466144</guid>
<pubDate>Sun, 11 May 2008 16:36:41 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20464527</link>
<description><![CDATA[<A HREF="/useremail/u/277471"><b>Bill_MI</b></A> : Sanity check...<br><br>How many years ago did you set up this service with Verizon?<br><br>Are you connecting ok without the router?  Is it 1 PC plugged directly into the modem?  If so...<br>Exactly how is the PC set?<br>What are the first 2 numbers of the PC IP address? (like 192.168)<br><br>You have an account with Verizon.<br>Do you put the account name(email) and password somewhere?  Exactly where?<br>What exactly do you do to monitor your PC network card?<br><br>I'm not sure exactly what you have. :-)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20464527</guid>
<pubDate>Sun, 11 May 2008 08:25:00 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20464462</link>
<description><![CDATA[<A HREF="/useremail/u/1550207"><b>MDEO</b></A> : I checked the Router Setup Pages each time I attempted this new work-around.  This "Status Page" would not obtain an Internet IP Address nor any other information (DNS/Default Gateway/Et Cetera).<br><br>Lastly, it was/is the Router I pay attention too... however my LAN card shows reciprication also... and it's much easier for me to monitor this in comparison to this Router page/stuff.  LOL!<br><br>So you think I need a new modem?  If so, maybe I'll just buy a contemporary one (in lieu of a new router) and ditch this antiquated hamster wheel one.  Then again... knowing Verizon... the new modem probably wouldn't work either.  Hahahahahahaa!  ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20464462</guid>
<pubDate>Sun, 11 May 2008 07:42:50 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20463145</link>
<description><![CDATA[<A HREF="/useremail/u/277471"><b>Bill_MI</b></A> : <div class="bquote"><small>said by  MDEO <A HREF="/useremail/u/1550207"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>...my computer continued to recognize my LinkSYS router and send commands to the B90 modem.  However, the modem would not reciprocate.</div>This sounds like Westell's stuff running on your computer.  If so, the modem will never respond through the router.  It was designed before routers were common. :huh: It shouldn't need to run (but I'm sure Verizon forum would know).<br><br>Your PC is mostly isolated from the modem, now, so using the Linksys STATUS page you should be able to see what the router is getting.  THAT is the key you should be watching.<br><br>Here's what latest BEFSR41 STATUS page looks like: &raquo;<A HREF="http://ui.linksys.com/files/BEFSR41/v4/1.04.05/Status.htm" >ui.linksys.com/files/BEFSR41/v4/&middot;&middot;&middot;atus.htm</A><br>...and this example is DHCP (same as "get automatically").<br><br>The Linksys better be pulling an address and most the other data.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20463145</guid>
<pubDate>Sat, 10 May 2008 21:20:28 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20462345</link>
<description><![CDATA[<A HREF="/useremail/u/1550207"><b>MDEO</b></A> : First off, my thanks to all of you for the assistance/guidance.<br><br>Second, after following Bill_MI's guidance, I was still unable to gain Internet access.<br><br>My problem seems to be my antiquated B90 modem.  That's my layman's guess anyway.<br><br>Following Bill_MI's advice, my computer continued to recognize my LinkSYS router and send commands to the B90 modem.  However, the modem would not reciprocate.<br><br>Outbound input requests were successful (Desktop----> LinkSYS router ----> DSL modem... with each of these devices indicating the communications were being made/accepted (i.e. a linked chain of "blinking" green lights were observed by me)).  Yet, in monitoring my Desktop's Netgear FA311 LAN card, it was apparent no reciprocation (return communications) was coming from the modem/router.  I would attempt to access the Internet... and my page request would simply "time out".<br><br>I attempted PPPoE Router settings and that definitely did not work (Desktop wouldn't even recognize my Router).  My only progress was made while keeping my Router set to "obtain address automatically"... but that left me back at Day One.<br><br>Note:  I'm on the Left Coast in California, so my Verizon access is not PPPoE it is "obtain address automatically" (or so I am told anyway).<br><br>In any event, I'm quite overwhelmed with this having taken so much of my time (and that of other's) to deal with what I thought would be a relatively simple networking process.<br><br>I think I'm gonna forgo LinkSYS and obtain a Netgear router... I've read far too many Internet accounts from former LinkSYS/Verizon ISP users who claim they had success with Netgear routers (but not with LinkSYS ones).<br><br>I'll check back here and let you folks know what I find out (in way of Netgear vs LinkSYS and Verizon ISP).<br><br>Thanks again!   ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20462345</guid>
<pubDate>Sat, 10 May 2008 17:17:20 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20460801</link>
<description><![CDATA[<A HREF="/useremail/u/1423366"><b>dunworkin</b></A> : Check here for some info/help.<br>&raquo;<A HREF="http://help.expedient.com/broadband/" >help.expedient.com/broadband/</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20460801</guid>
<pubDate>Sat, 10 May 2008 09:44:47 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20460452</link>
<description><![CDATA[<A HREF="/useremail/u/1546846"><b>tenmachan123</b></A> : <div class="bquote"><small>said by  Bill_MI <A HREF="/useremail/u/277471"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>First, I feel your pain.  This isn't easy.  Here's some facts...<br><br>In what many call the BEST setup, modem in "bridge" and the router logging into DSL (WAN set PPPoE) getting to the modem page is not easy at all.  In fact, I'd hate to suggest it to anyone but the experienced.  The reason is: The router is tunneling PPPoE right through the bridged modem with no easy way to talk to it.  People prefer this because all their routing is handled in one place - the router (and the modem's routing doesn't interfere).<br><br>That is the basic problem... you have two things wanting to be routers - a modem with built-in router functions and a separate router. :-)<br><br>That said, here's what many do...<br><br>The router and modem must be on separate network "subnets".  Was that correct that you changed the router to 192.168.1.<b>2</b>?  That is not a separate subnet - it's a separate address in the same 192.168.1.x subnet.  If you meant 192.168.<b>2</b>.1 then that is a different subnet.<br><br>Modem all set to login to your DSL ISP like Verizon probably suggests.<br>Set the modem and router to separate subnets (router on 192.168.2.1 is fine).<br>Linksys WAN to 2100 Modem.<br>Set Linksys WAN to obtain address automatically.<br>All your PCs hook to the router LAN.<br><br>You should now be able to get to the modem AND internet.  Power cycle everything to be sure.<br><br>Hope this helps.  How close are you already to this configuration?<br><br>If it undoes a lot of what you were told, just holler and fill us in.<br><br>EDIT: I'm very familiar with the Westell 2100.  Turns out, in default configuration, it automatically is in bridge mode and router mode at the same time.  Westell calls it a "PPPoE shim" or something like that.  It's somewhat unique in the DSL modem world. :-)<br> </div>Bill_MI is correct. BEFSR41 should be set to 192.168.2.1 and its Internet/WAN connection type should be set to obtaib IP automatically.<br><br>But that depends on how you connect to the Internet when the computer is connected to the Westell modem. If you are entering a username and password from your ISP to connect to the Internet when the computer is connected to the modem, then the router needs to be set to PPPoE, if not, then just set it to obtain IP automatically.<br><br>If you will set the modem to Bridge mode only, then the router needs to be on PPPoE.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20460452</guid>
<pubDate>Sat, 10 May 2008 06:11:48 EDT</pubDate>
</item>

<item>
<title>Re: Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20458783</link>
<description><![CDATA[<A HREF="/useremail/u/277471"><b>Bill_MI</b></A> : First, I feel your pain.  This isn't easy.  Here's some facts...<br><br>In what many call the BEST setup, modem in "bridge" and the router logging into DSL (WAN set PPPoE) getting to the modem page is not easy at all.  In fact, I'd hate to suggest it to anyone but the experienced.  The reason is: The router is tunneling PPPoE right through the bridged modem with no easy way to talk to it.  People prefer this because all their routing is handled in one place - the router (and the modem's routing doesn't interfere).<br><br>That is the basic problem... you have two things wanting to be routers - a modem with built-in router functions and a separate router. :-)<br><br>That said, here's what many do...<br><br>The router and modem must be on separate network "subnets".  Was that correct that you changed the router to 192.168.1.<b>2</b>?  That is not a separate subnet - it's a separate address in the same 192.168.1.x subnet.  If you meant 192.168.<b>2</b>.1 then that is a different subnet.<br><br>Modem all set to login to your DSL ISP like Verizon probably suggests.<br>Set the modem and router to separate subnets (router on 192.168.2.1 is fine).<br>Linksys WAN to 2100 Modem.<br>Set Linksys WAN to obtain address automatically.<br>All your PCs hook to the router LAN.<br><br>You should now be able to get to the modem AND internet.  Power cycle everything to be sure.<br><br>Hope this helps.  How close are you already to this configuration?<br><br>If it undoes a lot of what you were told, just holler and fill us in.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20458783</guid>
<pubDate>Fri, 09 May 2008 19:32:14 EDT</pubDate>
</item>

<item>
<title>Westell 2100 Modem and a LinkSyS BEFSR41 Router:</title>
<link>http://www.dslreports.com/forum/remark,20454221</link>
<description><![CDATA[<A HREF="/useremail/u/1550207"><b>MDEO</b></A> : I'm a complete noob when it comes to networking... I'll start with that.<br><br>I've spent two days now trying to open an internet connection through my newly purchased LinkSyS BEFSR41 Router.<br><br>System Specs:<br>WinXP SP2<br>Westell Wirespeed B90-210015-04 Modem<br>Verizon DSL<br>BEFSR41 Router (4-Port)<br><br>I've done everything LinkSyS has asked of me, and followed every piece of self-help troubleshooting they have on their website... to no avail.  I have already changed my Router setting to 192.168.1.2 (to avoid the conflict with the modem's 192.168.1.1 setting and a known issue with LinkSyS Routers/Verizon ISP).<br><br>As of right now, I can access my Router's settings but can't get my WinXP SP2 Desktop to link to the internet.  My Netgear FA311 LAN card recognizes the Router connection as good... but there's no link between the Internetz and my computer.<br><br>I sit and watch as the Router/Modem communicate (via their mesmerizing flashing green lights) but the Router will stay in an endless "connecting" loop when I check its status (on it's setting page).  I have the current firmware for the Router/drives for the Netgear FA311.  I tried to update my Westell 2100 modem but it won't allow me to access it via my browser (so I can't update it's firmware).<br><br>I think my issue is I have to set my modem to "bridge" but I can't access its settings page.<br><br>Anyone here have a Westell 2100 modem successfully linked to the Internetz through a LinkSyS wired (preferably a BEFSR41 model) Router?<br><br>Or know what I can do to access my modem's setting page? (I've already reset it twice... which didn't work).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20454221</guid>
<pubDate>Thu, 08 May 2008 22:11:26 EDT</pubDate>
</item>

</channel>
</rss>
