Outside says Xfinity XB3. Admin page says:
Model: DPC3939Vendor: CiscoHardware Revision: 1.0Serial Number: 269815875Processor Speed: 447.28 MHzDRAM: 524288 MBFlash: 128 MB 

     On Sunday, February 1, 2015 3:01 PM, Ryan Coleman <ryan.coleman at cwis.biz> wrote:
   
 

 Which model modem did they bring?

On Feb 1, 2015, at 1:44 PM, Olwe Bottorff <galanolwe at yahoo.com> wrote:
Looking at the modem admin page, I saw that the errant T410 was only listed as its MAC address. Also, it was not listed as DHCP but always listed with a "Reserved IP" of 172.16.0.145 --which will not allow itself to be changed, even when I repeatedly try to choose DHCP and save. On a hunch, I changed (Ubuntu/Gnome) in the "IPv4 Settings" tab from "Automatic (DHCP) to "Automatic (DHCP) addresses only". Now it works . . . after a whole weekend of hair-tearing-out! Can anyone tell me why it wants to default to (won't change from) "Reserve IP"? And what did my changing to ". . . addresses only" do exactly?
Thanks. 

     On Sunday, February 1, 2015 1:43 PM, Olwe Bottorff <galanolwe at yahoo.com> wrote:
   
 

 I want to blame Comcast because these problems on the T410 don't appear when I use it on any other Wifi connection (I'll test again to make sure) -- and they don't even happen when Comcast gave us a loaner modem a few weeks ago! The new box is a dual 2.4/5.0 GHZ, while the loaner box was just 2.4 GHZ. On the new (and previous) 2.4/5.0 box I can't get any Internet logging into the 2.4, and the 5.0 connection gives me the aforesaid weirdness. There has been sporadic weirdness with other things too: Android devices tend to act up occasionally; an older Kindle has trouble getting online. I also tested this with the T410 on a straight ethernet connection to the modem -- same problems. To make it even more confusing, I tried Win8.1 on the T410 -- and it worked just fine. So if my T410/U14.10 works elsewhere AND with a different Comcast modem, gosh, it must be some very weird clash with the 2.4/5.0 Comcast modem and my T410/U14.10. Also, my Thinkpad X201 used to have weirdness, but it settled down and seems to work now. That's another wrinkle to this, problems come and go. For a long time we'd get Internet AFTER we waited 10 minutes or so after Wifi login, sometimes even with ethernet. But again, like I say, my older T61/U14.10 works fine. The only explanation I can think of is that the Comcast 2.4/5.0 modem and U14.10's network software don't like each other when U14.10 is installed on my T410. Just for laughs, I should get a non-Debian Linux version or even BSD for my T410 and see what happens. 

     On Sunday, February 1, 2015 11:32 AM, Ryan Coleman <ryan.coleman at cwis.biz> wrote:
   
 

 
 My Thinkpad T61 (also Ubuntu 14.10) works fine with no weirdness. 
So it’s your laptop not Comcast.
It’s amazing who quickly people blame their ISP when only one device on the network has issues.
I suspect something is RFU with your firewall (UFW).

On Feb 1, 2015, at 9:47 AM, Olwe Bottorff <galanolwe at yahoo.com> wrote:
Still having problems with my Comcast Internet service. Now it looks like my U14.10 Thinkpad 410 connection (wire or w-less) won't do ssh (no route to host), won't give me most web pages, but, amazingly, will connect with gmail, YouTube, and Wikipedia. Also, I can do software updates and synaptic. My Thinkpad T61 (also Ubuntu 14.10) works fine with no weirdness. 
LBGrand Marais (in spirit)_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
tclug-list at mn-linux.org
http://mailman.mn-linux.org/mailman/listinfo/tclug-list




 
    

 
    



 
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20150201/72816b47/attachment-0001.html>