Posted by Bleh. on December 10, 2000 at 22:50:49:
In Reply to: technical diff. posted by maximelb on December 10, 2000 at 19:16:43:
> Hi, I've finaly found out why I can't connect to CF (website and telnet)... I contacted my ISP and they told me they had a problem with sprintnet for IP attribution Uh. IP attribution would have nothing to do with it. Other than you not getting one, meaning you're not truly online at all. Sure, you're dialed into a bank, but you're not goin' no where. and so, some IPs could not be accessed... I think what you mean they meant is "Sprintlink is having routing problems." What else is new? But there's the funny part, I've got 2 comp. at home with the same cable modem link to internet, Whee! both with "modem built-in" IPs Huh? Speaka english! (2 separate IPs without proxy) Uh. . One of my comp. can acces carrionfields, Yay! and the other can't. Boo! Has anyone had the same problem or heard of the sprintnet problems? If one of your comps *can* hit cf, it's not sprintlink. It's the other comp. I've been 3 days without playing CF now, if tomorow I can't I'll... well, I'll... just wait ! (argh) what can I do, those damned ISP.(dictators). Damned ISP dictators? Look, bucko - from your lack of grammar and utterly nonsensical attempts to communicate I *know* you're a moron. If what you say they said hasn't been lost in conveyance then they're morons too. Morons can't dictate anything. Now me? *I* am a damned dictator. And I work for an ISP. Does that make me a damned ISP dictator? Probably. Now, listen close: If there were routing problems, be it arp cache clearing, bad route tables, or cut fiber *noone* on that side of the bad thingie would be able to get past it. Meaning.. if it's a bad route table on the sprintlink router your isp is inside of no one at your isp could hit that *class* of IPs. Since your *OTHER COMPUTER* can hit cf that means it's not sprintlink, it's not your isp, and if the computer that can't hit cf can pass traffic somewhere it's not even your hub/router/gateway/firewall/however the fuck you've decided to network the two computers, cable momem and kitchen sink. Now, should I be helpful, or should I keep being abusive(Like I always want to do when morons like you call me and say "My thingie's broke. It says I can't connect. Uh, what does "Page Fault in Kernel32.dll mean?" Well, I suppose I'll be helpfull. If the one computer can hit cf, and the other can't, the problem is going to be on the computer that can't(because I'm abso-damn-lutely positive that you aren't bright enough to have set up some sort of gateway/firewall/routing thingie. You've got the two computers plopped into a hub, DON'T YOU!?!) If you can't pass traffic at all, the problem is going to be either your network card or tcp/ip protocol(mebbe socket files?). If you can pass some traffic(in your case comprable to passing gas?) but you can't hit cf... you've got the wrong subnet mask configured. Or you've got a virus infesting your socket files. Whee! Wasn't that easy? > a ranger who want to wake up!