NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Trek PR2000 DHCP-problems, keeps dropping connections, maybe workaround
Hi!
Some days ago I bought the new Netgear Trek PR2000 mobile wireless router. Purpose was to have an AP for all my devices while traveling and being able to connect them to a hotspot or hotel wifi.
Configuration was fine and I was able to connect to my home network in wireless client mode. My home router is a TP-Link TL-WR1043ND running OpenWrt 12.09 Attitude Adjustment, wifi with WPA2-AES, serving DHCP.
The Trek was able to connect and the whole system was running. Unfortunately I realized, that the Trek kept dropping connections every 3-5mins with the annoying Netgear genie popping up and trying to reestablish a connection. Sometimes it worked, later on the Trek failed to connect at all.
Since I read that OpenWrt Attitude Adjustment might be having problems with certain wifi connections, I upgraded my WR1043ND to Barrier Breaker. The connection drops continued, especially under OSX nearly every minute. The WR1043ND showed various DHCP- and wifi-failed-to-acknowledge-errors in its log.
After trying all possible setting changes in the Trek-config (and shortly before returning the Trek), I found something like a workaround. In the Trek-config I disabled the DHCP-Server for the LAN-zone and assigned static IPs to the connecting clients. Well at least until now this seems to be working fine. No more dropped connections, no more annoying genie popping up and trying to reconnect, the whole system seems to be working.
But at the moment I'm kinda confused about the reason. In my understanding, the Trek connects to a hotspot and gets an IP-address assigned by the hotspot-DHCP. Then the Trek uses NAT to connect the attached clients to the internet. Actually the DHCP-IP-addresses assigned by the Trek to the clients connected to the LAN-zone shouldn't affect the DHCP-settings of the hotspot-network at all. Normally the private IP and DNS-settings are just for the private client LAN, aren't they? If I'm not completely wrong with my assumption, there might be a bug in the DHCP-server of the Trek or the way how dynamic IPs of the client LAN are handled. Starting from the point where I changed to static IPs in the client LAN, there were no more error messages in the log of the WR1043ND.
Strange thing... Maybe someone could correct me if my assumptions are wrong? Btw, I'm using the Trek PR2000 stock firmware (which is something like 1.0.0.9) since there's no other available.
Thanks.
Some days ago I bought the new Netgear Trek PR2000 mobile wireless router. Purpose was to have an AP for all my devices while traveling and being able to connect them to a hotspot or hotel wifi.
Configuration was fine and I was able to connect to my home network in wireless client mode. My home router is a TP-Link TL-WR1043ND running OpenWrt 12.09 Attitude Adjustment, wifi with WPA2-AES, serving DHCP.
The Trek was able to connect and the whole system was running. Unfortunately I realized, that the Trek kept dropping connections every 3-5mins with the annoying Netgear genie popping up and trying to reestablish a connection. Sometimes it worked, later on the Trek failed to connect at all.
Since I read that OpenWrt Attitude Adjustment might be having problems with certain wifi connections, I upgraded my WR1043ND to Barrier Breaker. The connection drops continued, especially under OSX nearly every minute. The WR1043ND showed various DHCP- and wifi-failed-to-acknowledge-errors in its log.
After trying all possible setting changes in the Trek-config (and shortly before returning the Trek), I found something like a workaround. In the Trek-config I disabled the DHCP-Server for the LAN-zone and assigned static IPs to the connecting clients. Well at least until now this seems to be working fine. No more dropped connections, no more annoying genie popping up and trying to reconnect, the whole system seems to be working.
But at the moment I'm kinda confused about the reason. In my understanding, the Trek connects to a hotspot and gets an IP-address assigned by the hotspot-DHCP. Then the Trek uses NAT to connect the attached clients to the internet. Actually the DHCP-IP-addresses assigned by the Trek to the clients connected to the LAN-zone shouldn't affect the DHCP-settings of the hotspot-network at all. Normally the private IP and DNS-settings are just for the private client LAN, aren't they? If I'm not completely wrong with my assumption, there might be a bug in the DHCP-server of the Trek or the way how dynamic IPs of the client LAN are handled. Starting from the point where I changed to static IPs in the client LAN, there were no more error messages in the log of the WR1043ND.
Strange thing... Maybe someone could correct me if my assumptions are wrong? Btw, I'm using the Trek PR2000 stock firmware (which is something like 1.0.0.9) since there's no other available.
Thanks.
hksteve I would like to inform you that the fix is now available in our download page.
Feel free to update your firmware and provide feedback.
Thanks!
185 Replies
- Same problem of disconections very frequent. Testing conection and disconection of an electrical thing (a heater was used for this test, only resistive but 2kW of power) near the PR2000 Trek: the problem was systematically reproduced.
In fact, the problem is well given by an electrical power sensibility.
I've plugged the trek with the USB cord plugged to a phone adapter. No more disconnections, problem resolved.Hi,
i bought a PR2000 in March to use when travelling.
i seem to be experiencing issues with wifi drop out too. It can work for couple days then have constant drop outs.
i have unchecked DHCP server in LAN settings and created IP reservations for my devices and set the rip to in only.
i am on firmware v1.0.0.14_1.0.1 which was on when purchased so this might not be the latest firmware. Is it worth updating to latest firmware first ?
i am also using in 4 way adaptor but then tried in a wall plug but still got same issue.
any assistance appreciated as it's becoming to be useless and I might aswell take an old house router with me on travels
You appear to have the latest firmware. What mode are you operating the PR2000 in? Is it operating as a repeater and if so what is it connecting to, what are the wireless settings? Do you have other wireless networks in the area, and if so do you know if the PR2000 / base AP are automatically changing wireless channel, or is the wireless channel fixed?
I'm also having the same issues / similar issues. When I'm traveling, I'm using the Beaglebone Black (connected via ethernet) and it'll compelty drop out of the network, and need to be rebooted to reconnect. I've confirmed that it only happens on the netgear, and not the home linksys network.
Two different hotels with similar issues
Curious on the beta firmware also, otherwise, this goes back to Amazon as well.
I'm needing to use the device as three separate configs, as a wireless extender/bridge at home (with two devices attached), a wireless/wireless router on travel, and a standalone wireless access point (with two devices attached) on a portable setup.
Wow can't believe this router doesn't work. I'm trying to connect to my XfinityWifi hotspot. It connects but its sooooooo slow that its unusable. Tried everything (and they don't leave many settings for us to play with).
Works fine on the local network with the NAS I just bought.
I bought this because I needed the LAN port for the NAS.
I was using the amazing HooToo Tripmate Nano. It works awesome, especially for this AP hotspot mapping (hotels, Xfinity WifiHotSpot). Has a great USB "nas". The web-page interface is instantaneous fast. Runs off almost no power from a USB port. Almost matchbook sized.
This Trek is 4X as big and doesn't work for what I want.
Netgear folks, just go buy a HooToo and copy it exactly, then add on the LAN port.
Hoping this gets fixed quick or it's going back to Amazon and I'll just grab one of those TP-nano's. Sadly, it doesn't have a USB "nas" so then I'll have to carry two routers. The hope with this one was to only have one. But the Tp-nano and the Tripmate nano will be smaller than the Trek anyway.
If this issue isn't resolved by Nov. 11th, both of the Treks I have now will be going back to Amazon, and I will ask for a full refund. This device is erratic at best. I've worked in Information Technology for nearly 30 years, and I have rarely come across a networking device as unstable as this one.
Amazon should be made aware that the PR2000 Trek devices they are selling are defective, and buyers have little hope of having issues resolved.
I too am having horrible disconnect problems. I am on version V1.0.0.14_1.0.1 - is the bet available to download? Or does anyone know when it will be available?
I just realized what was happening with my Trek after reading this thread. Any chance I can get a test/beta firmware to try out? Here's my application:
I have a fleet of wireless temperature sensors that report via WiFi, and I want to use them with this router. The way these sensors work is that they connect once per minute and send their data, then disconnect. I was confused as to why the router would keep rebooting when I had devices pointing to it, but remain on when nothing was connected - this issue is obviouly the disconnections causing a reboot.
I'd like to deploy these sensors soon, so getting all these routers I bought working is a priority. Alternatively, if anyone can suggest a similar router that is able to to DHCP, that would be ideal. The TP-Link models don't do that, so I can't use them.
Hi HaxNobody
Kindly PM me your network setup and description of the problem as to when it happens.
What's the current mode you're using with the PR2000?
Is it Wired or Wireless? This is the toggle switch available on the side of the router.
Also, what is the brand/model of that sensor devices you have?
Let me know and I'll verify with our engineering department if the test firmware is applicable to you.
Registered to this forum to say I am experiencing the same disconnecting issue. I connect the Netgear PR2000 Trek to another WiFi network, and allow the Trek to create its own SSID. I then connect my devices (laptop, iPhone, Blackberry, iOS and android tablets) to Trek's SSID. Whenever one device sleeps or disconnects, the Trek reboots. This behavior is consistent, every time, everyday.
If there is a Beta that may resolve this issue, please forward a copy to me. Thanks.
In response to Netgear support urging the closing of my case, I replied with the following:
"It is up to you whether or not you close this case without resolution. There are plenty of other users that are dissatisfied with the lack of functionality of this product. I have returned one device to Amazon for an exchange, and will be sending the other back requesting a refund. $40 may not seem much to you guys, but it is a lot to me. I had to have a functional device for my $40, so I purchased a router/extender with a LAN port from another vendor. It works without a hitch.
I have spent nearly 30 years in Information Technology, and I cannot fathom delivery of a product such as the Trek PR2000. To make it worse, the first reports of failure were posted many months ago, and the issue still remains unsolved by your technical staff. If I am a manager at Netgear, I would be looking for new staff. Selling a defective product on a popular storefront like Amazon, and then providing sub-par technical support, cannot be welcomed by your marketing department either.
If your agenda is to close cases, then certainly do so, but if your agenda is to solve problems, then let this case remain open until the issue is resolved.”
- Elaine
Please can I get hold of the beta software. I would have hoped that it might have been released by now but having upgraded to v14 I am still getting these frustrating issues with the connection being dropped very frequently. It seems to have become much worse after adding an Android phone to the network a couple of weeks ago. Hi. Same problem here. It worked fine (sort of) for couple month. but now signal drop out are 3-10 times a day or more. Funny enought I lost signal reading this toppic .... no, its wasnt funny....
so. I using apple macbook pro and samsung galaxy s6. Noticed that if I loose signal on one device its stay on other and vice verca. (but not always - might lost signal on both devices) and than when turn off wifi on apple and turn back on signal is back for both devices - for a while and afrer that its start over again.
- Afer latest upgraded my poblem is gone. Work ok. Not sure for how long :D
- The beta firmware? Or there is a new official final firmware?
