(wL) Forums

If the world is slowly coming to an end, they better not take down the Battle.net servers first! Leave em up while we having something to do when the world is crumbling beneath us.  :

for sure

| 02:00:04 PM | Downtime script loaded.
| 02:00:06 PM | -- BNLS: Connecting (bnls.anubisdev.net)...
| 02:00:06 PM | -- BNLS: Connecting (bnls.anubisdev.net)...
| 02:00:07 PM | -- BNLS: Connected!
| 02:00:07 PM | -- BNLS: Requesting version byte for: D2DV
| 02:00:07 PM | -- BNET: Connecting (useast.battle.net)...
| 02:00:08 PM | -- BNET: Connection is forcefully rejected!
| 02:00:08 PM | -- BNET: Try connecting to a different server or IP address...

Noooooooooo!! Its happening to me again Yet my NF will connect, Mirage wont.

[01:01:47 PM] [BNCS] Connecting to the Battle.net server at 63.240.202.130...
[01:01:48 PM] [BNCS] Connected!
[01:01:50 PM] [BNCS] Client version accepted!
[01:01:50 PM] [BNCS] Your CDKey was accepted!
[01:01:50 PM] [BNCS] Login successful.

Stupid battle.net and your rejections...

bnet dont like u lol

East Connection Problems

Is anyone else having connection problems connecting to USEast on bots?
Heres with MirageBot X:
| 12:42:12 AM | -- BNET: Connection is forcefully rejected!
| 12:42:12 AM | -- BNET: Try connecting to a different server or IP address...

And then I tried connecting with Alpha & Omega... and got:
[12:42:06 AM] Notice --- Connection interrupted, network may have dropped.
[12:42:08 AM] Notice --- Disconnected from 63.240.202.139.

Before these WAR3 updates everything has been fine, since they have happened, connections are seeming to suck... : \ Neglected Fury still connects btw.

Re: East Connection Problems

yep  139 is dead try 130

Re: East Connection Problems

This is slowly getting irritating lol

Re: East Connection Problems

lol dont us 139 lol u nub