02-12-2012 05:57:08 AM - edited 02-12-2012 05:57:44 AM
02-16-2012 07:24:18 PM
After making the changes recommended in this thread I was working great...until yesterday. All of a sudden my Windows 7 laptop wouldn't get an IP address and then today my wife's Macbook Pro wouldn't either. I just set them with static IPs and it appears to be okay, but that's not an acceptable solution. I'm about 90% sure once I turn on my PS3 or Western Digital TV Live Plus, they'll not get any IP addresses either.
Anyone had any luck with UVerse support helping out on this issue?
At this point I'm really close to putting my old Linksys WRT54G back into service behind the 2Wire router because it's so bad.
02-19-2012 03:56:15 PM
But why won't they ?
02-19-2012 06:08:40 PM
I've got this problem too, and in searching the web, many people do, and AT&T or 2-wire need to fix this. At first, my problem was I randomly could not get to my desktop computer's shares. I thought it was some random Windows7 problem and fought with it for a while, and even paid to upgrade to win7 Pro. Then one day I realized that if I went to it by IP address instead of name, it worked. So, I started looking and the computer and the RG admin panel showed it had a valid IP address, but when you would ping it, it would resolve to 127.0.0.1.
After searching and finding many with the same problem, I cleared the IP address list in the RG and rebooted. I DO NOT WANT TO DO A FACTORY RESET as that, in the past, has caused me to get a new external IP address. I don't pay for a static IP address, but it never changes, and I depend on that and have some firewalls at clients opened to it.
Anyway, I did the clear and rebotted the RG, and DING... I could then get to the shares on the desktop computer flawlessly... I thought problem was solved. But, nope. It just moved the problem to another device. It is now my Brother MFC printer that is getting 127.0.0.1 when you ping it. Again, it and the RG show a valid address, but the DNS is resolving to 127.0.0.1. And, this time, I can't seem to get it to fix, even with clearing the list.
02-21-2012 09:04:40 AM
I have set up this DHCP server application http://www.dhcpserver.de/dhcpsrv.htm on my desktop, to replace the DHCP server running on the U-Verse gateway.
So far, so good. I will make another update here in the future to let you know if I have any more problems.
Setting up a DHCP server is not a big deal, but if you don't understand the concept, you probably need directions. Maybe I can write some up later, but not now. I just wanted to let you know I am trying the idea.
History: Been having to reboot at least once a week or every time I try to bring certain devices ont o the wifi. Kindle, HP laptop from work, Dell laptop, and sometimes iPhones. Pretty much every kind of device sometimes connects, but cannot get an IP.
I have factory reset more than once.
I have tried all of the suggested settings.
02-23-2012 09:27:52 PM
02-23-2012 09:29:27 PM
02-24-2012 05:43:00 AM
Interesting. Three or four days ago would be when I had the last "failure" of the network -- after not having any problems for a while.
Love how they are blaming the "Apple devices" for the problem, and not their hardware. It's not like they don't have access to this stuff to test it before they release new hardware/software.
I will also bet the device the are going to blame is the iPhone, because that is the only device in my group of devices that is able to stay connected to the network. Tough little guy. ;-)
02-24-2012 10:32:19 AM
Honestly, the problem does seem to happen predominately with Apple devices. This could be that the Apple devices use a unique interpretation of a spec that is compliant but unexpected, or it could be out of compliance with the spec, or somewhere in the gray area between those two points.
However, it is descriptive.
02-24-2012 10:40:51 AM
Thank you noahphex for the encouraging note! I guess we all have to wait patiently for the next update now.
It seems logical that some device (such as iPhones) on our networks could be behaving in a way that the router's DHCP service was not handling properly. I just hope they really have it nailed down this time.
02-24-2012 10:57:40 AM
Will the firmware update for the 2Wire gateway be automatically pushed to the modem or do we need to install it manually?
Your 2Wire RG will automatically update.
02-24-2012 11:01:47 AM
Thanks, texasguy37. I will check when I get home. Early this morning my Uverse service was down-my alarm system started beeping due to loss of phone service. After a little while it came back on. Could that have been the update coming through?
02-24-2012 02:43:48 PM
Yes, it could have been the update. The RG has to reboot, so everything goes down: TV, Internet and phone. My experience is that they come through in the middle of the night, like 2 or 3 am. I have been working before (I do on call some weeks) when it happend. Kind of a forced health break.
If you log into your RG's web page from your PC, you can dig into the menus and find the current firmware version.
02-24-2012 03:53:01 PM
If you still have problems send Alex a PM he is an ATT Community Manager on this forum.
02-27-2012 08:22:46 PM
02-29-2012 07:25:57 AM
I have had a DHCP server freeze issue since I got Uverse and have to reboot my server all the time at varying intervals.
I have had no solution from them or this forum and quite frankly don't think AT&T gives a darn.
I called and they offered to ship me a new unit that I would have to configure myself when I got it or change all of the configurations on my devices to match the new unit or the wonderful option to pay $149 to have a technician come out and service their equipment.
Somehow AT&T thinks that I work for them, I offered to do the configuration on the new device for a fee and they declined.
If AT&T told 2wire that they would no longer use their hardware until this issue is resolved they would fix it quite rapidly to be sure.
It's too bad but I am looking to replace Uverse with something that does not require me to pay for hardware and then be a support agent for that hardware.......
02-29-2012 07:38:52 AM
I have a friend who has had the same problems with DHCP via wifi. I have found I don't have any of the issues since I have setup my own router with the RG and set the DMZ mode for my router. Doing it this way it passes your public ip to your router and you have your RG in a sudo "bridge" mode.
I have found this to be pretty reliable and also i got better wifi coverage and have wireless n. It is honestly the best solution at this point. You also might want to see getting the equipment rental fee waived permenantly. It is silly they charge $6 a month for something that has so many problems and does even have wireless n or gigabit ethernet.
02-29-2012 08:01:53 AM
Regarding the people saying we shoud "set up our own router" and resort to other kinds of self-help:
Not everybody is technically inclined enough to do that -- this is why we pay AT&T (a lot of) money -- to provide these services for us.
I know enough to be dangerous and I don't think I should be mucking around with settings and configurations that could potentially mess up my connectivity and cause me to have to request a service call and have to pay AT&T MORE money to fix what I broke.
No, AT&T needs to make it work the way it was intended to be used.
As an aside - The shutting down computers at night seems to have kept the problem at bay. However, now I schedule my online backups for during the day, instead of overnight which is an inconvenience, but it's not the end of the world.
02-29-2012 09:51:49 AM
I simply expect AT&T to hold their vendors accountable and deliver what they promised but that seems to be a stretch in todays society.......
03-04-2012 09:24:09 AM
Hey guys. Looks like I'm suffering from this issue as well. I just posted my story here: http://forums.att.com/t5/Residential-Gateway/Netwo
I see mentions of a new firmware that may fix the problem. Just checked my firmware and I'm still on 126.96.36.199-enh.tm. I think the version everyone is mentioning is 188.8.131.52. I know the update will automatically happen at some point but is there a way you can force the update?
Thanks and I'll subscribe to this thread and share my learnings (if any). Keeping fingers crossed.
03-12-2012 08:29:22 AM
I recently got Software Version 184.108.40.206-plus.tm on my system. My Kindle was actually on the WiFi by itself for the first time in months, without my having to reboot the router!
Crossing my fingers that this fixes the issue for good!
03-14-2012 07:45:43 AM
Another positive report. I had given up on the WiFi and disabled it on the router and started using my own wireless router. When I saw that I got the update, I enabled the WiFi again and I haven't had to restart the RG in over a week. I used to have to reset the unit daily, so I'm hopefully optimistic that this has resolved our problem!
03-30-2012 02:34:54 PM
03-31-2012 08:02:21 PM - edited 03-31-2012 08:26:49 PM
I have had this problem too. Nice to find this thread. I just got U-Verse a couple of months ago. I have lots of Apple products and some Linux boxes and sometimes run windows on some laptops. The DHCP issue is the one that everyone here notices, but when that issue is there, I also see problems with some of my wireless devices no longer being able to talk to each other. Details of my equipment are (from the Settings/System Info/Status page):
Manufacturer 2Wire, Inc.
Hardware Version 000705-004
Software Version 220.127.116.11-enh.tm
DSL Modem 8.1.4
Wireless Access Point
Manufacturer 2Wire, Inc.
Hardware Version 2700-000679-004
Software Version 18.104.22.168-wifi.tm
This was installed on Jan 18th, 2012. The interesting thing is that when I sometimes find that one Linux box can no longer ping or ssh to another box, that the wired devices I have connected to the i38HG can still ping and/or ssh to both of those boxes. In all cases every box could still go through the router to the internet. They just couldn't talk to each other. All these problems do clear up after I power cycle the i38HG wireless access point. I have not always had success by rebooting the unit via web access, but pulling the power plug and then plugging it back in 10 seconds later has always done the trick. I'm glad to see this is a known problem and very discouraged that there has been no positive identification or solution. I just tried one possible solution mentioned here and that was changing the wifi protected setup to disabled and changing the wifi security setting setting from "WPA-PSK (TKIP) and WPA2-PSK (AES)" to just "WPA2-PSK (AES)". I'll give this a couple of weeks and if no trouble, then I think there's a good chance those changes have worked.
04-02-2012 05:39:57 PM
I just want to report that I tried changing the wifi protected setup to disabled and changing the wifi security setting setting from "WPA-PSK (TKIP) and WPA2-PSK (AES)" to just "WPA2-PSK (AES)", but I had the DHCP trouble already the very next day. A laptop running windows could not get an IP address. I'm tempted to disable the WiFi and connect another wireless router to one of the ports of the i38HG. But I'm also kind of curious what the heck is going on, so for now I'm digging in and trying various things for a while. Amazing that this has apparently been going on for months with no indication that the problem has been solved even in the latest firmware (I don't have the lastest firmware -- I'm just going by reports in this thread). So far, playing with the settings in the web server, the software seems buggy and/or poorly designed. Often a network device will show up as having a static IP, even after I've changed that device to use a dynamic IP. When making reserved IP addresses for the DHCP server, you're shown the name of the device and not the MAC address. Often times a device will show up as connected when it isn't or as not connected when it is. I see no way to save my settings locally or restoring settings from a local file. The logs, which you can send to a syslog server, are useless for diagnosing DHCP problems as they do not show the MAC addresses. I'm also unable to find any documentation on the logs. I don't see a way to update the firmware as that is apparently done automatically (but for some reason has not been done on my system). I hate to call tech support because I know what a time waster that can be and it doesn't sound like anyone else has really had their trouble resolved via tech support. Ugh.
04-25-2012 08:40:16 PM
Sounds like I have the same exact same issue and it's driving me crazy. It started for me about 2 weeks back and only impacted one device, my Leno work computer running Windows XP on my 2WIRE Gateway (but I'm not on Uverse if that matters). My company tech support couldn't figure it out so they replaced the wireless card - still same issue. AT&T sent out a new gateway (Pace 4111N) and still same issue. I have no issues connecting to other routers or service providers - it's only at home on AT&T. I have several other wireless devices (Ipad, Iphone, Apple TV, Wireless Thermostat, Vizio TV, and Laptop running Windows7) and all connect without issue. It just this PC running on Windows XP SP3.
As of now, I get "limited or connectivity" message...and sometimes after a few hours, it miraculously gets an IP and then works, but as soon as I disconnect and try to reconnect, it fails and have to wait several hours.
I've tried everything I can think of - resetting IP stack and Winsock, rebooting, no luck. Reinstalling adapter, no luck.
Anyone have any ideas or updates on how to fix this?