07-09-2012 09:41:48 AM
I picked up a refurb Netgear N600 (WNDR3400) wireless router. My plan was to shut off its DHCP, statically address it on the existing LAN with the backbone cat5 connected to a client NOT uplink port, and use it only as a wireless access point (WAP). I've done this same config successfully in other networks so I didn't expect any issues. Unfortunately, after fighting with it for 3 days, I've found it can't seem to handle making and maintaining wireless connections when a Uverse STB that is wired to a client port is on and streaming. Turn the STB off and wireless connections work as expected.
I also tried connecting the LAN backbone cat5 to the uplink port and creating a new subnet for the wired and wireless clients with rounting to the HGV. While that works great for normal wired and wireless, the STB stream experiences frequent freezes so I assume the STBs must be on the same subnet as the HGV.
I'm thinking an easy solution would be to connect the LAN backbone, N600, and STB to a cheap Hub/Switch this way the STB stream wound pass through the N600. That should work, right? Is there any way to do what I want without the extra h/w? I suppose I could get a new wireless STB. Do those cost more monthy than the wired ones? Would I have to also upgrade the HGV (a several year old 2-Wire device)? At my cost?
07-09-2012 10:04:58 AM - edited 07-09-2012 10:11:27 AM
See SomeJoe's post found in the link below:
Also, the STB should connect to the U-verse gateway not to your own router.
By the way, there is a one-time fee of $49 for a wireless STB. The monthly cost is the same as the wired STB. You will be provided with a WAP to connected to your current U-verse RG to be used to communicate with the wireless STB.