Welcome to the MacNN Forums.

juanvaldes · Feb 1, 2003, 04:52 PM

I can not access these sites. I can't update WC3 from instead the game. I am sitting here at a LAN party with everyone else on 1.05 PC and both blizzard & battle are coming up for them. The mac patches do not seem to be online anymore.

Anyone know whats up?

xyber233 · Feb 1, 2003, 05:48 PM

Everything works fine for me. I'm all updated.

juanvaldes · Feb 1, 2003, 07:05 PM

I still can't connect to battle.net from WC3 and blizzard.com is still down to my browsers.

Adam Betts · Feb 2, 2003, 01:09 AM

What did the error dialog window said? Lack of connection or couldn't connect to B.net? Maybe you could delete the pref and relaunch.

BTW, I didn't know that you like to play WarCraft 3? If you're on the east coast, my account is AdamBetts (just don't look at the record... you'll get a heart-attack

)

juanvaldes · Feb 2, 2003, 02:19 AM

well after the usual 2+ min time out I get that message. Couldn't connect I believe. I will try the pref but I don't think it's that as I can't connect to blizzard.com in my browser either. And I know its' up as both in game up-date AND blizzard.com works from windows.

edit: deleting prefs didn't fix it.

juanvaldes · Feb 2, 2003, 03:58 AM

well

!!!!!!

I get home and it works just fine. I'm now beginning to think it was some issue with my campuses network (I live off campus). But if that was the case why did it still work for windows...

xyber233 · Feb 2, 2003, 09:48 AM

Did other websites work?

xyber233 · Feb 2, 2003, 12:15 PM

Now that we are on the WC3 topic....who here is the best at WC3?

juanvaldes · Feb 2, 2003, 04:55 PM

Originally posted by xyber233:
Did other websites work?

yup, everything but blizzard.com worked. And that worked just fine on the windows system, but could see no mac patches.

As for who's the best, not I. I have school and other **** to do, but my roommate plays with the top30 on B.net all the time.

rbarris · Feb 2, 2003, 05:18 PM

We found a rash of people on campus networks that were not able to connect to battle.net with their Mac even though PC's were working OK.
With help from Cisco, Apple and one particularly knowledgeable poster on the support forum, we narrowed the cause of the problem down to an optional feature of TCP/IP called RFC1323, and a bug in certain Cisco routers. While Cisco has a fix ready, they have not yet released the updated router firmware. However we do have a one line command that you can use to disable RFC1323 from Terminal in OSX:

sudo sysctl -w net.inet.tcp.rfc1323=0

It should answer like this:

net.inet.tcp.rfc1323: 1 -> 0

This variable will only stay set to 0 for the rest of your login session.

We have found that the vast majority of "campus network blockages" are cured by this change.

The reason it specifically affects battle.net and perhaps not other connections has to do with the way that the TCP software on each end negotiates during the setup of a connection. It is this particular combination of Cisco firmware version, Mac OSX client, and the server software used for battle.net that can lead to this connection failure. As you discovered, other connections might in fact work fine. Not all TCP/IP transactions are created equal, as a few long sessions with a packet sniffer will reveal. ('man tcpdump')

Interesting side note, we also discovered that a PC running the OpenBSD UNIX operating system could be blocked from connections by this interaction.

I hope this helps.

Rob rbarris "at" blizzard.com

Gul Banana · Feb 2, 2003, 10:49 PM

How alarmingly specific... a graphic illustration of the impossiblity of covering every contingency.

skyko · Feb 3, 2003, 01:03 PM

Originally posted by rbarris:

sudo sysctl -w net.inet.tcp.rfc1323=0

I hope this helps.

Rob rbarris "at" blizzard.com

Dead on the point. Now Blizzard stuff works again (I'm sitting behind a CISCO PIX firewall). Only your diagnosis that only battle.net would be affected is not quote correct. I could not even get to http://www.blizzard.com/ without using the ISPs proxy. I thought this would be something bad the ISP does, but since using your hint it started to work too!
I guess that PIX will be removed ;-)

zorn · Feb 3, 2003, 04:08 PM

Originally posted by xyber233:
Now that we are on the WC3 topic....who here is the best at WC3?

Not me, I suck

Well I'm still a newbie .. a newbie with the disadvantage of not being able to play much at home ether cause my Ti only has 8 MB VRAM (er...) Hoping to get an iMac ASAP when the are rev-ed .. then you're all going down

CyberZorn (on EastCoast)

xyber233 · Feb 3, 2003, 05:19 PM

I'm just hoping someone is really good so they can send me their replays

.

rbarris · Feb 3, 2003, 08:05 PM

Originally posted by skyko:
Dead on the point. Now Blizzard stuff works again (I'm sitting behind a CISCO PIX firewall). Only your diagnosis that only battle.net would be affected is not quote correct. I could not even get to http://www.blizzard.com/ without using the ISPs proxy. I thought this would be something bad the ISP does, but since using your hint it started to work too!
I guess that PIX will be removed ;-)

Ah, but what if battle.net's machines and 'www.blizzard.com' are running on the same OS and TCP/IP stack when you run the test? Bam, same problem occurs.

Rob rbarris "at" blizzard.com