|
|
 |
|
|
Pages: 1
Dang UDP pack crap on 6112
(Click here to view the original thread with full colors/images)
Posted by: Naxus
Yes, I am another poor soul who can't connect to battle.net because of the UDP packets on 6112. I'm running Windows ME, and I blame that, but I hope there is something I can do.
I've been searching and searching for an answer to this problem. I've emailed blizzard but I haven't gotten a response yet. It seems nothing works to fix this. Has anyone figured it out yet?
Posted by: Canis Lupus
Are you using a firewall with your broadband connection? Or a router maybe? If so, then you need to open up port 6112 to UDP and TCP/IP incoming and outgoing...
Try these URLs and see if any of these solutions help you out:
http://www.blizzard.com/support/ind...ution&BugID=280
http://www.blizzard.com/support/ind...ution&BugID=247
Post back on your progress...
Posted by: Naxus
Ok, I use BroadBand and I've heard about the problems for BB users in NY. I live in Massachusetts. I traced my connection to bnet and I have like 44 ms on all the servers, thats very good. I can always connect and start playing a game, then suddenly the screen goes blue and I get the warning and error message with Netmate(1) or something. I'll do it again and write it all down. BTW this is problems with StarCraft. I also play Diablo II and I have absolutely no problems with that. I don't know if I have a firewall. I'm pretty sure I don't, could you tell me how to open up port 6112? Also, those solutions didn't work.
Posted by: Canis Lupus
I assume you didn't build your computer and bought it from a third party vendor. Who did you buy it from, and what does this "Netmate" program do ... disable or uninstall that program and see if the problem goes away...
We need more details about your system and connection so that we can help you better... Write down and post here the error message(s) you get...
It would also be a good thing to consult the tech pages of your broadband provider and your computer's manufacturer, if you have access to them...
Posted by: Naxus
COMPUTER (Gateway)
Pentium III ~633MHz (L1 cash: 32.0 Kb, L2 cash: 128.0 Kb)
memory: 126 Mb (129 420 Kb)
14.3 Gb (8.66 Gb free = 60.5%) (8.66 Gb free on C: drive)
Intel(r) 82810E Graphics Controller
Doesn't list my sound card ie.. gateway sucks
Network card: (1) USB/Ethernet Link
Microsoft Windows ME (probably my first problem  )
I'm pretty sure that Netmate is a program for the network card. It might be the drivers so I can't uninstall or disable it. A few times this happend my network card wouldn't work at all, the light went out.
Ok I played again and this was the error.
netmate2(01) + 00049CD Error : 0E : 0028 : C2A1982D
and then the game exited. If I try to log back on Bnet I'll get the UDP packet message on port 6112.
Posted by: Canis Lupus
Okay, first make sure that you have the latest drivers for your USB Network Card. Check this link:
http://www.catc.com/products/support/sup_elc.html
Now, if the drivers won't work, what I would recommend is to see if you can change the network card on that thing to something else, and see if it works.
It could also be that Windows ME does not have the proper support for your network card.
Try the drivers first ... and stick around for more suggestions...
Posted by: Naxus
Yeah I forgot to mention that I did that already and it didn't work.
Also, I reinstalled the game after getting the new drivers and that didn't work.
Trying to log on to battle.net again I get this error message:
"Your Internet connection is either very poor or is not processing UDP packets through port 6112. You will be able to char but will not be able to play games. Contact your Internet service provider or your system administrator for assistance with opening this port."
I contacted mediaone and they said they're not blocking it. But I'll bet that this problem occured because of my network card which has that error when I play.
Also, I don't know if I told you this or not but I play Diablo II on battle.net useast and I don't have any problems with that.
Oh and one more thing. I often have problems with my cable modem, it will stop working and I have to unplug my network card and then plug it back in. Sometimes my mouse will stop working at the same time I restart the network card. This makes me think windows ME has trouble with the card, let me know what you think.
Posted by: Bobaroo
It must be your network card that is not working, or causing you to not get on b.net. If your mouse and cable modem don't work with your network card, that could mean that SC does not to.
Posted by: Naxus
Whew, ok I just upgraded to Windows 2000 and it seems that everything is working perfectly. I haven't disconed once. I also installed the Network card updates correctly. That may have something to do with it.
Posted by: Bobokiller
It must have been the network card drivers because this same setup works for a friend of mine using Wingate and WinME on both computers, sharing access to battle.net over his cable modem.
Posted by: TueurDelite
i had that problem before am using windows Xp . i had to reformat to get it working 
Posted by: ant2334gog
I'm having the same problem. I get an error message about connection to port 6112 with UDP. I play Diable 2 LoD on Battle.net with no ploblems, my problem is just with Starcraft.
Computer Specs.
Microsoft Windows 98SE(a little outdated)
Pentium III 600MHz
128MB RAM
Video Card - NVIDIA RIVA TNT2 Model 64(newest detenator drivers)
Sound Card - MachOne
Network - DFE-530TX+ 10/100 PCI Fast Ethernet Adapter
I connect to the internet with SNET DSL.
P.S. I don't have the money to upgrade OS.
Posted by: Shalome
Starcraft uses more than just UDP packets on port 6112.
Hosting/Playing a TCP/IP game (not on Battle.net):
Port 4000 must be open to send and receive TCP packets.
Hosting/Playing a game on Battle.net:
You must open port 6112 through port 6119, and 4000 to receive inbound AND outbound TCP and UDP packets.
Posted by: Neon Reaper
Or if you have a server like i was on, you need to get a network administrator to come "open" those ports specified to allow more UDP and TCP packet receivability
Thought I would share to those in need suffering from the same problem as I once had
|
|
|
|
|
