Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Limewire and Internet disconnection


  • Please log in to reply

#1
Waterchan

Waterchan

    Member

  • Member
  • PipPip
  • 18 posts
Hi there. Here's another one of my "mysterious" network problems again. :whistling:

I'm a university student living in on-campus housing. Each of the rooms here have this box that provides interenet, television and telephone service.

I have a laptop and a desktop. Before I had a wireless router, my desktop was connected to the above box via ethernet cable, and my laptop was connected to my desktop via crossover cable. I noticed that every time I started up Limewire, I would lose my Internet access for about 12 hours. In this situation, the network icon in the taskbar still shows "Connected 100 Mbps", but I cannot surf the web or do any online activity. I assumed that this was implemented by the university's network admins so that students could not use Limewire.

Currently, my Belkin Wireless G 2.4GHz 802.11g router is connected to the box while, my main desktop computer to the router via ethernet cable. (My laptop connects to the router wirelessly.) One day, in a moment of curiosity-turned sheer stupidity, I happened to start up Limewire again and my internet access gets promptly cut off. (As before, the taskbar icon shows "Connected 100 Mbps" but no real access.)

Then I checked my router's security log, and to my surprise found something unusual:

05/12/2006 20:05:25 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:05:24 **IP Spoofing** 212.241.77.155, 1321->> 192.168.2.2, 2440 (from WAN Inbound)
05/12/2006 20:05:24 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:05:22 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:05:14 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:05:12 **IP Spoofing** 82.35.58.232, 50301->> 192.168.2.2, 2439 (from WAN Inbound)
05/12/2006 20:05:10 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:05:07 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:05:06 **IP Spoofing** 82.35.58.232, 50301->> 192.168.2.2, 2439 (from WAN Inbound)
05/12/2006 20:05:03 **IP Spoofing** 82.35.58.232, 50301->> 192.168.2.2, 2439 (from WAN Inbound)
05/12/2006 20:04:59 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:55 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:53 **IP Spoofing** 68.20.19.75, 6346->> 192.168.2.3, 3595 (from WAN Inbound)
05/12/2006 20:04:53 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:51 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:51 **IP Spoofing** 80.111.191.71, 23531->> 192.168.2.2, 2438 (from WAN Inbound)
05/12/2006 20:04:47 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:45 **IP Spoofing** 80.111.191.71, 23531->> 192.168.2.2, 2438 (from WAN Inbound)
05/12/2006 20:04:44 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:43 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:42 **IP Spoofing** 80.111.191.71, 23531->> 192.168.2.2, 2438 (from WAN Inbound)
05/12/2006 20:04:41 **IP Spoofing** 67.102.33.10, 6346->> 192.168.2.3, 3586 (from WAN Inbound)
05/12/2006 20:04:40 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:38 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:38 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:38 **UDP Flood (per Min) Stop** (from WAN Outbound)
05/12/2006 20:04:37 **UDP Flood Stop** (from WAN Inbound)
05/12/2006 20:04:36 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:36 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:36 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:30 **IP Spoofing** 67.77.215.197, 80->> 192.168.2.2, 2437 (from WAN Inbound)
05/12/2006 20:04:28 **UDP Flood (per Min)** 192.168.2.3, 26197->> 12.240.6.219, 6346 (from WAN Outbound)
05/12/2006 20:04:28 **UDP flood** 192.168.2.3, 26197->> 12.240.6.219, 6346 (from WAN Outbound)
05/12/2006 20:04:28 **IP Spoofing** 67.77.215.197, 443->> 192.168.2.2, 2436 (from WAN Inbound)
05/12/2006 20:04:28 **IP Spoofing** 152.3.74.15, 6348->> 192.168.2.3, 3576 (from WAN Inbound)
05/12/2006 20:04:26 **IP Spoofing** 67.77.215.197, 29207->> 192.168.2.2, 2435 (from WAN Inbound)
05/12/2006 20:04:25 **IP Spoofing** 152.3.74.15, 6348->> 192.168.2.3, 3576 (from WAN Inbound)
05/12/2006 20:04:24 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:24 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:24 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:24 **IP Spoofing** 67.77.215.197, 80->> 192.168.2.2, 2437 (from WAN Inbound)
05/12/2006 20:04:23 **IP Spoofing** 198.53.94.3, 6346->> 192.168.2.3, 3574 (from WAN Inbound)
05/12/2006 20:04:23 **IP Spoofing** 12.240.6.219, 6346->> 192.168.2.3, 3568 (from WAN Inbound)
05/12/2006 20:04:22 **IP Spoofing** 69.222.137.138, 31042->> 192.168.2.3, 3572 (from WAN Inbound)
05/12/2006 20:04:22 **IP Spoofing** 67.77.215.197, 443->> 192.168.2.2, 2436 (from WAN Inbound)
05/12/2006 20:04:20 **IP Spoofing** 67.77.215.197, 29207->> 192.168.2.2, 2435 (from WAN Inbound)
05/12/2006 20:04:20 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:20 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:20 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:19 **IP Spoofing** 69.222.137.138, 31042->> 192.168.2.3, 3572 (from WAN Inbound)
05/12/2006 20:04:19 **IP Spoofing** 67.77.215.197, 443->> 192.168.2.2, 2436 (from WAN Inbound)
05/12/2006 20:04:18 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:18 **IP Spoofing** 220.245.174.118, 6348->> 192.168.2.3, 3571 (from WAN Inbound)
05/12/2006 20:04:18 **IP Spoofing** 67.77.215.197, 29207->> 192.168.2.2, 2435 (from WAN Inbound)
05/12/2006 20:04:17 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:17 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:17 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:17 **IP Spoofing** 12.240.6.219, 6346->> 192.168.2.3, 3568 (from WAN Inbound)
05/12/2006 20:04:09 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:09 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:09 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:05 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:05 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:05 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:05 **UDP Flood (per Min)** 192.168.2.3, 26197->> 70.35.112.86, 44257 (from WAN Outbound)
05/12/2006 20:04:05 **UDP flood** 192.168.2.3, 26197->> 70.35.112.86, 44257 (from WAN Outbound)
05/12/2006 20:04:05 **IP Spoofing** 24.83.86.248, 6346->> 192.168.2.3, 3561 (from WAN Inbound)
05/12/2006 20:04:04 **IP Spoofing** 68.255.163.252, 38005->> 192.168.2.3, 3560 (from WAN Inbound)
05/12/2006 20:04:03 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:03 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:04:03 **UDP Flood (per Min)** 192.168.2.3, 26197->> 71.242.91.62, 14689 (from WAN Outbound)
05/12/2006 20:04:03 **IP Spoofing** 24.86.91.47, 20960->> 192.168.2.3, 26197 (from WAN Inbound)
05/12/2006 20:04:02 **IP Spoofing** 24.215.76.22, 21833->> 192.168.2.3, 26197 (from WAN Inbound)
05/12/2006 20:04:02 **IP Spoofing** 65.78.10.94, 6349->> 192.168.2.3, 3554 (from WAN Inbound)
05/12/2006 20:04:02 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:04:01 **IP Spoofing** 24.83.86.248, 6346->> 192.168.2.3, 3561 (from WAN Inbound)
05/12/2006 20:04:01 **IP Spoofing** 68.255.163.252, 38005->> 192.168.2.3, 3560 (from WAN Inbound)
05/12/2006 20:04:00 **IP Spoofing** 69.161.45.3, 6346->> 192.168.2.3, 26197 (from WAN Inbound)
05/12/2006 20:03:56 **IP Spoofing** 65.78.10.94, 6349->> 192.168.2.3, 3554 (from WAN Inbound)
05/12/2006 20:03:54 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:53 **IP Spoofing** 65.78.10.94, 6349->> 192.168.2.3, 3554 (from WAN Inbound)
05/12/2006 20:03:50 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:48 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:48 **IP Spoofing** 207.150.179.24, 6350->> 192.168.2.3, 3551 (from WAN Inbound)
05/12/2006 20:03:47 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:43 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:41 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:39 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:36 **IP Spoofing** 65.184.200.31, 12363->> 192.168.2.3, 3534 (from WAN Inbound)
05/12/2006 20:03:35 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:33 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:32 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:30 **IP Spoofing** 192.168.1.1->> 192.168.1.11, Type:0, Code:0 (from WAN Inbound)
05/12/2006 20:03:29 **IP Spoofing** 69.223.148.166, 6348->> 192.168.2.3, 3526 (from WAN Inbound)
05/12/2006 20:03:28 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:26 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:24 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:20 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:18 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:17 **IP Spoofing** 70.242.14.130, 57827->> 192.168.2.2, 2428 (from WAN Inbound)
05/12/2006 20:03:16 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:13 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:11 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:11 **IP Spoofing** 70.242.14.130, 57827->> 192.168.2.2, 2428 (from WAN Inbound)
05/12/2006 20:03:09 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:08 **IP Spoofing** 70.242.14.130, 57827->> 192.168.2.2, 2428 (from WAN Inbound)
05/12/2006 20:03:05 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:04 **IP Spoofing** 68.20.19.75, 6346->> 192.168.2.3, 3508 (from WAN Inbound)
05/12/2006 20:03:03 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:03:01 **IP Spoofing** 68.20.19.75, 6346->> 192.168.2.3, 3508 (from WAN Inbound)
05/12/2006 20:03:01 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:58 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:56 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:55 **IP Spoofing** 69.143.130.163, 80->> 192.168.2.2, 2427 (from WAN Inbound)
05/12/2006 20:02:54 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:54 **IP Spoofing** 69.143.130.163, 443->> 192.168.1.11, 2426 (from WAN Inbound)
05/12/2006 20:02:52 **IP Spoofing** 69.143.130.163, 64339->> 192.168.2.2, 2425 (from WAN Inbound)
05/12/2006 20:02:50 **IP Spoofing** 192.168.1.1->> 192.168.1.11, Type:0, Code:0 (from WAN Inbound)
05/12/2006 20:02:49 **IP Spoofing** 69.143.130.163, 80->> 192.168.1.11, 2427 (from WAN Inbound)
05/12/2006 20:02:48 **IP Spoofing** 192.168.1.1->> 192.168.1.11, Type:0, Code:0 (from WAN Inbound)
05/12/2006 20:02:48 **IP Spoofing** 69.143.130.163, 443->> 192.168.2.2, 2426 (from WAN Inbound)
05/12/2006 20:02:47 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:46 **IP Spoofing** 69.143.130.163, 64339->> 192.168.2.2, 2425 (from WAN Inbound)
05/12/2006 20:02:46 **IP Spoofing** 67.102.33.10, 6346->> 192.168.2.3, 3477 (from WAN Inbound)
05/12/2006 20:02:45 **IP Spoofing** 69.143.130.163, 443->> 192.168.2.2, 2426 (from WAN Inbound)
05/12/2006 20:02:43 **IP Spoofing** 67.102.33.10, 6346->> 192.168.2.3, 3477 (from WAN Inbound)
05/12/2006 20:02:43 **IP Spoofing** 69.143.130.163, 64339->> 192.168.2.2, 2425 (from WAN Inbound)
05/12/2006 20:02:43 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:41 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:39 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:39 **UDP Flood (per Min) Stop** (from WAN Outbound)
05/12/2006 20:02:37 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:37 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:37 **UDP Flood Stop** (from WAN Inbound)
05/12/2006 20:02:36 **IP Spoofing** 192.168.1.1->> 192.168.1.11, Type:0, Code:0 (from WAN Inbound)
05/12/2006 20:02:35 192.168.2.3 login success
05/12/2006 20:02:33 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:33 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:33 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:32 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:32 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:32 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:31 **IP Spoofing** 74.131.147.91, 44428->> 192.168.2.2, 2424 (from WAN Inbound)
05/12/2006 20:02:31 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:30 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:30 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:29 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:29 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:29 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:29 **IP Spoofing** 152.3.74.15, 6348->> 192.168.2.3, 3445 (from WAN Inbound)
05/12/2006 20:02:28 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:28 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:28 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:26 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:26 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:26 **IP Spoofing** 192.168.1.1->> 192.168.1.11, Type:0, Code:0 (from WAN Inbound)
05/12/2006 20:02:25 **IP Spoofing** 74.131.147.91, 44428->> 192.168.2.2, 2424 (from WAN Inbound)
05/12/2006 20:02:24 **IP Spoofing** 192.168.1.1, 53->> 192.168.1.11, 32768 (from WAN Inbound)
05/12/2006 20:02:24 **UDP Flood (per Min)** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)
05/12/2006 20:02:24 **UDP flood** 192.168.1.11, 32768->> 192.168.1.1, 53 (from WAN Outbound)


