Unable to connect to Battle.net

[[vL]Kp]

Have tried this wireshark thing, but it doesn't make any sense to me, what exactly am i supposed to do with it?

Post the output somewhere.:) Wireshark is a good diagnostic tool, but its output is often meaningless to people who lack a deep networking background. I can read it pretty quickly, and hopefully there are a few other people on the lounge who could do the same. Beware that depending on your capture options, you might have snagged quite a bit of unrelated traffic, some of which could be considered "sensitive" (i.e. contains personal information, reveals network layout that you don't want to share, etc.). Note: even if you were not doing anything sensitive at the time, Wireshark probably went into promiscuous mode, in which case you could have captured traffic from other people in the network. You can filter the capture as you take it or you can have Wireshark resave an existing capture with less information. To do the latter, go to the "Filter" input control, write a rule that excludes irrelevant traffic (in this case, "tcp.port == 6112<enter>" should do the job), and then do File->Save As. Choose "All packets" / "Displayed", and save it to a new file. Make the new file available.

using windows vista home premium

I'm so sorry. No one should have to use the home versions of Windows Vista.

It does work though, only problem is the connecting to b.net part.

I've manually patched to 1.09, but it doesn't seem to have made any difference.

I imagine the problem has something to do with the fact that I'm on a large server in a student dorm but I'm sure that a lot of you played in college on similar networks, so any ideas?

I have read that Windows Vista has a more comprehensive firewall than Windows XP, though I do not know if it has been turned on for your system. As a quick test, try opening a command shell and running telnet uswest.battle.net 6112. After telnet responds, you can just dismiss the window. If the connection succeeds, that indicates the problem is Diablo being unable to get to battle.net. If the connection fails, the issue is a more general connectivity problem. Your university might be blocking traffic on port 6112. Do you have any friends on campus that are still running Windows XP? If so, consider having one of them try to get on battle.net. Since Diablo has no cdkey and the failure occurs before account logon, you would not need to share any logon information with them. This would distinguish a problem with your system from a general inability to use battle.net from university.