dsecrest_1

Q: New Uverse modem drops Time Capsule once a day

I think I have a similar issue as MaxKaladin had about 9-10 months ago, but i can't seem to figure out how to solve the issue in my environment.  I have an Apple Time Capsule 802.11 ac and have it directly connected with my Uverse modem.  The TC is set in bridge mode.  Furthermore, i have an airport express connected directly to the TC via one of the 3 LAN ports (to facilitate wifi in a distant part of the house) and this AE is also set for bridge mode.  I've set both TC and AE to static ip addresses 0f 192.168.1.200 & .210 (TC and AE, respectively).  Once I establish connection with the Uverse modem (with all wifi services disabled), everything seems to work great.....for a period of time.  Typically, around the 22-24th hour of connectivity, my TC loses broadband connection with the Uverse modem and all my wireless clients are then dead in the water.  Upon a restart of the TC, all is well for the next 22-24hrs.  Obviously, nobody wants to live like this!  I haven't set my Uverse modem to a static ip as MaxKaladin suggested he did, partially bc I'm not exactly sure how.  If that seems to be the recommended simple solution, i'll get the right person to help me with the Uverse modem (apologies, but I'm not truly tech savvy).  Any other suggestions that a novice might try to solve my issue.

 

For the record, Bob Timmons helped me probably 2-3 years ago with my wireless home environment and it had worked great since.  Its only the introduction of this new Uverse modem (which apparently is so much better) that I've had the problem.  And, of course, the Uverse technical support is practically useless until you manage to get 3-4 tiers up into the help call tree (which i haven't had the time or patience to attempt yet).  Kindly appreciate any response.

 

~ds

 

I also set the DCHP Lease time to 72hr from 24, which might help me triangulate my issue if I'm able to stay connected for almost 72hrs rather than almost 24hrs.

Posted on Sep 14, 2016 4:52 PM

Close

Q: New Uverse modem drops Time Capsule once a day

  • All replies
  • Helpful answers

  • by LaPastenague,

    LaPastenague LaPastenague Sep 14, 2016 5:44 PM in response to dsecrest_1
    Level 9 (52,541 points)
    Wireless
    Sep 14, 2016 5:44 PM in response to dsecrest_1

    TC has indeed shown various issues with its WAN port.. these often show up after some considerable time or with a major network change.

     

    It might seem odd but a factory reset is still a worthwhile exercise.. you would think in bridge it would not matter but it can help at times.

     

    The other one is to plug the uverse into a LAN port of the TC instead of WAN. This is the first thing I would try. In bridge mode there is no WAN port.. Apple set WAN to LAN.. but with the LAN ports being more reliable it is well worth a try.

     

    If both of those fail I recommend another factory reset and setup static IP with DHCP on the TC.

     

    I've set both TC and AE to static ip addresses 0f 192.168.1.200 & .210 (TC and AE, respectively).

    This is good.. but the next step is to let the TC take over as DHCP server.

     

    The setup means you need to login to the uverse and set a more limited range to the dhcp if it goes higher than 200.

     

    Let me also say it is well worth setting a reservation for DHCP in the uverse for the TC as well as setting a static IP on the TC. That ensures the uverse has the best hope of finding things.

     

    I have already posted my setup of this.

     

    I use a different IP range.. 192.168.2.x but otherwise it will look pretty much exactly like this.

    I would say it is worthwhile setting your DNS servers to whatever works best.. google public or your ISP.. do not use the uverse IP.

    Screen Shot 2016-09-15 at 10.37.19 AM.png

     

    Here is the network tab.

     

    Screen Shot 2016-09-15 at 10.37.36 AM.png

     

    So from my IP of 201.. I use 202-225 but you can set whatever you like up to 254.

     

    I also use a very short lease time.. This has nothing to do with the lease on the Uverse.

     

    Screen Shot 2016-09-15 at 10.37.48 AM.png

     

    I have found this works great.. but it is different in one respect.. here the wan port is active.. albeit the TC is NOT routing.. so the link to the uverse must be WAN TC to LAN uverse.

     

    For bridge remember I recommend LAN TC to LAN uverse.

     

    Once you configure the TC the AE should also go back to factory setting.. and this should be bridged.. remember the Express must create a wireless network not extend wireless.. that will cause problems.. for roaming it is setup same SSID (wireless name) and same password as the TC.

     

    Good luck.