I used to work IT for a university here in TX, and i can say that the above is correct. 99% of all universities will not allow private servers to be run on their networkm even worse.. to add to the above topic of port scanning, activities such as this can be expellable offenses on some campuses, not t0o mention that even if the port is open, it is more than likely only open to allow certain types of traffic, and definitely not UDP or TCP connections on a p2p. Add also that as soon as you set up your server and try and access your server from your laptop in your dorm room, you will most likely have to do so with a router in your room in order to accomplish this, and most campuses also restrict routers in student dorms due to the mess they can cause... especially if dhcp is enabled on the router and connected to the school network. Read your Student Computing Handbook, or contact your IT or ResNet staff, but in my experience, it is usually much less of a headache and much easier in the l0ong run to just fork out the cash for a server colocation and host your server in someone elses farm cluster. Most colocations are fairly cheap, i have 15 19" racks being colocated for MUCH less than it would cost me to build/maintain the server room and not to mention a dedicated dual oc-48 connection for them with very generous bandwidth allocation. A single server can be hosted for 15-30 a month depending on required bandwidth, cooling, power requirements, security, backup, maintenance, etc. Do a search in your area for "Server Colocation", many of the sites will allow 24/7 access for maintenance and upgrading your server. You supply and maintain the box, and they take care of the rest of the logistics.