New Kazaa v2 using port 80

I was wondering about information anyone could give me on this new version of Kazaa. I myself have never used any version of Kazaa, but since its (v2) release the network at my school runs very slow, the Network Admin clames it is because Kazaa v2 uses a default of port 80. Our school has also recently been attacked by a DoS attack that the Admin also attributes to this Kazaa v2, not to mention that our school network has attacked other places recently too. The network admins are blocking those IPs of the people that are doing this but more and more people are downloading this program every day. Basicaly I am wondering if 1) Kazaa v2 can be the cause of all this and 2) What can be done to stop this from going on??

Thanks

Disable port 80 :D

Seriously though, if your admin seriously wanted to stop this, he'd disable/unauthorise the ability to install programs by simple student users (login restrictions). They could also attempt to block any types of sites with the affiliation to the word KaZaA (although you can get around that) They could always use a firewall to restrict any connection made by any other program then the browser. There's many things the school admins can do, I find it odd they haven't though of this?

The fact is that P2P programs are known bandwidth hogs mostly because of file size and most users choose to do 15 to 20 downloads at one time, even if it's not port 80 this will slow down an entire network, and yes cause a massive security hole through well built firewalls. Most colleges and universities have banned their use for this simple fact alone, how by having a student or a parent clearly informed that such programs are not allowed and if instally the user account will be disabled, not a good thing at school. Sounds like the security needs to be tightned at your school users informed that some actvities will not be allowed then activly monitor the network for the out going traffic. Have the parents suggest a full time net admin person you cannot do it part times now days.

I remember the first version of kazaa had alot of spyware everywere and lack of security and now they have moved away from spyware into makeing backdoors. LOL I understand that kazaa needs peaple to connect directly to its networks but that doesn't mean that they should highly weaken systems by opening a !MAJOR! root port.

It would be really disastrous if kazaa were using port 80 by default. Not because more people can get files but because the only way that ISP's could keep some bandwidth open for their customers would be to drop all requests to port 80 on their network by default. Then if you wanted to publish a web site they would charge you an arm and a leg for the privilege. This would be the end of a free internet.

This isn't true is it?

Google search for "kazaalite". It probably won't rectify the Port 80 problem, but it also won't load a lot of other useless crap with it. I believe the main KazaaLite page was kazaalite.tk

Oh! thats what the admin claims...ok! i was trying to leave work when i saw your post.

when kazaa/lite loads it displays a kazaa home page which it gets by making a request to kazaa.com port 80, but all the bandwidth gets eaten up by requests to port 1214 for file downloads and searchs from the computers of users.
Although he is right about the bandwidth getting eaten up by p2p. if half the users on the network all decide to start downloading mp3s, you might as well switch to tin cans and string.

i hope these p2p users see what their doing so their not too shocked when restrictions are placed on their internet usage.

High Speed Bell Sympatico in Ontario has a cap on their usage. A friend of mine found this out the hard way. He enjoys downloading "movies" off Kazaa. His last bill was for $190+. That was for one month! I've now heard rumors that Rogers High Speed Cable in Ontario will also be putting a limit on usage.

kazaalite V2 will allow the user to change the port used for downloads. The suggestions on other boards have been to bypass firewall security by using port 80, port 8080, or port 21. :(

It still won't help the fact that a school full of kazaa users will use port 80.

We would go out of our way to change it, but what about the other 80% of people who don't care, as long as their songs and such come in?

And as for the Ontario thing, Rogers has put a cap, but if you exceed it, you get cut down to near 56k speed. (but no extra billing!)

yikes, limit on Rogers? i just got mine a couple of weeks ago, so i certainly hope they don't end up doing that here in New Brunswick. after being on dialup (28.8kbps max, mind you) for seven years, capping my newfound broadband would just be a kick in the face.

so i have to make sure nobody in my town downloads too much or i'll have to break their fingers :(

Why does your school even allow you to download software such as KaZaa in the first place. I know if I even downloaded software such as Winzip for example I would probably get suspended if I got caught. What do you do on your computer at school that would even require KaZaA? heh..

Use kazaa lite.....problem solved. ;)

no, because the other half of the problem is that people downloading mp3s kill any bandwidth on the network, which happens to be another big problem. well, for the school, anyway.

as far as the Port 80 issue goes, i suppose you could, you know... not download the new version of kazaa.

