Some games will not connect

Hello, I have SBC Yahoo DSL... er, AT&T Yahoo, or whatever they are called now - anyway; I have the modem connected to the "realtek rl8139 family pci fast etherner nic". Windows Firewall is turned off and I don't have another firewall. My problem is, some online games will not connect. For example, Yahoo Games and Inklink (no matter what browser I use). Also, iRO will connect, but kRO will not (not even the patchers), and nor will any, like, unoffical patchers - so I can not connect to private servers, which is making me quite sad. I realise I am trying to play some crappy games, but can anyone help me out with this? I tried adding kRO and firefox to the Windows Firewall allow list, even though it's turned off, but there was no change. Thanks in advance for any help you might be able to give me.

Yahoo

There's your problem.

are you dowloading (torrents) at same time. I have this pob. when I'm dl and try to play Wolfenstein - Enemy Territory. What I do, is set my upload limit to 15kb/s and then I can connect and play ET.

>>2
Well they're the only high-speed internet provider in my area :(

>>3
At first I was, but then I turned them off, no change...

Infact, everything I installed since I disabled this yahoo connection shit (this is my brother's computer, and he installed the sbc cd) won't connect. PPPOE connections won't connect, so I'm afraid to uninstall the yahoo connection shit completly...

http://www.obviously.com/tech_tips/Yahoo_DSL_setup_no_CD.html

>>6
Uh yeah, that's what I'm trying to do, I have a Speedstream 4100, but

>>PPPOE connections won't connect, so I'm afraid to uninstall the yahoo connection shit completly...

If I uninstall the yahoo shit, will pppoe connections start to work? I don't want to be completly stuck off the internet... where can I download the shit that comes on the CD (my brother threw the cd away), just incase?

http://www.disk919.com/bb/archived_learnins/install_sbc_yahoo_dsl_without_cd/

When I got dsl, I did this, never installed anything form CD and I have been online ever since.

>>1
I am going to stop trolling for a few minutes. This only happens like once a week so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

>>8
>>7
>>7

>>9
Thanks, but I'm not quite THAT stupid.

>>9
hey are you still around? Could you tell me what compelled you to copy pasta that? (I wrote it). Am I a retard? Are you doing it because it needs to be told to practically everyone who posts a support thread here?

I'd like to hear from you with questions/comments/feedback!

>>11
I am going to stop trolling for a few minutes. This only happens like once a week so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

that's great, but can anyone lead me to where to download the sbc cd shit?

>>12
hey are you still around? Could you tell me what compelled you to copy pasta that? (I wrote it). Are you a retard? Are you doing it because truth needs to be told to practically everyone who posts a support thread here?

I'd like to hear from you with questions/comments/feedback!

>>13
I am going to stop trolling for a few seconds. This only happens like once a month so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

>>15
hey are you still around?  Could you tell me what compelled you to copy pasta that? (I wrote it).  Are you a retard?  Are you doing it because truth needs to be told to practically everyone who posts a support thread here?

I'd like to hear from you with questions/comments/feedback!  I'd also like to subscribe to your newsletter!

siiiiiiiiiiiiiiiigh.

>>17
I am going to stop trolling for a few seconds. This only happens like once a month so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

I hate you guys.

hey are you still around? Could you tell me what compelled you to copy pasta that? (I wrote it). Are you a retard? Are you doing it because truth needs to be told to practically everyone who posts a support thread here?

I'd like to hear from you with questions/comments/feedback!

I got pppoe connections to work (I hooked up my hub and went to 192.168.0.1 Went to Advanced, PPP Location, changed it to PPP is on the computer) but stuff installed after I turned off the sbc shit will still not connect. Please help.

>>21
I am going to stop trolling for a few seconds. This only happens like once a month so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

BTW, I can ping things I can't connect to... for example, I can't connect to any irc servers since I installed the irc client after I turned off the sbc shit - but I can ping them fine

Thanks for helping, those that tried to... turned out I needed to uninstall Norton Internet Security