Friends and Family test and NDA

FYI, we’re getting very close to starting the closed public beta test for Diablo III. You might start seeing some new reports about the beta client as we’ve begun limited external testing with employees and their families, and there is no non-disclosure agreement (NDA) for that. We look forward to sharing more info about the beta test in the near future. Stay tuned.

If you have a beta license, you are free to show, share, or talk about any portion of the beta content to which you have access, as this beta test is not confidential.

Q u o t e:
Why was this posted later on these forums then the others?
Has thou forgotten us Bashiok?!

Anyhow, hope this "close" is actually close.

Because I can log in and post on the new forums from home. :)

Q u o t e:
Do friends and family keep beta access once you've moved into the closed beta? I thought this would be an obvious yes, but somebody asked me that today, and I'd like to be able to give the correct answer.

We don't plan to remove anyone's access once they have it.

Is anyone having this issue that is not on a campus connection?

Would those of you experiencing this issue please let us know what campus you are trying to connect from?

While I don't have a specific solution for any of you, I do want to reiterate that where ever you're playing, you need to make sure the appropriate ports the game uses are open to and from your pcs. In many cases, such as a campus, hospital, apartment complex, etc... you won't have the ability to do this yourselves and must rely on a network admin to make sure they're open.

Here's the list of ports again for reference.

Battle.net - is using 1119 TCP and UDP. 1120 is reserved for future use but shouldn't be used at the moment.

Launcher - 1119, 80 for web site for patch notes

Downloader - 3724, 6881 ~ 6999 for P2P, (Downloader uses 3724 first and if it’s not available then moving to 6881 and up to 6999.)

Patching – TCP 80

Voice – 6113 UDP

Something to keep in mind is if this issue has come up on campuses at around the same time for a lot of people, it may be the result of an update to a piece of networking hardware those campuses use, such as a primary Cisco router for example.

We'll continue to monitor the forums for any more info as it's provided to help pin down any possible causes.