I'm with Ted and Tiger on this one, it is one thing to design a P2P network and it has the pipes to deal with the downloads. But fact is simple all P2P users think they are the pnly ones. My son uses Kazzalite and when he in on-line and I am on my connect is useless so I unplug him. I have a big pipe into the house and he thinks nothing of 30 to 40 MP3 download and maybe a video or two all at the same time (why if I am using his line is not connected). But is is also not fair to other broadband users mostly moms and dads on my leg of the connect because his activity will slow their use also, (an old man I care about my neighbors thing even if you do not know them). Fact is ports can be closed real fast and outgoing traffic can be watch just as easy P2P is a great concept if all users and the system are designed for a specific task. Face it the recent laws attempting to be passed are because of mass copying of copyrighted stuff. If you were a struggling music person that was lucky enough to get a contract to have your works published is this considered selling out or paying the rent, feeding your children or caring for your family? Just like JP here 24/7 he wants a life becuase 24/7 for free will not pay the bills...go figure :) Life costs money and hads nothing to do with selling out just feeding the children or life you may owe for college loans. Be i music, programs what ever you get what you give.

When Kazaa first connects, do a "netstat -n", You'll will see what ports Kazaa is connecting on. It does not connect nor download on port 80. Port 80 is merely used to show that first "web" interface. I tried, unsuccessfully, to block users connections to P2P progs by adding the following lines to our company firewall.

access-list acl_in deny tcp any any eq 1214
access-list acl_in deny udp any any eq 1214
access-list acl_in deny ip any 213.248.112.0 255.255.255.0
access-list acl_in deny ip any host 217.116.226.11
access-list acl_in deny ip any host 217.116.226.12
access-list acl_in deny ip any host 217.116.226.13

Users can still connect but they cannot see that first "web" interface because it's ip is blocked. Some downloads that choose to initiate on 1214 get blocked as well. I think to block access totally we are going to close access to all ports above 1024 from within the firewall.

Quote:

---

Originally posted here by Gixxer
When Kazaa first connects, do a "netstat -n", You'll will see what ports Kazaa is connecting on. It does not connect nor download on port 80. Port 80 is merely used to show that first "web" interface. I tried, unsuccessfully, to block users connections to P2P progs by adding the following lines to our company firewall.

---

I have done some more homework on Kazaa v2 using port 80 and I have been told that it uses it for an alternative port for incoming data. The person I talked to was unsure what would "trigger" Kazaa to switch to port 80. So if anyone knows what causes it to switch it would be very helpful. Obviously the solution would be to Turn off the "Use port 80 as alternative for incoming connections" but it seems that some people don't know, don't want to, or don't care. This great connection speed for viewing webpages kinda reminds me of using a 28.8k dialup connection...

If your school is using Novell, I am absolutley sure that the admin. could block it, it is very strange that they haven't thought of that unless the admin is a monkey wearing boxing gloves

Couldn't you prevent this whole problem from starting if you are at a school/university/work and not allow the end users to install KaZaa or Kazaalite at all?

Where I used to work, we ran NT 4.0 on top of Novell and no end users could install and .exe files.

-Chris

Quote:

---

Originally posted here by JockVSJock
Couldn't you prevent this whole problem from starting if you are at a school/university/work and not allow the end users to install KaZaa or Kazaalite at all?

Where I used to work, we ran NT 4.0 on top of Novell and no end users could install and .exe files.

-Chris

---

The problem with not allowing the end user to install the P2P programs is that the end user's computer belongs to them and is hooked up to the network through a connection in their dorm room.

Someone called in to the helpdesk here at school really upset over the network being soo slow. When she was told that its because people are missusing network resorces she asked if she could have all their names to go find them and "hunt them down". Well it turns out that she was one of those people missusing the network... OOPS

Quote:

---

The problem with not allowing the end user to install the P2P programs is that the end user's computer belongs to them and is hooked up to the network through a connection in their dorm room.

---

My bad, I didn't know it was a university and people's own machines, not the school's machines.

Ya, that would be tough to control/admin., and from what I understand from my friends who live in university dorms, it is anarchy on those networks, especially is wireless is involved.

But, alot of these companies are now going after the schools for copywrite violations, maybe u all could claim there is a lawsuit against the school and ban all P2P file swapping.

-Chris

Those talking about trying to block KaZaA and other net apps like ICQ and MSN, what OS is your Lan running? Best off is to get Win2K (Don't flame, Understand most Schools and Companies use Win2k for their users) and some third party blocking software and disable installing properties/priviledges for the users. (Kinda like Linux removing ownership of system)

As for the dorms at such, it actually is not legally allowed to control the content that the pages or software is obtained by the students. It becomes invasion of privacy and conflict with right to press/media and expression & speech.

The reason work and school computers in labs and libraries are allowed to be monitored is that your purpose there is for work/studies and not for leisure activities.
Read 2600 magazine Spring 2001, page 6 about it.

Divine Rogue,
A fellow newbie here. Did you know there was a new virus discovered on November 18, which infects KaZaA networks and creates a backdoor Trojan? It's called W32.HLLW.Togod.
See www.symantec.com, and click on expanded threats. This might me the cause of the "dos attacks" that you mentioned. Just a thought.