- Comcast newsgroup problem
- Posted by Dieter Knollman on July 9th, 2003
The IP address assigned by the Comcast cable DHCP host is not recognized as
a Comcast IP by Comcast newsservers.
Attempts to sign up for Giganews yield FORBIDDEN - bad IP address.
Attempts to connect to netnews.comcast.net yield server not found, yet pings
find it.
Comcast customer torture claims that ALL IP addresses have been included in
the ATT merger, 67.166.9.xxx is not recognized.
With dial-up, I could hang-up, reconnect, and get a new IP to try again.
With cable, I keep getting the same IP address. I have tried to release the
address and renew, but get the same address.
Also resetting the modem yields the old Address.
Any help appreciated.
- Posted by Warren on July 9th, 2003
Dieter Knollman wrote:
Use netnews.comcast.net.
--
Warren H.
==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.
Webhosting: 500MB Space, 30G Transfer, 7.95/mo.
http://www.holzemville.com/refer/
- Posted by Dieter Knollman on July 9th, 2003
Thanks for the reply, but the problem is my IP address not the netnews one.
netnews.comcast.net does not work.
I get "Unable to connect to the server." in Outlook Express.
I also tried the direct IP addresses with the same result.
Pings on the addresses yield about a 50ms response.
I suspect that the server checks the IP client address and does not respond
for non Comcast User IP addresses.
Comcast has not added all the Colorado AT&T addresses to the data base,
although they claim to have.
I was hoping to find some way to get a new IP address, hopefully one in
their data base. Since DHCP and modem resets have failed I may have to
cancel.
"Dieter Knollman" <djhk@netzero.com> wrote in message
news:befm9k$775$1@news.chatlink.com...
- Posted by a user on July 9th, 2003
In article <behi1t$p54$1@news.chatlink.com>, Dieter Knollman wrote:
Didn't Comcast sell their Colorado, Montana, and ??? base to anther
cable company???? Thought I also read in the news that the transaction
was "completed"...
I just did some "host 67.166.9.xxx" and was returned that it was a
comcast.net client each time.
Have you tried looking up your own ip????
same ipaddr that was last used when you "cancel" the ipaddr; this
registry addr can be changed to another ip to get the ip specified.
Of course, it is preferable that the ip requested is not used by
someone else. Never tried it with an ip of 0.0.0.0 to see if a new
ip would be assigned.
I had made this discovery when I had a different ipaddr for windows and
linux on the same machine with the same nic and before getting a router.
As I wanted the same ip for both os, I just edited the windows registry
dhcp request ip since I "knew" the ip was also "mine"; however, I had
adsl at the time and still think that it may be the same with cable.
- Posted by Dr. Orgasm on July 10th, 2003
"Larry" <nospam@home.com> wrote in message
news:3f0ca2dd.37407689@news.usenetserver.com...
- Posted by a user on July 10th, 2003
In article <3f0ca2dd.37407689@news.usenetserver.com>, Larry wrote:
addr. I don't think the "conversion" converted everything as I am
still considered also as an attbi.com for hostname.
He implied that he had a 69.x.xx.xx addr which is probably a legacy comcast
ipaddr.
- Posted by Larry on July 10th, 2003
I doubt anything really changed. Comcrap just bought up the Accounts
Receivable and the headaches of customer support from ATT who's still
running the equipment and wholesaleing it to Comcrap.
On Thu, 10 Jul 2003 15:09:12 GMT, a user <paul@not_real.edu> wrote:
73 de Larry W4CharlestonSC
RF radiation hazards since 1957...
