Welcome to the new AT&T Community
We've got a fresh look! Take the tour to see what's new.
I am having trouble properly configuring this AT&T 2Wire 3600HGV modem for my network. Maybe someone is aware of a different firmware for this product?
I am completely aware of how to setup the DMZ mode & router behind router setup in these boxes but that is NOT the point. (We have supported firewalled networked equipment working that has all the bells & whistles including QoS)
In the event of a factory reset of the AT&T 2Wire VDSL modem at this business, I want to properly insure the following business requirements are met:
- DHCP - OFF (at min, it appears you must leave one available?)
- WiFi - OFF (Yes this can be turned off, but bridging it always insured it was turned off in the past. ON is a security concern among just bad business i.e. conflict with other business WiFi, employees might see/use this non-content filtered WiFi, etc etc)
- & passing off internet service needs to be easy to another networked supported OUTSIDE of AT&T firewall. (I'm NOT asking for AT&T support on this, but in the bridge DSL world, this was EASY)
- if bridging this 2Wire is NOT an option, backing up the configuration settings would be a nice alternative but that is not available as well?
Bridging the old DSL modems always worked nicely but the 2Wire 3XXXHGV line appears to be the ONLY ones to support the AT&T VDSL Max Turbo speeds. 24Mbps down / 3 Mbps up which we use not only for normal business operations (credit cards, business email, web based training, etc) but this high speed is required to view onsite security video (3Mbps up) and offer customers FAST free WiFi!
AT&T U-Verse offers the right price, contract, speed, internet package & installers to properly handle our resturant locations company's data needs but I'm struggling with the their "business" support of this 2Wire VDSL modem product. We ONLY use the internet, no TV (not legally available for restaurants, yet). No Voip because POTS is our reliable backup. So it's just the internet service ...
For coverage on AT&T Uverse, we have over 50 locations lit up like a Christmas tree but sadly business support on this product is driving me nutz! Maybe because I now see this is listed under "Residential Gateway"? Is this AT&T 2Wire VDSL modem product not meant for business? Is anyone aware of another supported AT&T VDSL modem or a different 2Wire firmware available? Official AT&T support has me running in circles (AT&T U-verse support > AT&T Connecttech > AT&T Connecttech360 > AT&T U-verse support, rinse, repeat)
There is no true bridge mode on the 2Wire routers. However, you can still configure it such that almost all functions of your own router will work properly.
1. Set your router's WAN interface to get an IP address via DHCP. This is required at first so that the 2Wire recognizes your router.
2. Plug your router's WAN interface to one of the 2Wire's LAN interfaces.
3. Restart your router, let it get an IP address via DHCP.
4. Log into the 2Wire router's interface. Go to Settings -> Firewall -> Applications, Pinholes, and DMZ
5. Select your router under section (1).
6. Click the DMZPlus button under section (2).
7. Click the Save button.
8. Restart your router, when it gets an address via DHCP again, it will be the public outside IP address. At this point, you can leave your router in DHCP mode (make sure the firewall on your router allows the DHCP renewal packets, which will occur every 10 minutes), or you can change your router's IP address assignment on the WAN interface to static, and use the same settings it received via DHCP.
9. On the 2Wire router, go to Settings -> Firewall -> Advanced Configuration
10. Uncheck the following: Stealth Mode, Block Ping, Strict UDP Session Control.
11. Check everything under Outbound Protocol Control except NetBIOS.
12. Uncheck NetBIOS under Inbound Protocol Control.
13. Uncheck all the Attack Detection checkboxes (7 of them).
14. Click Save.
Your router should now be able to route as if the 2Wire was a straight bridge, for the most part.
Inbound port 22 might be blocked, and inbound ports 8000-8015 might also be blocked, and there's nothing that can be done about it.
This is how I have my 2Wire configured, and I have a Cisco 2811 behind it doing IPSec, IPv6 tunnels, etc.
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.
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?
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!
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..
You may have to reset your Linksys E2000 to factory defaults. It might be remembering the old RG.
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.
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.
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?
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.
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.
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.
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.
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
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!
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!
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.
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?
Sign up now to post, reply, and join the conversation.
© 2014 AT&T Intellectual Property© 2014 AT&T Intellectual Property link. This link will open a new window All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. AT&T 36USC220506