Home› AMX User Forum› NetLinx Studio

Zoom ADSL Modem Experiences

TurnipTruckTurnipTruck Posts: 1,485
in NetLinx Studio
Anyone ever have trouble working with Zoom X3 ADSL Modems? I have been unable to get any ports forwarded through the darn thing.

Are there any recommended ADSL modems?

Comments

  • DHawthorneDHawthorne Posts: 4,584
    My only bad experience with ADSL modems was one that was on-demand only. It dropped the connection when no local machines were using it, and re-established it when something on the LAN wanted access to the WAN. So, in that case, port forwarding was completely useless. The system simply did not exist on the Internet unless someone on the LAN was using it. You can't forward to nothing ...

    You may be running into something similar.
  • Chip MoodyChip Moody Posts: 727
    Sounds like time to include a "tickle" request in the NetLinx code that does something mundane or useless on the internet at regular intervals...

    I wonder how frequently the IP changes on those?

    - Chip
  • DHawthorneDHawthorne Posts: 4,584
    Chip Moody wrote:
    Sounds like time to include a "tickle" request in the NetLinx code that does something mundane or useless on the internet at regular intervals...

    I wonder how frequently the IP changes on those?

    - Chip

    The one I worked with changed it's IP every time it went on line. It was a Verizon ADSL package, one of the cheaper slow ones. I didn't need remote access so badly that I felt justified in adding a stay-online feature, but my guess is they would have trapped it and charged the customer. It really was bargain-basement DSL, barely faster than dial-up ...

    Actually, now that I think about it, I did try that (was a while ago). The connection process took so long that IP_CLIENT_OPEN timed out before it was done, and my stay-online function was only firing every 15 minutes ... too infrequent to keep it running, apparently. That was when I decided it wasn't worth toying with any further.
  • gary_cumminsgary_cummins Posts: 52
    Turnip,

    I've had the exact problem you are describing with the zoom DSL modem. I was getting upset with Verizon because I thought they were blocking ports. I changed to a very cheap SpeedStream and was able to poke through on 1319.

    I'd say "Ditch It".
  • TurnipTruckTurnipTruck Posts: 1,485
    Thank you for your reply.

    Turns out that the modem was the issue.

    The modem was originally configured for a dynamic IP. I forwarded ports through THEN changed the configuration for the static IP later purchsed by the customer.

    According to Zoom: Due to a firmware bug, you must first configure the modem for static IP THEN do your port forwards.

    After defaulting the modem, then doing things in the "correct" order, it worked fine.

    I have had a few glitches with the modem since then as well.

    I will be "ditching" it as you advise.

    I may try running it as a bridge first and using an SMC router.
  • Chip MoodyChip Moody Posts: 727
    TurnipTruck wrote:
    may try running it as a bridge first and using an SMC router.


    Back BCM, (Before Cable Modem) I had Sprint DSL at my previous house. I had to do just what you said - set the modem up as a bridge and configure my Linksys router to handle the login - in order to get things working well.

    I don't know about Verizon, but I was really blown away by Sprint's support - they had .PDF walkthroughs on their website on how to re-configure the Zyxel modem as a bridge...

    - Chip

    P.S. Note of some interest/humor - I moved a few miles up the road from my old house. Sprint was able to let me keep the same phone number, but I was too far from their switch at the new location for DSL to work. I was annoyed at the time, but the 8-9 MBS/sec I get through the cable modem is pretty sweet compared to the 1.5MBS DSL had...
Sign In or Register to comment.