BEFVP41 Inconsistently Delivering IP Addresses

[pagreen]

I have a small network that uses the BEFVP41 as an internet router and for VPN. DHCP is turned on. Every now and then, however, people start to have problems connecting to the Internet. When I check the malfunctioning computers, it is clear that no IP address has been assigned by the BEFVP41 (it will have one of those automatic addresses, instead of one in the assigned range). I discovered that, by unplugging the power cord to the BEFVP41 and plugging it back in, it immediately starts serving up IP addresses and everything works. Obviously, there is something wrong with the unit's ability to perform DHCP services.

When I emailed Linksys, they suggested 1) do a hard reset on the router, and 2) if that doesn't work, reflash the firmware. I will try it, but, other than the unit being defective (which seems to be the most likely answer), could something else be causing this? The network includes a number of NT servers, Novell Netware servers, and individual computers running some variation of Windows 98/ME/XP. Before we got the Linksys router, DHCP was provided by one of the NT servers, and a second NT server with MS Proxy installed acted as the firewall. Although both computers are still on the network, DHCP services have been disabled on the one server, and the Proxy server has been disconnected from the Internet (it is still on the network to help remove any remaining Proxy clients).

Any suggestions are welcome. Thanks.

 

[bcastner]

There have been several reports similar to yours. In many cases upgrading the firmware seems to solve the problem, but not in all.

First, if you intend to return the router do so with the cross-shipping option. The RMA form:

https://ssl.linksys.com/rma1.aspcom/sharing/xp_ics/x.zip

Second, prior to doing the RMA request, you might try a newer version of the firmware. The latest available on the Linksys site, including their public FTP site, is 1.404. There have been quiet releases of 1.405, and 1.406; and I have seen mention of a release 1.407. Most of these releases were to handle problems with WAN renewal on cable systems, but I am told that 1.406 improves on LAN side DHCP problems. Here is a link to obtain the 1.406 release of the firmware:

http://www.dslreports.com/r0/downlo...1bf51823623ec20/BEFVP41_v1.40.6_0117_code.zip

You can e-mail Linksys Tech Support after this firmware upgrade if the problem persists. Tell them that you tried your current firmware version, 1.404 and 1.406.0117. They should send you anything they have that is more current.

Again, you cannot rule out completely a hardware issue, but I would explore a firmware change first. Note: in my experience removing all other connections but 1 from the router before flashing avoids a lot of problems, as does connecting with your NIC adapter set to 10-half duplex. I always do a hard reset of the router after a firmware change and reset my configuration. You hard reset the router by holding the reset pin until the red diag lite goes on, and then eventually off. Takes about 40 seconds. Unplug, wait 10 seconds and restore power. Then re-enter your settings. It is advisable to write your original settings down before the process begins.

Best wishes.

 

[pagreen]

I must say, I was not expecting much when I posted my question, but I thought I'd give it a shot anyway. I am glad I was wrong!

I just completed reflashing the firmware to 1.404 (although I had not yet read your note, I actually did use the procedure you suggested). I will try that to see if the problem recurs. If it fails again, I will try the 1.406 version, which, using your link, I just downloaded.

You might have thought that, if the newer firmware version contains a possible fix for my problem, Linksys' technical support might have mentioned something about it? Of course, one thing I have noticed about Linksys' technical support. Their use of the English language indicates that they are not native English speakers. It's not that their English is bad, it's just that their use of colloquialisms indicates that they are someplace else, like maybe Korea or Malaysia. I guess that's the power of the Internet. You can outsource your tech support to Asia, and the only way to tell is by the use of language.

Anyway, not only was I not aware of the updated firmware, I was also not aware that they provide cross-shipping for repairs. Very good to know. Thanks!

 

[bcastner]

Usually for firmware problems an e-mail gets handled in Irvine, California, USA. I do not bother with phone support anymore. Send them an e-mail and you might find a response with an even newer firmware release.

 

[markku]

Hi,

Try this firmware, it should solve your problem:

http://www.dslreports.com/forum/remark,7132365~root=equip,16~mode=flat

 

[pagreen]

