03-16-2011 8:18 AM - edited 03-16-2011 8:59 AM
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)
Solved by: Go to Solution.
10-10-2011 1:13 PM
I tried some of the tutorials in this thread, but I am still unable to get internet.
Here is what I am trying to do
I have two computers connected to the 2Wire router that came from ATT, and I have two more that I want to be connected to another router (TP-Link) because it's a gigabit router and I transfer files very often between PC3 and PC4.
I have a wire from a LAN port of 2Wire going to the WAN port of the TP-Link router. I followed the steps in one of Joe's first posts, and everything was set up like it said it would be. (The TP-Link router got the external IP and ect) However I have no internet connectivity on PC3 and PC4
I did tried changing routers default address pool from 192.168.1.100-200 to 192.168.2.100-200, but that didn't help.
Thank you for your time.
10-10-2011 1:45 PM
To do this you have to open all ports on the 2Wire router. If you have already done this then I don't know what the problem can be. I have similar setup but with a Belkin router and works fine with two different IP pools like you have. FYI the two PC on the 2wire router will be more accessible to hacks with all the ports open...i have all my PC on my Belkin and 1 of my SlingBoxes and my Xbox connected to the 2wire since they could not connect through Belkin
10-10-2011 1:53 PM
^ I don't have all the ports open on 2Wire, but the LAN port that the router is connected to is set for DMZPlus.
10-10-2011 2:01 PM
10-10-2011 6:02 PM
Don't follow the instructions in post 2 of this thread. For your application, follow the instructions in post 13. This will turn your TPLink into a switch + wireless access point. You will not use the WAN port on the TPLink, just the LAN ports.
10-10-2011 8:31 PM
^ That work perfectly, thank you so much!
I did see it before, but I figured I needed the other steps.
Thank you again! I can finally enjoy my gigabit network again.
10-14-2011 3:43 PM - edited 10-14-2011 3:50 PM
Joe, (and everyone else), if you're still prowling around here, I could really use some help. I've been at this for quite a while, so any advice would be hugely appreciated.
I have the 2Wire RG, a Time Capsule (1st gen), a Mac Mini running OSX Server 10.6, a pile of switches, and a block of static IP's from Uverse.
The environment is a small business (25-30 people in and out on laptops, phones, a couple of hard-wired desktops, etc.)
My goals are relatively simple, but I can't seem to figure it out.
The main goal is to set up the Mini as an FTP server that can be accessed through the LAN and from the WAN.
Secondary goals would be wireless network printing, as well as two separate wireless networks (the time capsule serving specifically N-enabled devices, while the 2-wire would deal with everything else a/b/g, whatever).
Edit: I also wouldn't mind having some DNS resolution for the Mini on the LAN.
This seems to be the only thing on the internet that I can find that deals with the 2Wire, so I hope you all can help me out.
Thanks in advance.
10-14-2011 4:16 PM
10-17-2011 1:28 PM
I tried the other forum and Oz responded, but said he wasn't sure exactly what to do with the networking. Maybe I'll give it another try and put it in more generalized terms, rather than specific hardware, since you seem to be the resident networking genius.
I think there's only a couple things tripping me up, and I should be able to troubleshoot on my own once I have the main skeleton figured out.
I have: A server that I would like to do DHCP, FTP, and some DNS Resolution; a wireless router that can be put in bridge mode, the RG, and a block of static IPs.
My main questions are:
Where do I need to point my static IP (to which piece of hardware)?
Do I need to add a supplimentary network in the RG setup?
Should I place anything in the DMZ?
Are there any ports I should need to open up?
What would be the physical cabling setup?
RG --> Router --> Server ?
RG --> Router ?
If this still doesn't make sense, I apologize for bothering you.
10-17-2011 2:45 PM
11-15-2011 9:09 PM
Thanks for the help in this thread -- I've been troubleshooting some issues and your comments have been invaluable.
I do have a question, though. I followed the instructions in post 2 on this thread (turning the 2Wire into a pseudo-bridge) and have a Netgear WNR2000v3 in the DMZ, with all my other devices hanging off the Netgear (had to do this because my wife works from home and has a SIP phone that connects to an IP PBX at her work that I simply could not get to play nice with the 2Wire, even in the DMZ).
I think I ran into the problem you mention in point 8 of that post, wherein after a short period of time the Netgear would just lose its Internet connectivity; I guess it was probably blocking the DHCP renewal packets. I followed your advice and set the IP address static and everything has been fine for 30 minutes now. Hooray!
My question is this: since the IP address I've set the Netgear to is actually the public IP address the 2Wire is assigned by AT&T, and it's not a static address, is that address likely to change regularly? I assume when that happens, my connectivity will break pretty hard. Do I need to get a static IP from AT&T? Do they even offer those to residential customers?
11-16-2011 7:32 AM - edited 11-16-2011 7:33 AM
If your IP address happens to change, then yes, it will break your connectivity and you'll have to reconfigure the NetGear.
However, it is known that on the U-Verse system, IP addresses normally do not ever change, unless the 2Wire RG is replaced or (sometimes) if it's factory reset.
I have been running a web server at home on a U-Verse IP address for over a year, and the IP address has not changed.
You can indeed purchace a block of 5 static IP addresses if you want, but those have to be assigned by the 2Wire. The 2Wire also has no facility to insert a static route, so you can't use those static IP addresses behind your router -- you can only use one of them on your NetGear's WAN interface. The other 4 would go unused.
12-07-2011 11:22 AM
Is this the easiest way to set my router up behind the RG? I want to have as many functions as I can from my Router which is the Asus RT-N56U
12-08-2011 6:11 PM
Hi Joe, I am thinking you can help with my issue. Here is what I've got:
Uverse 2Wire 3800HGV-B
Netgear WNDR3400 (brand new!)
LG N2A2DD2 NAS (fairly new!)
My Netgear was just hooked up the other day and seemed to realize what was going on and automatically assigned itself a new sub net (10.0.0.1). The 2Wire is still 192.168.1.254. Everything seemed to work just fine....networked all my computers, printers and have access to my LG within the network.
Now one of the reasons I put the new router behind the 2Wire was to get access to the LG from outside the network. The LG has software that helps to set it up but it is telling me that I need to setup port forwarding on my router. I tried this when I had the 2Wire only but couldn't get it to work since 2Wire doesn't support UPnp. So, I bought this new router, set up port forwarding for all the ports that LG says I need open, and it still fails to connect on all three test items: Web (HTTP, HTTPS), FTP Port, & Media Server. I followed all your instructions on Post #2 as well and rebooted the Netgear multiple times and still cannot get it to pass.
I want to first make sure I've got everything setup correctly on the 2Wire and Netgear before contacting LG about how to get this to work and thought you might be able to help. Thanks!
Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!
Service acting up? Click here to troubleshoot now!
For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.