The above goes on and on starting from the timestamp I started Limewire, which was about 9 hours ago.

My thoughts: Previously I had assumed that the disconnection was due to university policy on using Limewire, but now I wonder if the disconnection is due to intrusion from an external source via Limewire? Right now I have my computer connected directly to the internet box via cable, without using the router, and I can go online.

Any thoughts on what I can do to get my connection-via-router working again? Maybe changing the router's IP or MAC address will help?

Edited by Waterchan, 12 May 2006 - 09:27 PM.

  • 0

Advertisements


#2
coachwife6

coachwife6

    SuperStar

  • Retired Staff
  • 11,413 posts
Our site policy prohibits us from assisting with computers using P2P programs.
  • 0

#3
Waterchan

Waterchan

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
I assume it's ok for non-staff members of GeekstoGo to comment on these issues? If not, please feel free to delete or lock this thread.

no...it's not ok for non staffers to h elp with P2P problems here.

Edited by dsenette, 15 May 2006 - 10:25 AM.

  • 0

#4
Dan

Dan

    Trusted Tech

  • Retired Staff
  • 1,771 posts
Whilst I don't condone the use of P2P programs, as in most instances the user is using the application illegally, I have to say that the way these anti-P2P companies are going about dealing with the issue is not very appropriate. There are users out there using legitimate P2P applications, and flooding the networks is a poor way to go about dealing with the issue at hand.
  • 0

#5
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP

Whilst I don't condone the use of P2P programs, as in most instances the user is using the application illegally, I have to say that the way these anti-P2P companies are going about dealing with the issue is not very appropriate. There are users out there using legitimate P2P applications, and flooding the networks is a poor way to go about dealing with the issue at hand.

while it is ture that there are legitimate uses of P2P...if this is indeed a school network restriction (either by software or network configuration) it's that network's perogative for this to be in place

waterchan. as the original poster i woiuld suggest that you contact your schools network tech support group...they may be able to shed light on your situation as they will know what restrictions they have placed on their network
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP