Solve : Disabling P2P file sharing on the network?

1.	Solve : Disabling P2P file sharing on the network?
Answer» Hello Can I ask which is the best way of detecting P2P filesharing on a network. I'm not in a position to download analysers to a user's computer. Ideally, it would be best if the programmes showed up in cmd prompt and I wondered if any of the netstat commands on a user's computer would do the trick: http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/com.ibm.aix.prftungd/doc/prftungd/nestat_a.htm Thanks for any suggestions. SteveWhose computer are you talking about? Do you own it?Hello Broni Thanks for your reply. No, I don't own any of the computers which may access P2P filesharing programmes, but I am partly responsible for the healthy running of the network which these applications abuse. Thanks.You need to explain better your relationship to a whole network, and computers involved.Hello Broni I work on a helpdesk for a university responsible for Windows/Mac operating systems and the network itself. The network is sometimes subject to abuse where students use P2P filesharing which drains the network, resulting in other students having intermitten Internet connection problems. A bit like living in a houseshare where one person uses up all the HOT water for himself! We are able to detect some network activity using Wireshark, for instance, but it is limited. So, I wondered if it were possible, simply using a student's own cmd prompt to detect which P2P tools the student was using, and if devices were being used by that student's laptop (such as a router). Where we suspect P2P filesharing we disconnect students from the network. Does this help? SteveI suspect you're way out of your league. First of all, does your school policy prohibit using P2P programs on students private computers? Secondly, who is in charge of enforcing any of those policies? You?one possibility would be to block ports used by common P2P programs. And HOPE that no legit programs use them...Quote one possibility would be to block ports used by common P2P programs. Since the OP didn't answer my last questions, yet, you may be playing with serious legal issues.Well, He's already stated to be responsible for the network itself- it would be nice to know what it means to be responsible for the Mac/WIndows operating Systems, but simply owning the network is enough to block all questionable LAN ports. I don't see how this would raise an legal issues, really- it would end up slowing down torrent downloads, but they won't be stopped entirely, and in any case, everybody knows one of the prime reasons for using a P2P program has legal issues in and of itself, which would very likely prevent anybody from pursuing any legal stance they did have with the university.Quote I work on a helpdesk I've never seen any helpdesk person, being a network owner.Quote everybody knows one of the prime reasons for using a P2P program has legal issues in and of itself It has to be proved in court in each individual case.Hello Yes, it is because this is an issue I have not dealt with before and is probably above me, that I am posting this message - for assistance. And yes again, it is the policy of the IT department to disconnect users who use P2P programmes on their own private computers. I did not draw up this policy, but it is one of my ROLES to ensure it is put into practice. My apologies for lack of clarity. In addition to some network issues, I am also responsible for dealing with Windows and Mac problems. That's all I was trying to say. Almost all users deny using these P2P programmes, but sometimes Wireshark picks them up and we can tell, too, by the amount of complaints which come in from other users whose connections are intermittent. My original question simply asked if there was a way of picking P2P users up from the cmd prompt on the users' own machines - would they show through tracert, for EXAMPLE, or a similar COMMAND? - because we are in a position to go through, with the users, set up configurations on their computers. I hope this clarifies things.

Answer»

Hello

Can I ask which is the best way of detecting P2P filesharing on a network. I'm not in a position to download analysers to a user's computer.

Ideally, it would be best if the programmes showed up in cmd prompt and I wondered if any of the netstat commands on a user's computer would do the trick:

http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/com.ibm.aix.prftungd/doc/prftungd/nestat_a.htm

Thanks for any suggestions.

SteveWhose computer are you talking about? Do you own it?Hello Broni

Thanks for your reply.

No, I don't own any of the computers which may access P2P filesharing programmes, but I am partly responsible for the healthy running of the network which these applications abuse.

Thanks.You need to explain better your relationship to a whole network, and computers involved.Hello Broni

I work on a helpdesk for a university responsible for Windows/Mac operating systems and the network itself.

The network is sometimes subject to abuse where students use P2P filesharing which drains the network, resulting in other students having intermitten Internet connection problems. A bit like living in a houseshare where one person uses up all the HOT water for himself!

We are able to detect some network activity using Wireshark, for instance, but it is limited. So, I wondered if it were possible, simply using a student's own cmd prompt to detect which P2P tools the student was using, and if devices were being used by that student's laptop (such as a router).

Where we suspect P2P filesharing we disconnect students from the network.

Does this help?

SteveI suspect you're way out of your league.
First of all, does your school policy prohibit using P2P programs on students private computers?
Secondly, who is in charge of enforcing any of those policies? You?one possibility would be to block ports used by common P2P programs.

And HOPE that no legit programs use them...Quote

one possibility would be to block ports used by common P2P programs.

Since the OP didn't answer my last questions, yet, you may be playing with serious legal issues.Well, He's already stated to be responsible for the network itself- it would be nice to know what it means to be responsible for the Mac/WIndows operating Systems, but simply owning the network is enough to block all questionable LAN ports. I don't see how this would raise an legal issues, really- it would end up slowing down torrent downloads, but they won't be stopped entirely, and in any case, everybody knows one of the prime reasons for using a P2P program has legal issues in and of itself, which would very likely prevent anybody from pursuing any legal stance they did have with the university.Quote

I work on a helpdesk

I've never seen any helpdesk person, being a network owner.Quote

everybody knows one of the prime reasons for using a P2P program has legal issues in and of itself

It has to be proved in court in each individual case.Hello

Yes, it is because this is an issue I have not dealt with before and is probably above me, that I am posting this message - for assistance.

And yes again, it is the policy of the IT department to disconnect users who use P2P programmes on their own private computers.

I did not draw up this policy, but it is one of my ROLES to ensure it is put into practice. My apologies for lack of clarity. In addition to some network issues, I am also responsible for dealing with Windows and Mac problems. That's all I was trying to say.

Almost all users deny using these P2P programmes, but sometimes Wireshark picks them up and we can tell, too, by the amount of complaints which come in from other users whose connections are intermittent.

My original question simply asked if there was a way of picking P2P users up from the cmd prompt on the users' own machines - would they show through tracert, for EXAMPLE, or a similar COMMAND? - because we are in a position to go through, with the users, set up configurations on their computers.

I hope this clarifies things.

Solve : Disabling P2P file sharing on the network?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment