NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

floriann's avatar
floriann
Aspirant
Apr 27, 2014
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...
  • ElaineM's avatar
    ElaineM
    Mar 22, 2016

    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!

ElaineM's avatar
ElaineM
NETGEAR Employee Retired
Mar 01, 2016

Hello @n1ktung Do you experience the same problem? Can you describe the problem you're having?

What are the devices you have on your network?

n1k1tung's avatar
n1k1tung
Aspirant
Mar 01, 2016

Sure ElaineM

 

My setup is as follows:

 

PR2000 is connected via LAN to my modem(router). A PC is connected to PR2000 via LAN and works fine (there're no hiccups with Internet caused by PR2000, or they are very rare to bother me).

A couple of devices (1-3) are connected to PR2000 via WiFi. I use the PR2000 to cover a blind spot for the WiFi from my router and also to reduces the simultaneous connections count.

 

 

My experience:

 

At first, I've noticed my devices connected to the PR2000 via WiFi would lose connection to the Internet w/o dropping WiFi connection. I've updated firmware to the latest, the problem still occurs, and also devices would occasionally lose WiFi connection altogether (and switch to the router WiFi with low signal strength). Before upgrading the firmware I could just restart WiFi on a device to force it reconnect to PR2000 and it worked for a while. So currently the situation is even worse and also seems to be happening sooner than before (e.g. 5 min after device was first connected to PR2000 I'm safe to assume that it doesn't have Internet anymore - that's basically unusable). I've tried tweaking WiFi settings, turning DHCP off and setting IPs manually - nothing helps.

 

 

Regards

  • ElaineM's avatar
    ElaineM
    NETGEAR Employee Retired
    Mar 01, 2016

    -kd- It is always recommended to use hardwired connection to avoid firmware corruption in case your wireless gets disconnected.

     

    n1k1tung Thank you for the description.

     

    I have both forwarded you to support. They'll be in contact with you shortly.

  • -kd-'s avatar
    -kd-
    Aspirant
    Mar 05, 2016

    ElaineM 

    Looks that the Beta Version (v1.0.0.15_1.0.1) fixed it.

     

    i did the Update with my IPad only with WiFi and crossing fingers, because other way in the hotel was not possible.

     

    So let's look that you make this Version public to get less frustrated user.

     

    Thanks for your Help.

    -kd-

     

  • BARNES's avatar
    BARNES
    Apprentice
    Mar 05, 2016

     

    Same here, no disconnects in Hot Spot mode. Though speeds are not good, however I'm aware it's a beta... Also noticed port 23 is open (Could be in debug mode? - again beta).

    I concer, Netgear should link this as an open beta it you need Hot Spot mode and who doesn't when traveling.

    Oh my, I would love to see DD-WRT or OpenWRT on this sucker!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

     

    Curently have four devices connected for the last 18 hours... One is my wifes, and she loves playing those casio's games on the weekend, and she hasn't said anything about connection issues! <- that there is probably the best test I have for evaluating routers lol

     

  • -kd-'s avatar
    -kd-
    Aspirant
    Mar 06, 2016
    BARNES schrieb:

     

    Same here, no disconnects in Hot Spot mode. Though speeds are not good, however I'm aware it's a beta... Also noticed port 23 is open (Could be in debug mode? - again beta).

    I concer, Netgear should link this as an open beta it you need Hot Spot mode and who doesn't when traveling.

     

    So Telnet is open. Not the best idea.

     

    Did you check, that Telnet was closed in the regular Firmware?

     

     

  • BARNES's avatar
    BARNES
    Apprentice
    Mar 06, 2016

     

    Appears to be open only on the LAN side, not getting a telnet handshake on the WAN side. In fact, it's responding to my scans as a DDos. Tried connecting with Juice on the inside buts it's not responding to my telnet request.

    Never tested with .14 which the unit was shipped with...Though I did put the regular .14 in Debug mode, which should reset as soon as the unit was unpowered...Did NOT put the beta in debug mode.

     

    Here's the results on my port scan on the LAN side...

    Open Ports: 23, 53, 80, 20005, 33344, 5000, 7777, 8443 (Have remote admin on), 56688...

    Nothing returning on the WAN side...

     

     

  • ElaineM's avatar
    ElaineM
    NETGEAR Employee Retired
    Mar 07, 2016

    Port 23 is open on the LAN side designed for our telnetable tool.

    Glad to hear that the firmware helped solved your concerns.

  • BARNES's avatar
    BARNES
    Apprentice
    Mar 07, 2016

    Indeed it has, and thank you again Elaine for the help...

     

    To those having the reboot issue with the PR2000 Trek, should contact support ASAP and get that Beta .15 firmware! Mine has been running flawless all weekend, aside from a little performance tuning needed, offers a really good compromise with size. Those who expect dual core AC performance don't fully understand what compromise means even though everything in our lives is a compromise. They had a saying when it came to engineering; Speed, Cost, Quality - Pick two...

    Peace out...