Tenda Router Not Working After Firmware Update
Gene Cryder
The router was cheap and I am getting something else. The router will work but it is wide open to anyone in the neighborhood and the getto people across the street have already logged in and are telling me they found a free internet connection.
Since the firmware is done, I suspect that everything has been reset. You may have to connect directly into the router, and use the address below (192.168.1.1). Are you the person that initially setup the router?
Treat the router as a new install.
Posted by manpildo (what?)
on Oct 12 at 9:04 AM Mark as helpful
Thank you all for answering, but none worked.
@Bill Davice - I chose the correct one (D1.0R)
Is there something else left to try?
Just another thought - link through to Tendnet site TRENDnet Error 404 - File or directory not found
There are 4 versions of update for this machine - Double-check that you dowloaded the second on the menu.
billd
Hi
Replying through this thread Manpildo - I was going to suggest something like that - have seen problems with other modem/routers after updates. Some like to be powered-up without the phone cable attached - let it get started then plug-in the phone.
Are you connecting through WiFi or RJ45 cable? It sometimes is better to restart with Ethernet cable connection and check settings via IE. Just a thought - sorry if it sounds too simple - are you resetting with the modem connected only to the power cord?
Billd
Everything was working fine and I decided to do the firmware update that I was told about via email from Netgear today. Everything went well except now I can turn on the wifi. I have tried every setting that I can find, rebooting, unplugging, etc. I need my wifi back!!!
Open CMD and ping the routers IP 198.162.1.1. If you do not get a responce this update killed your router. I also got that message, I also pdated my firmware we it was done it killed my router. Nothing I have tried let me gain acess to change the firmware back. If you do get a responce with a ping then u can get in to revert yuor firmware back to waht it was. If you get no responce from a ping its dead. I wont be buying anymore Netgear routers thats for sure.
Thank you, Michael. I'm glad that I didn't have the same problem that Mike did and as frustrated as I was, I am sure he feels even worse. No where in the directions did I see anything about doing a reset. If it's in there I missed it, if it's not in there perhaps it needs to be.
I was fortunately able to just power cycle the router after waiting long enough to know that the router wasn't going to correct itself with the firmware initiated reboot. After the power cycle, all functionality was restored and the firmware is shown as updated, so looks like I'm also in the clear, thanks!
The firmware update for my R6400 disabled my WiFi and I tried rebooting it with no success. I didn't even have the option to enable the SSID broadcast on the WiFi settings. I decided to change back to the previous Firmware Version (V1.0.1.24_1.0.18) and after it was installed and the router rebooted, everything worked. It was very frustrating to waste an hour and experience needless stress on a Friday. Here's the link to the R6700 firmware, if you want to try the same thing:
With the latest firmware update, version 1.0.9.34_10.2.36, the VPN option using openVPN is no longer working. It will show from my android that my VPN is connected to my VPN on my router, but it will not connect to anything on the internet. It appears that it is not routing any traffic. I am using the same settings that I always have been using with the only difference being the updated firmware.
was the firmware that changed MD5 to SHA256) I've done a file comparrision of all the certificates downloaded from the router from 1.0.9.32 and 1.0.9.34 and they are identical. So reloading the certs in OpenVPN would make no difference.
After my last firmware update here is what I had to do to get the VPN to work. Log in to the router and create new configuration package files. On you Android device uninstall the OpenVPN application and clear all data. Reinstall the OpenVPN application and import the new configuration package files you created after the new firmware was installed.
Although the VPN gets a successful connection to the R7000, all DNS lookups are failing rendering the VPN useless for internet access. It should be noted that the problem seems limited to the smartphone profiles. Windows clients are uneffected by this problem.
Depending in the router you are using, you might try disabling the 5GHz network to force your phone to connect to the 2.4Ghz. Another possible benefit might come from power cycling the router, leaving it unplugged for 30s.
Firmware flash in exFAT is not supported. While the cam can read from and write to exFAT AFTER the firmware has been successfully loaded, only FAT32 can be used for the Firmware Flash. That is why I posted to use a 32GB card because they come factory formatted FAT32.
I just wanted to let you know along with everyone else that after getting a 32GB SD Card I finally succeeded in flashing my Cam. I made sure that it was formatted as Fat32 before adding the firmware and that made all the difference. It is now updated to the latest firmware and working like a charm. Thank you very much for your assistance,
Yes, I had the same problem. I tried the update for all cameras. One update failed and then that camera would no longer connect to the network. If they are destroying their own cameras with their updates, they should give us new cameras.
It is more likely that during the OTA file download of the firmware to that specific cam, the network lost connectivity with the cam momentarily and packets were lost during the transfer. The quality of the firmware is moot if the cam never gets the full package due to network WiFi connectivity loss.
A factory reset deletes the settings file on the camera and rolls it back to the default settings. It can also be performed as a troubleshooting step for restoring a device to a previous working st...
No offense taken. Since I am nearing the end of my second full retirement, I often get frustrated with the youth and their new fangled social technology. I am one of those old school nerds though. But there is absolutely nothing wrong with a Zagnut Bar! Those things ROCK!
I'm trying to unpack and rebuild a Broadcom based router firmware image (for a Tenda RX3), using ubireader_*, ubinize and mkimage tools. It mostly works, but for some reason the router does not seem to accept the UBI image generated by ubinize.
I do not want to dash your hopes, but this looks like a Broadcom 802.11ax platform. You might be able to get OpenWrt going, but you'll never get wireless working. Broadcom simply does not offer any drivers for it that might work on OpenWrt.
Yeah, I'm well aware of that. I bought this Tenda RX3 mostly to experiment with hardware hacking. Maybe I will run things like a DNS server on it, but I have no intention to run it as my main wireless router.
The issue is not dependent on AirLink or VirtualDesktop. It's a clear communication issue between the Quest 3 and certain routers in Quest build vertion 57. That effects both 5Ghz and 6Ghz. Quest 2 is unaffected.
Our Wireless RD found that it might be the case Quest3 are kind Quest3's wireless connection rate strategy is more aggressive in terms of speed reduction. Once it encounters wireless packet loss or interference, it will reduce the negotiation rate on a large scale, thus affecting the actual wireless performance.
Also thanks a lot for your updates about that article, we will also notice to get the previous quest2 sample to check how it works with our router in old firmware, then upgrade it to newer one for checking.
Though with the new update to v.59 it is actually a lot better on AXE75 for both 5g and 6g. It's fluxing, but not below 1200 in 6g and not below 720 in 5g. Making it... "usable"... if you are relatively close to your router.
A lot of new posts here and in my community on still experiencing this issue making their wireless experience unbearable. The uptick has been noticeable since the release of SteamLink bringing more people over to PC wireless.
Meta Store Support following up on your issue.
To clarify, the issue you are experiencing is most likely to be patched up with a new software update. I know how inconvenient this may be for you. We really appreciate your extended patience and utmost understanding regarding this matter. As much as I would like to give you an exact timeline, since this is still a known issue, I'm afraid we are still unable to provide an exact date for it.
This is also for our customers, as we don't want to set you an expectation that is vague. We value transparency here at Meta, and we can assure you that we will quickly contact you as soon as possible once the issue is resolved or workarounds are provided.
We're eager to have this one sorted out for you, so we'll keep an eye on this issue. Looking forward to solve this issue at your earliest convenience so you can proceed enjoying your VR experience.
I can confirm that your issue regarding Wi-Fi connection has been coordinated with our engineering team; however, they didn't provide an exact time; maybe they are still figuring out the root cause of the issue. By the way, thank you for the clear explanation of your issue; that helps us a lot.
Hey everyone! I wanted to let you all know that I heard back from our engineering team. It looks like there might've been some changes with the recent v60 update. I recommend checking your headset to make sure that it is updated to the latest version, and then checking your Wi-Fi connection with your headset. If you're still having trouble after updating your headset, please let me know the below information and I'll pass it along to our engineering team so this can be looked into further.
64591212e2