The support for Peer-Peer (Ad Hoc) wireless on Microsoft Windows workstations is problematic at best and should be avoided. Man in the middle attacks and "Evil Twins" can be avoided with a little care.
Wireless on Microsoft Windows includes support for "Peer-Peer (AdHoc)" as well "Infrastructure" networks. Peer-Peer networking involves two or more laptops communicating directly with one another -- it is sometimes used for gaming. Infrastructure support involves an access point that the laptop connects to that relays traffic to the larger Internet. The campus wireless network is an Infrastructure network with robust connectivity to the Internet.
If you are not careful you may automatically connect to a Peer-Peer network when you mean to connect to an Infrastructure network. That can have nasty consequences if the peer you connect to is malicious -- the peer can act as a man in middle to capture all traffic you send and receive (also known as the Evil Twin). Further, if you have connected to a Peer-Peer network your laptop will advertise that it is ready and willing to connect to or host similarly named networks in the future. This can be a problem for those connecting to you.
A convenient option is to have your wireless card automatically connect to any available wireless access point. This saves you a few steps at home or at work when getting online. The downside of an automatic connection is that you may end up connecting to a rogue access point, otherwise known as an "evil twin."
This configuration prevents you from automatically connecting to any new networks and refuses all ad-hoc networks.
Much of the above is from the Nomad Mobile Research Center -- we are greatful for the information provided.