For the moment, I want to see if the hard reset and reflashing with the latest posted firmware (1.40.4, December 2002) suggested by Linksys tech support does the trick. From what I read, although the later versions work, they have some drawbacks. If it fails, I will certainly upgrade.

It appears that the major bug fixed in the later version is the ability to connect to a dynamic IP. Since ours is static, this particular fix does not appear to be essential, particularly if it comes with drawbacks. Interestingly, when I first set the unit up to test, it was at my home on a cable modem with dynamic IP. It gave me no problems for the test period (of course, it was a much smaller network, the test only lasted for about 3 weeks, and I never even tried to set up the VPN).

 

[bcastner]

pagreen,

markku (posting above) knows the foibles of this particular router cold. If he advised me to upgrade the firmware, darn me if that would not be the first thing I did.

Let us know how it works out.

 

[pagreen]

Even though the unit had not crapped out since I last flashed it and gave it a hard reset (last week), I decided to go with the 1.41 firmware. So, I took it off the network and attached it directly to my handy (and trustworthy) sub-notebook computer, flashed it, gave it a hard reset, and re-entered all of the settings (by hand--I was not confident that restoring it from a file would have worked, since the firmware had changed). That was about 2 hours ago, and so far, so good. Performance seems fine (at least no one has complained), and I will check the VPN when I go home tonight.

Thanks to all.

 

[nobeta]

pagreen,
I was wondering how you made out with this as I am having the exact same problem with the BEFVP41 with Firmware Version:1.40.4, Nov 21 2002. It worked great for a couple of months, but the last couple of weeks users on the LAN have frequently been coming up with I.P Adress 0.0.0.0. (NT4.0) After we power cycle the router it starts dishing out I.P Addresses again. Is the 1.41 version still working out for you?

 

[pagreen]

Funny you should ask today. With the upgraded firmware, it worked fine--for about 3 weeks. Today, all of the sudden, it has reverted to form and stopped providing IP addresses. I unplugged it and it started working again. This makes me think it must be broken. Anyway, I sent an email to Linksys tech support asking for an exchange. Too bad. I thought the problem was licked.

 

[bcastner]

One possibility for both of you is to replace the power adapter.

Linksys will do this without cost, and without concern for the warranty status of the device. See the site below and select the second radio button for power adapter. You do not need to return the old one first:

https://ssl.linksys.com/rma1.asp

 

[hope2help]

If you can, I strongly recommend setting up a DHCP server that is more reliable and robust than what comes with linksys routers.

I have setup an NT DHCP server and now running W2k DHCP server and had always disabled the DHCP capability that comes with the linksys.

Hope that helps.

 

[pagreen]

Really? Is this a known problem? It certainly is easy enough to do, since the same NT server that previously provided DHCP services is still on the network.

 

[bcastner]

pagreen,

hope2help paints with a very broad brush. I likely see well over 100 postings a day about Linksys issues, and the DHCP one you mentioned is confined to nearly only the version of the router you have.

My own guess at this point is that an RMA exchange is indicated. Please save the firmware upgrades the marrku and I suggested above. The easiest return is through this web site:

https://ssl.linksys.com/rma1.asp

I am not criticizing the notion of providing local DHCP services through the server approach. I would be happier if we were discussing a Win2k server rather than NT. But, in the main hope2help's comment is too broad an indictment of DHCP services under Linksys to pass without comment.

A cross-ship return should take 2-3 business days, and you can use your router until the replacement arrives.

Best wishes.
Bill

 

[Shocker]

Pagreen,

I would agree with Hope2help's suggestion of using another DHCP server and disabling totally the router's DHCP. You could also flash the firmware of your router to the same 1.40.4 or you could ask from Linksys's Escalation Team for a beta version of 1.40.7 version of your firmware.

 

[bcastner]

I agree totally with markku's link to firmware 1.41 and its use.

There is a problem that requires an RMA return for this particular router.

I disagree, and said so earlier, that too broad a brush was painted against using Linksys DHCP services by their router products.

And the notion of implementing DHCP on a very small LAN under NT 4.0 relative to the Linksys service is more than arguable.