Notice! BNet may be unreliable after a patch! - Page 9
Forum Index > SC2 General |
theSAiNT
United States726 Posts
| ||
skronch
United States2717 Posts
![]() i don't even have a firewall on | ||
sMi.WiZaRd
United States28 Posts
On May 23 2010 00:40 skronch wrote: i still haven't been able to get around the authentication module error ![]() i don't even have a firewall on same alot of mac users are having this problem | ||
Teejing
Germany1360 Posts
SC2MASTER_SERVER_ERROR_INVALID_DATA | ||
jamesr12
United States1549 Posts
| ||
zakkssst
Canada19 Posts
| ||
SichuanPanda
Canada1542 Posts
| ||
Guc
Australia28 Posts
| ||
NB
Netherlands12045 Posts
=> bootcamp => window => still authen cant download spam login button for 3 times PW bar appear, enter pw => agreement => the ship fly away and u stare at the universe forever ![]() | ||
zakkssst
Canada19 Posts
| ||
Djzapz
Canada10681 Posts
On May 23 2010 00:48 zakkssst wrote: what if you cant hit the login button? Seems you don't want to login anyway atm do you... Game is unplayable. | ||
EnvoYofAiuR
Netherlands71 Posts
| ||
murd3r3r
Czech Republic102 Posts
| ||
SichuanPanda
Canada1542 Posts
Sadly, it appears that this trend is moving towards SC2 already in Beta. Now don't get me wrong extended down times in a Beta are to be expected. I guess. I say this because Blizzard knows EXACTLY how many users are connecting because they know how many keys they have given out as well as access logs etc. - that said and as a result should easily be able to determine how much network access is needed to support the users, massive random server lag shouldn't happen. But it did in WoW Beta and first few days of release, and we can almost be 100% assured it will in SC2. This also comes with the random 'service updates' which Blizzard releases in both games already quite frequently, on WoW these are server side completely and you don't even download a patch. However every time, every single time Blizzard releases a patch on WoW there's extended downtime for 'an forseen issue' - I really hope this trend is not continuing into SC2. | ||
GoodCat1
Israel266 Posts
On May 23 2010 00:54 murd3r3r wrote: SC2MASTER_SERVER_ERROR_INVALID_DATA | ||
ToT)OjKa(
Korea (South)2437 Posts
| ||
SayaSP
Laos5494 Posts
On May 23 2010 00:59 SichuanPanda wrote: Ever since WoW came out it seems like Blizzard has forgot how to do networking or hire competent networking staff. Every single week without fail WoW comes down for 'some maintenance' as a network admin myself I can safely say a load-balanced network appropriate to the number of users connecting should not need weekly maintenance or even monthly maintenance, in fact the only thing I have ever to do with servers I run is a restart every now and then, which takes ~ 15 minutes per server. With remote server consoles you can easily restart all your servers simultaneously. But yet Blizzard still finds a way to take WoW servers offline every week, every Tuesday for extended periods of time. Sadly, it appears that this trend is moving towards SC2 already in Beta. Now don't get me wrong extended down times in a Beta are to be expected. I guess. I say this because Blizzard knows EXACTLY how many users are connecting because they know how many keys they have given out as well as access logs etc. - that said and as a result should easily be able to determine how much network access is needed to support the users, massive random server lag shouldn't happen. But it did in WoW Beta and first few days of release, and we can almost be 100% assured it will in SC2. This also comes with the random 'service updates' which Blizzard releases in both games already quite frequently, on WoW these are server side completely and you don't even download a patch. However every time, every single time Blizzard releases a patch on WoW there's extended downtime for 'an forseen issue' - I really hope this trend is not continuing into SC2. That's not just for network stuff though lol | ||
Teejing
Germany1360 Posts
| ||
Senx
Sweden5901 Posts
![]() | ||
SichuanPanda
Canada1542 Posts
On May 23 2010 01:06 Senx wrote: Then again, this being the unlucky number 13 patch, this seems to be the most convenient time to have a patch that is truly broken ![]() Woah Senx you might have something there. Look out here comes your 1337 post. | ||
| ||