bozo1, I wouldn't be able to use a router...those things prevent Internet-aware apps (like NetMeeting) from functioning.
But you say they would have to enable my MAC address on their DHCP...so their downloadable executable will do this? But this also means that if I upgrade or change my NIC (or buy a new machine), I would have to go thru the pain of re-registering my machine again...what are the chances that they'll screw up my account info? Or if I want to access with my laptop just for today in order to download Windows updates or whatever, the answer would be a guaranteed "no", because I, personally, am no longer their "account" or "subscriber"...a specific machine is now the account, and the only machine allowed to access the 'net. I pay for a service, and that's what they should provide, not restricting my capabilities to what they deem is acceptable.
EvlG, my wife spent an hour in AT&T tech chat last night...the guy assured her it's already happening, and that everyone will eventually be dynamic. There were one or two other links he pushed concerning the switch to DHCP. Here's some excerpts from the chat:
"No, all of our customers are now using dynamic IP addresses."
"...that may be, but eventually your IP address will change, and you will need to find out what your new one is."
"...the IP address can change at any time. You will not be notified, because we have informed all of our customers that they are to be set up dynamically"
(the last quote was a lie...I didn't find out until this chat happened)
"If you choose to have static settings, then you will eventually run into a little trouble with your connection."
He pushed
this link. I found
this link on my own. Also, DHCP is listed first for computer setup
here. And I found the following quote
here:
<<
Please note that the AT&T Broadband Cable Internet Service Agreement requires use of a DHCP TCP/IP client on the AT&T Broadband network. Customers who violate this provision and configure for a static IP in the Network Settings will now experience IP address conflicts and failure to establish a network connection. In order to avoid any IP address conflict, and possible loss and/or interruption of your service, your TCP/IP setting must be set to obtain an IP address from a DHCP server >>
LordFortius, using the machine name to place a NetMeeting call only works on corporate LANs, not the Internet...so that wouldn't work for me.