04-27-2013 01:32:02 PM
I think I may have been trying to do too many things at once. I ran through the whole thing again very carefully and it worked this time. Was gonna come back and delete my post but you beat me to it
Thanks for the info.
05-09-2013 02:27:39 PM
I have read 98% of this thread, but can't find a solution to my problem. Or else I'm just blinded and can't see it. Anyway, I have very simple problem:
Originally, our small office system consisted of a Netgear DGND3300-V2 base station router connected to ATT DSL Internet in an office in one building (bldg #1). We had 2 ethernet devices connected to that router plus some wireless devices. In another buidling (bldg #2), we had a Netgear WNR2000-V2 running as a repeater, because wireless access to the RG in that building was insufficient. The NR2000 repeater connected with the base station wirelessly - there is no direct connection between the two. We have a couple computers in bldg #2 connected to the repeater wirelessly and a couple ethernet devices connected to that unit in the same bldg. We used different SSID's for each router. WEP security was used.
The base address of the RG was 192.168.0.1, with DHCP using the range 192.168.0.100-254. The Repeater's address was manually set at 192.168.0.30. All computers could be set to access the internet or each other's file.All this worked flawlessly until the secretary upgraded to ATT U--Verse and they installed a 2-Wire 3800HGV RG blindly without my knowledge and without regard to any other devices that might be on the network. Obviously, everything came to a screeching halt and since I was in the hospital having surgery, a nightmare ensued!
Anyway, very simply, I want to get the 2-Wire RG to work in the same fashion as the original base station router set up, but keeping the Netgear WNR-2000 repeater. This is almost identical to Joe's original post on this thread, with the exception that the routers do NOT have a direct connection with each other (just wirelessly). We can change all IP addresses to whatever the recommendation turns out to be.
Can you help?
05-11-2013 02:53:11 PM
This should be possible by performing the steps in post 2 of this thread on the NetGear DGND3300 base station router.
Basically, work from the new U-Verse 2Wire RG backwards. Perform the DMZPlus setup as in post 2, verify that wired Ethernet on the DGND3300 works. Then verify that wireless on the DGND330 works. Then verify that the NR2000 repeater is connecting properly to the DGND3300, then finally verify that wired and wireless clients on the NR2000 can reach the Internet.
05-12-2013 11:23:32 AM
Hello Joe, I'm following your instruction in post #2 to set up my Linksys E2000, but the RG doesn't see my router, and won't issue it an IP Address via DHCP. I had it set up and working perfectly on a previous RG that was replaced by AT&T due to hardware failure, and had the same problem originally, I just can't remember for the life of me what I had to change to get it connected the first time.
Any help is much appreciated!
05-14-2013 10:06:47 AM
Hey there Joe,
Are you saying that AT&T continues to ignore this issue?
IMO, AT&T does continue to ignore this whole issue BTW.
My reasoning; when setting up my Uverse package (very recently) the tech ignored my Apple Extreme router
(which had been working without flaw with my DSL IPS) and setup the RG for/with the Uverse system and things have NOT been the same since.
As for your (above my pay grade) procedure to get my internet on line without having to re-boot every time (what?).
I freely admit, I'm not the sharpest knife in the box when dealing with someting that was reputed to be included in the Uverse (ISP) package, which was (IMO) a VERY big selling point for this product.
BOTTOM LINE: if this issue has a solution (and you note that it does), why are not the installion crew's dealing with this when coming through my door?
NOTE; Once things get on line, other than manually having to access the net, I have NO other issues..
05-14-2013 08:14:21 PM
You may have to reset your Linksys E2000 to factory defaults. It might be remembering the old RG.
05-15-2013 06:48:51 PM
Thanks for getting back, Joe. I reset my E2000, but still experiencing the same results. It won't grab an IP Address from the RG and doesn't show up anywhere in the LAN settings of the RG, I've tried multiple 192.168.1.xx and 192.168.2.xx LAN configurations on my Linksys but the results don't change. Wierd thing is, I can see packets being sent and received on the RG port that my linksys is plugged into. Thinking about factory resetting the RG, but I'm not sure of the ramifications of that.
05-15-2013 08:04:04 PM
05-16-2013 05:39:05 PM
I confirmed all that again, Joe. I'm beginning to wonder if it's time to upgrade. Any last ditch troubleshooting steps before I retire the E2000? In any event, I appreciate you taking the time to reply.
05-16-2013 06:50:49 PM
05-19-2013 02:56:17 PM - edited 05-19-2013 02:59:21 PM
Joe, thanks for your insight and advice. I purchased the Netgear R6300 today and while trying to configure ran into the same issue. It didn't exist according to the RG. The only cable I hadn't verified was the ethernet jumper going from the RG to the horizontal cable coming from my router becuase I watched the ATT technician take it out of the bag and install it for me. Yeah, it was bad, I replaced that cable and everything came to life, which means most likely my Linksys E2000 is just fine, however I like the manual configuration and GUI interface so much better with the Netgear I'll probably just keep it. Thanks again, sorry to take up your time with a bad cable issue, but I thought I had ruled out all the easy stuff before I posted. Geesh.
I do have one last question though, we signed up for 18 Mgb internet and the 2wire speed test says we're averaging 2.5 Mgb download speeds- any thoughts on that?
05-19-2013 05:43:09 PM
Remember on the download issue that U-Verse advertised speeds are shown in megaBITS per second (i.e. 18 Mbps), while WIndows shows file download speeds in megaBYTES per second (i.e. 2.5 MBps). There is a factor of 8 difference between the two.
Go to speedtest.net and do a speed test, and make sure to do it from a wired computer. Speedtest.net reports speeds in megaBITS, to match what the advertised speed is rated at. See what it shows.
05-20-2013 08:13:11 AM
AT&T should fire all of their foreign national Tech Reps and hire you and many clones of you to quickly and efficiently address basic concerns like setting up parental controls on a Uverse internet account. I ask, why do we have to purchase a second router, go through all of the technical genuflections to bridge to the routers,just to achieve a very basic and fundamental requirement of establishing internet service at home? Even businesses lock down their internet access to avoid security breaches and internet abuse. If this is what it takes, the short answer to my question is jettison the Uverse router completely and just follow the KISS principle.
I wish someone at AT&T Executive Management would read some of these painful threads.
05-21-2013 08:21:25 AM
05-30-2013 10:05:47 PM
Ok, SomeJoe. I've read about 2/3rds of this thread and I can't seem to find out where I'm going wrong. I've got an ASUS wireless router I'm trying to do this with. I do everything you posted then I run an ethernet cable to the main STB and I get about 30 seconds of tv then it just stops. I change the channel and I get the same thing. About 30 seconds of feed then it turns into a still. I'm hoping you can help me with this before I send this router through the window
I'm not as well versed in networking but there's quite a bit of settings to tweak on this router so I'm sure there's a fix if you can point me to it. Thanks in advance.
05-31-2013 02:31:02 PM
Unfortunately, setting up your own router as directed in this thread will only work for computers and other Internet devices. It will not work for the TV boxes -- those must be connected directly to the RG.
The TV boxes receive the IPTV signal using a combination of unicast and multicast packets. When you first tune to a channel, the stream is unicast. After about 20-30 seconds, the TV box joins the multicast stream seamlessly.
However, consumer routers (and even most professional routers) are not set up to route multicast traffic, nor can your Asus be configured to do so. So what happens is that the STB begins displaying the channel, but the channel freezes as soon as the box attempts to shift to the multicast stream, because the multicast stream won't go through your Asus.
You will have to either run an Ethernet cable separately for the TV box, or if the wiring is such that only the computer network (off your Asus) is coming to the TV box's location, you can also solve this problem with VLANs, but you will have to purchase at least 2 VLAN-capable switches (least expensive models that will work with U-Verse are $70-$90 each).
06-01-2013 10:24:32 PM - edited 06-01-2013 10:33:14 PM
Joe, thanks for the great instructions. I purchased a new wireless router (TP-LINK TL-WDR3500 Wireless N600 Dual Band) to get better signal and speed in my house with 5 PCs on LAN and a few devices on wifi. It does actually work very well even in areas of my house that the 2Wire barely reached. Initially I followed your post 13 only using the wireless features of the TP-Link. I had one issue with wireless dropping out once in a while on the 2.4GHz while the 5GHz kept working nonestop. Couldn't figure out the problem and went as far as resetting both the 2Wire router and the TP-Link. It wasn't too bad and every other day or so I had to reboot the TP-Link to get the 2.4GHz working again.
I then decided to follow your instructions from post 2. I got everything working after I gave the TP-Link a static IP. No more issues with wireless dropping (knock on wood). It's nice to have everything under one router and bypassing the 2Wire. I have one issue remaining and I am hoping you may have an answer. I have a Server 2012 Essentials running for backups and media streaming. The client PCs have been deployed with skipping domain setup (trick found at Paul Thurrot's site). Almost everything works between clients and server (backup, media, shared folders, dashboard), except "Anywhere Access" (remote web access) which allows the connection to the server and its clients from "anywhere" via a domain name.
The server is directly hooked up to the TP-Link and uses the same IP range as everything else. Remote Access worked fine when everything was running through the 2Wire alone. When I try to set this up with the TP-Link behind the 2Wire I get an error that the server is blocked. The wizard set port forwarding on the TP-Link router correctly (443 and 80) for this to work and I see the entries. The wizard is smart enough to suggest that there is more than one router on the LAN and that they may not be working together properly.
It seems that even though the correct ports are forwarded somehow the 2Wire prevents this from working. The server wizard lists the correct server IP address and the TP-Link as default gateway.
enough rambling. any hints are appreciated.
06-02-2013 08:50:42 AM
If the TP-Link is the DMZPlus device, then normally, nothing in the 2Wire would prevent inbound connections on port 443. Check your TP-Link configuration carefully.
There is one item you need to be aware of: If you have wireless STBs, the wireless access point that is used for the wireless STBs takes port 443 away from you, and nothing can be done about it. The only work-around if this applies to you is to purchase a block of static IP addresses and set up one of them as the DMZPlus device.
06-02-2013 10:09:13 AM
thanks Joe, it worked fine with just the 2Wire router and I do not have wireless STBs. I will go back and carefully look at the TP-Link settings. In the meantime I found in the MS 2012 forums that it is a common problem that the remote access stops working in a multi router situation. I still have to digest what their conclusions are. There are some directions but I do not understand them entirely.
thanks for your help.
06-02-2013 11:06:31 PM
Well, wouldn't you know. I did some browsing, after I wrote my post, around the wireless router settings and there were settings for IPTV http://imageshack.us/a/img600/8780/router1.png
I set the correct port and it worked. I didn't get any freezes. nothing. I was finally able to get rid of the hub I was using to splice the feed from the RG.
There's also settings for the unicast and multicast items you mentioned in my router as well. http://img266.imageshack.us/img266/7947/router2s.p
I'm assuming I don't have to tweak those since I'm getting the TV feed just fine.
Now, my only problem is my wireless router isn't sending out the wifi signal but I don't know if that's a result of me switching on that IPTV setting. I'm guessing it isn't but I'm going to bug ASUS about that tomorrow. Would you have any suggestions on that?
and Thanks again
06-03-2013 07:42:01 AM
Anyway, if they're working, then leave them as they are currently set.
For the wireless, you'll need to check the wireless settings in the Asus and verify that you have wireless enabled and that the access point's SSID is not hidden (or you'll have to manually add it to your devices if it is hidden).
06-03-2013 10:14:01 PM
so I fiddled around a little more with the TP-Link router and the Server 2012 Essentials issue of non-working remote access. After giving up I removed all special settings I applied (e.g. forwarding not under UPnP) or giving the server a static IP or putting into DMZ mode from the TP-Link).
A day later it started to work. I have no idea why. I have a slight guess that it may have to do with certificate reinstated for the server which may have taken some time after I initialized the Anywhere Access with the new router.
All works - thank you Joe!
06-16-2013 08:56:54 PM - edited 06-16-2013 09:05:28 PM
I have read through this entire thread (across several of days of course...tons of good info here!) and have 2 external wireless AP's running on my network (both hard-wired back to the RG), as according to post #13, along with wireless enabled on the 2-wire 3801HGV itself. I can connect to any one AP just fine, but switching from one to the other when walking throughout the house causes issues. My devices can see each AP's signal but cannot get an IP address when switching to a different AP. I suspect this is due to caching on the RG itself (it is handling the DHCP), as when I "Clear the List" on the LAN->Status page of the RG, I can then connect to a different AP just fine. This happens no matter which AP I switch to or from - I have to "Clear the List" each time to get a connection. When using only one AP (doesn't matter which one but the other two disabled), everything works fine when connecting/disconnecting. I am using the same SSID on all 3 AP's, but have tried having 3 different SSID's with the same result. Am I right there is a caching or DHCP release/renew issue on the 2-wire RG itself and is there a fix?
At one point I threw in the towel on having the 2-wire do the DHCP and set up a 2nd router using the "post #2" instructions. Everything worked in my test, but that isn't a long-term solution for me due to needing the 2-wire for my TV STB's. The way my house wiring is set up, I don't have the ability to run 2 separate networks for each, hence why I am doing AP's only.
This has been so frustrating...please help!
06-17-2013 12:28:06 PM
The 2Wire is quirky on IP address renewals. The IP DHCP request must come from the same MAC address when you roam from one access point to another. If it doesn't, then things will not work properly.
Make sure of the following:
- The access points are set up in accordance with post #13 (DHCP on the access point turned off, wired connection going to a LAN port, not WAN port, wireless mode must be normal access point infrastructure mode -- not ad-hoc or wireless bridging, etc.)
- All SSIDs should be identical
- The 3 access points should be on different channels, and should be at least 4 channels away from each other -- try 1/5/9, 2/6/10, or 3/7/11.
- All access points should have the same encryption type and password, and no MAC filtering should be in use.
- If you're running alternate firmware on either of your two access points like DD-WRT or Tomato, make sure the access points are not doing MAC-NAT or anything like that. The MAC address in the packets traversing over the network must be the MAC address of your laptop, not the MAC address of the access point or one of its internal interfaces. (See above -- disable wireless bridging/proxy/etc.)
If you still can't get it to work, I would begin to suspect your access points. What manufacturer and model wireless access points are these?
06-17-2013 01:43:19 PM
Thanks for the quick reply. I can confirm all of your bullet points above are true for my setup. The two other access points besides the 3801HGV are a Linksys e1000 v2 and WRT54G v8. The e1000 has DD-WRT which I just flashed a couple days ago hoping that might help (it did not).
In further testing that I just did today, I set up the e1000 to be a true router (a-la post #2 and using 192.168.2.1) with the WRT54G assigned to 192.168.2.2. 3801HGV wireless disabled. I went back and forth turning wireless on and off on one or the other and my devices transitioned to the other AP seamlessly when the e1000 DD-WRT was giving out the IP's. This test setup was done all within one room - unfortunately this isn't practical for me for the long-term because of house wiring limitations.
This certainly seems more and more like quirky IP renewals on the 3801 to me. However it sounds as if you're saying it should work if I have everything else set up correctly. Is there something else I could be missing?
Thanks for your help!
06-17-2013 04:04:35 PM - edited 06-17-2013 04:05:06 PM
Well, there are a few other people who have reported that they're using the 2Wire + another wireless access point together and are able to roam between them. However, I don't think anyone has reported that they're doing it with 2Wire + 2 additional WAPs.
Indeed, it could be the 2Wire's DHCP causing problems. You may try to factory reset the 2Wire, I've seen that cure some inexplicable problems in the past.
06-19-2013 07:52:21 AM
I did the factory reset on my 2-wire, and unfortunately it did not help. Still having the same issues when switching from one AP to another. Sometimes it will get an IP and connect, sometimes it won't. When it does connect, it gets a very poor connection - not in terms of wireless signal but in terms of actual speed/performance. A speedtest shows ping times of > 1s and speeds in the Bytes range (not Mega, but Bytes). Almost as if something is wrong in the routing.
I'm now going to move towards setting up the 2 separate networks, on two different subnets. I'm sure it's been discussed here before, but how do I route one subnet to the other using the 2-wire so that I can access computers across both networks? I know it's pretty straightforward in DD-WRT but don't know how to do the same on the 2-wire. Because of my house wiring, I will have to have computers on each of the subnets, that will need to be able to share across the subnets.
06-19-2013 04:06:51 PM
At this point, I would probably recommend a 3rd router to be used at the 2Wire's location, and set it up as discussed in post #2. Then use the existing 2 as wireless access points only, set up as in post #13, connected to the new router. Then turn the wireless access point in the RG off.
06-21-2013 10:27:43 AM
One other interesting tidbit - when both AP's are connected through the 2-wire, using the Wifi Analyzer app on my tablet, I see that one of the AP's signals cuts in and out while the other stays constant. It's visible for a couple seconds, and then cuts out for a couple seconds (and back and forth like that continously). However, when both AP's are running through the Linksys router, both signals are constant and do not disappear. How would the 2-wire be affecting the signal/connection like this?
06-21-2013 11:02:35 AM
I would chalk it up to just general 2Wire weirdness. Hence my previous recommendation for using at least one of them as a router in accordance with post #2.