The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

Networking (with Uverse) issues

Alright, here is my setup and goal.


My main Uverse Router is in our office room. There is a ethernet cable running from the office room to the living room connecting a set-top box for T.V. service. I am now adding a second router in the living room and have removed the ethernet cord once connected to the Uverse set-top box into the router (WAN interface).

There are several advantages to this setup. With this new setup, I should be able to connect my T.V. and accessories (Blue-Ray Player) hard-wired into the second router instead of relying on the wireless connection, for a stronger link. Also, now I should have a stronger wireless signal for the living room via the second wireless router.

Problem is, after everything is setup and (should've been) good to go, everything worked as planned - the stronger wireless signal (for the living room) is up and running, and all wired devices are up and running ... except for the Uverse set-top box.

Thoughts?
(Assume that all basic troubleshooting steps have already been taken [ex: rebooting the Uverse router, rebooting the second router, etc], as I have done everything in my limited-power to try and resolve this.)

Posts

  • WaterfallSandSunWaterfallSandSun Registered User regular
    Never mind. I just hit the (hopefully) easy-button and ordered a switch.

  • MushroomStickMushroomStick Registered User regular
    I don't think you can have have secondary routers/switches daisy chained in front of the set top with uverse.

  • MichaelLCMichaelLC In what furnace was thy brain? ChicagoRegistered User regular
    Yeah, I assume it would need to be the first point so it can negotiate the security and routing. Just guessing, based on your results.

  • DrFrylockDrFrylock Registered User regular
    Actually it may be possible if you turn off NAT and DHCP on the second router. In this case, the wired ports should act like a switch. I think the wireless should still work and pass DHCP requests to the Uverse Residential Gateway.

  • WaterfallSandSunWaterfallSandSun Registered User regular
    DrFrylock wrote: »
    Actually it may be possible if you turn off NAT and DHCP on the second router. In this case, the wired ports should act like a switch. I think the wireless should still work and pass DHCP requests to the Uverse Residential Gateway.

    Already done and failed.

  • Great ScottGreat Scott King of Wishful Thinking Paragon City, RIRegistered User regular
    I sounds like some port/service is getting blocked. For all I know about Uverse (nothing), it's possible that the set top box isn't even using IP.

    What you might want to try finding the IP address of the Uverse box and make it the "DMZ Host". This is called different things depending on your firewall but the idea is to let all traffic through and ignore firewall rules.

    I'm unique. Just like everyone else.
  • HaukyHauky Registered User regular
    I recently got Uverse installed as well, and have a similar setup to yours, save that my settop box is connected via coax instead of ethernet. I had a ton of problems with the modem's built in router conflicting with my Linksys router, even after I disabled all the NAT and DHCP stuff on the modem, until I set my Linksys to use/assign a 192.168.2.x address range. You might try setting one of your two routing devices to use that range instead of 192.168.1.x - I think you could pick either one, although it's possible that Uverse equipment might be hardcoded to expect .1.x IPs. I was just happy enough to get it to work that I never bothered experimenting further with that.

    For what it's worth, these are notes I wrote myself on how to configure the Uverse modem to just be a modem goddammit, in case a firmware upgrade wipes my settings out or something. Might be useful if you can make sense of them. I have DD-WRT installed on my router, so if you don't have that, I'm not sure how to change your IP range.
    - Connect to gateway
    - Settings, System Info, Event Notifications
    Enable router behind router detection
    - Attempt to browse to any site. It should prompt you to resolve a router behind router situation.
    Select Resolve
    - If it doesn't, reboot the gateway and then try to browse to a site

    - Reboot router to grab the public IP
    - Connect to router
    - Change Local IP to 192.168.2.1 and allow a few seconds for it to take effect
    - Release and renew computer's IP


    RBR detection: http://192.168.1.254/xslt?PAGE=C_0_3
    Reboot gateway: http://192.168.1.254/xslt?PAGE=C_5_7

    bobross.png
  • WaterfallSandSunWaterfallSandSun Registered User regular
    Thanks for the input guys. I will soon try manually splitting the ethernet cable with two RJ-45 connections on each end to fully utilize the cable run, and give a direct connection for both the set-top box and the second router - but the problem is that it would effectively limit the connection speed to 100mbps (gigabit connections require all 4 pairs), which should hopefully be ok since I heard that neither the set-top box nor the RG even supports gigabit connections. Just waiting for the connectors to arrive.

Sign In or Register to comment.