[NCLUG] IP Masqing on the New and Improved AT&T

[Terry M. Gray]

I'm using an Apple Airport to do my wireless and my routing. I was 
using DHCP on the wireless part of my network and that worked 
flawlessly. I have to use explicit IP's on the wired side (and for 
some port mapping) for some of my machines. I had the same problem 
that you have described with those machines until I put in the new 
DNS's that were being detected by the DHCP on my Airport. So I have 
the 10.0.1.1 (the private address for my Airport) but the attbi.com 
numbers for the DNS. I also set attbi.com as the domain. This made 
the problem with the "transition page" go away.

TG



>I have a few neighbors that are seeing something similar, they have a
>home network and dns doesn't seem to work (every page goes to some att
>help page). They're using windows and cable modem/hub boxes.  Could it
>just be something in Ft Collins?  I'll tell them about your solution.
>
>Matt
>
>>Has anyone else noticed strange things afoot when trying to do IP Masqing
>>through AT&T's new setup?   It seemed that no matter what I did, I couldn't
>>get out from my Masqed boxes (the ones behind my firewall).  My Masqing box,
>>on the outside, could see and do everything appropriately, but it seemed
>>that even ports were being blocked when I tried to connect out from the
>>backend boxes and http requests out just always returned the transition-aid
>>page (http://transition-aid.attbi.com/attbi_welcome_page.html).  Called tech
>_______________________________________________
>NCLUG mailing list
>NCLUG at nclug.org
>http://www.nclug.org/mailman/listinfo/nclug


-- 
_________________
Terry M. Gray, Ph.D., Computer Support Scientist
Chemistry Department, Colorado State University
Fort Collins, Colorado  80523
grayt at lamar.colostate.edu  http://www.chm.colostate.edu/~grayt/
phone: 970-491-7003 fax: 970-491-1801