- May 16, 2000
- 13,522
- 0
- 0
I love @Home. No really I do *gags on the sarcasm*. All right, I have 3 IP's from @Home and the second one is somehow corrupted (more on this later). So I call up to have them remove the IP from service and get a new one. Tier II used to handle this so I ask to be transfered up. I learn that they took that right away from Tier II. So I get transfered back down. I explain it to Tier I...they tell me it's taken care of. I go online and get a new third IP. Guess what??? It assigned my old IP address to the new computer name. So (after first grabbing a total of 5 IP's just to be safe) I call back and re-explain it all to them. They tell me it's Tier II. I tell them what Tier II said. They transfer me anyway. I talk to Tier II. The assure me they can't do it, it's Tier I now (and this time I knew the guy so I trust him). Back to Tier I. I re-re-explain it to them. I'm informed that "they can delete my computer name with the bad IP, but there's no way for them to take the IP out of the loop. Also there's no way to report this problem to their provisioning department unless it's during business hours so I can speak directly to them and tell them what's wrong." So I tell him forget it, just delete the two extraneous accounts and note it all in the ticket. The only good side to all this was getting some credit on the next bill and now all three IP's are on the same block so I can finally have my network set up the way I want without a lot of hassle. Jeez Louise.
Now for the question: Why was my IP corrupt? Background: A & B computers were on same IP block (24.10.67.xxx). Periodically (sometimes 2-5 minutes, sometimes 4-6 hours) I would lose connectivity with the B computer. I would still have my DHCP info active, and could ping my own IP and local loopback, but couldn't get to the gateway with pings or traces. A never had this problem. When I reformatted B it kept happening. When I set A up as B it started happening to that one as well, when I traded it back to A it worked fine. It couldn't be the gateway because they were the same for A & B. A DHCP release and renew would fix the connectivity. Setting static I would still lose connection, but then there was no way to get it back without restarting (since release and renew are pointless static). I also got these problems when I was with Tier II and was told 'the IP's bad, escalate it'. What is a 'bad IP', how does it get that way, and what is done at the administration level to correct it - if anything.
Now for the question: Why was my IP corrupt? Background: A & B computers were on same IP block (24.10.67.xxx). Periodically (sometimes 2-5 minutes, sometimes 4-6 hours) I would lose connectivity with the B computer. I would still have my DHCP info active, and could ping my own IP and local loopback, but couldn't get to the gateway with pings or traces. A never had this problem. When I reformatted B it kept happening. When I set A up as B it started happening to that one as well, when I traded it back to A it worked fine. It couldn't be the gateway because they were the same for A & B. A DHCP release and renew would fix the connectivity. Setting static I would still lose connection, but then there was no way to get it back without restarting (since release and renew are pointless static). I also got these problems when I was with Tier II and was told 'the IP's bad, escalate it'. What is a 'bad IP', how does it get that way, and what is done at the administration level to correct it - if anything.
