Articles

Router Keeps Disconnecting Recently

January 10, 2005 at 10:19:36
Specs: xp, NA

Our 3com wireless/lan router keeps disconnecting at the moment. The only way to re-connect it is to access it directly and tell it to connect through the options. This never used to be a problem and it worked just fine. Is there a single reason why this might have been the case? I don't think any settings have been changed whatsoever.

This is the log from the router, I wasn't sure how much of this to disclose so I've replaced the IPs with DELETED. Also, I think 192.168.1.1 - 192.168.1.4 etc are just local, would that be correct?

Logs:
This page shows any attempts that have been made to gain access to your network as well as the system activities. Pressing "Refresh" will update the list.

Security Log
2005.01.10 18:11:08 ATM get IP:DELETED
2005.01.10 18:11:02 ATM start PPP
2005.01.10 18:11:02 Dial On Demand(ATM)
2005.01.10 18:10:16 192.168.1.4 login success
2005.01.10 18:10:12 User from 192.168.1.4 timed out
2005.01.10 17:30:25 ATM stop PPP
2005.01.10 17:10:22 ATM get IP:DELETED
2005.01.10 17:10:18 ATM start PPP
2005.01.10 17:09:31 192.168.1.4 login success
2005.01.10 17:09:27 User from 192.168.1.4 timed out
2005.01.10 17:03:29 sending ACK to 192.168.1.4
2005.01.10 17:03:25 sending ACK to 192.168.1.4
2005.01.10 15:36:50 ATM stop PPP
2005.01.10 15:12:20 sending ACK to 192.168.1.4
2005.01.10 15:12:18 sending ACK to 192.168.1.4
2005.01.10 15:07:58 ATM get IP:DELETED
2005.01.10 15:07:53 ATM start PPP
2005.01.10 15:07:15 192.168.1.4 login success
2005.01.10 15:07:09 User from 192.168.1.4 timed out
2005.01.10 15:05:37 sending ACK to 192.168.1.4
2005.01.10 12:54:50 ATM stop PPP
2005.01.10 12:34:41 sending ACK to 192.168.1.4
2005.01.10 11:54:56 sending ACK to 192.168.1.4
2005.01.10 11:46:46 ATM get IP:DELETED
2005.01.10 11:46:37 ATM start PPP
2005.01.10 11:43:17 ATM get IP:DELETED
2005.01.10 11:43:11 ATM start PPP
2005.01.10 11:43:11 Dial On Demand(ATM)
2005.01.10 11:42:58 192.168.1.4 login success
2005.01.10 11:37:36 sending ACK to 192.168.1.4
2005.01.10 11:27:31 sending ACK to 192.168.1.4
2005.01.10 11:27:26 sending ACK to 192.168.1.4
2005.01.10 09:09:37 ATM stop PPP
2005.01.10 06:56:27 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:41:48 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:41:34 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:31:12 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:30:55 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:16:56 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:09:46 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:09:30 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:03:15 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 06:02:56 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:56:38 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:50:42 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:50:17 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:23:56 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:23:37 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:23:04 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:22:45 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:17:53 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:17:28 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:17:16 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 05:12:47 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:45:28 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:45:08 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:38:06 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:31:57 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:24:36 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:18:04 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:17:43 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:17:20 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:12:03 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:11:48 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:06:05 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.10 04:05:44 **IP Spoofing** 192.168.1.101, 3702->> 192.168.1.2, 6881 (from ATM Inbound)
2005.01.09 23:57:58 sending ACK to 192.168.1.6
2005.01.09 22:40:52 sending ACK to 192.168.1.4
2005.01.09 22:40:48 sending ACK to 192.168.1.4
2005.01.09 22:21:50 sending ACK to 192.168.1.4
2005.01.09 22:16:42 sending ACK to 192.168.1.6
2005.01.09 22:15:17 sending ACK to 192.168.1.4
2005.01.09 22:15:15 sending ACK to 192.168.1.4
2005.01.09 22:13:39 sending ACK to 192.168.1.4
2005.01.09 22:13:37 sending ACK to 192.168.1.4
2005.01.09 21:06:25 sending ACK to 192.168.1.4
2005.01.09 21:06:25 sending OFFER to 192.168.1.4
2005.01.09 21:06:22 sending OFFER to 192.168.1.4
2005.01.09 19:47:40 sending ACK to 192.168.1.3
2005.01.09 19:47:40 sending OFFER to 192.168.1.3
2005.01.09 15:13:16 192.168.1.2 logout
2005.01.09 15:13:11 ATM get IP:83.151.205.134
2005.01.09 15:13:06 ATM start PPP
2005.01.09 15:13:06 Dial On Demand(ATM)
2005.01.09 15:13:03 192.168.1.2 login success
2005.01.09 15:08:12 sending ACK to 192.168.1.2
2005.01.09 14:19:31 ATM stop PPP
2005.01.09 13:13:44 NTP Date/Time updated.
2004.09.30 19:19:30 ATM get IP:83.151.205.134
2004.09.30 19:19:24 ATM start PPP
2004.09.30 19:19:06 sending ACK to 192.168.1.6




See More: Router Keeps Disconnecting Recently

Report •


#1
January 10, 2005 at 11:30:51

192.168.whatever is a private IP. Your logs show that the router also runs a private IP, your modem perhaps?

I've had this problem occurr a couple of times during inclement weather. A power cycle was all my router needed to run correctly.


Report •

#2
January 10, 2005 at 11:57:22

Here at work we are having an increasing number of calls with the same random disconnect problems. One major reason is that an increasing number of folks are using w/less setups WITHOUT ENCRYPTION, and they are getting crosstalk which causes random disconnection because there are several other wireless routers in the same building. You might check out if your system is encrypted.

Give a man a fish and you feed him for a day;
Teach a man to fish and you feed him for a lifetime;
Then industry pollutes the water and kills all the fish.


Report •

#3
January 10, 2005 at 12:54:09

What do you mean by inlement weather? We've had bad weather recently, but not in this area, it doesn't look like a power problem.

The router is encrypted with a network key, also it has 128 bit web enabled.


Report •

Related Solutions

#4
January 14, 2005 at 12:10:17

I'm getting this now, does this mean anything to anyone?

2005.01.14 17:12:17 **SYN Flood to Host** 192.168.1.4, 1700->> 38.113.207.80, 80 (from ATM Outbound)


Report •

#5
January 14, 2005 at 13:00:20

A SYN flood to host is a denial of service attack. It appears to have been initiated by a computer on your network. IP address 192.168.1.4. Find out which computer is using that IP and deal with the nasties which seem to have installed themselves there.

38.113.207.80 is a teenage pornography site. This appears to be the target of this attack.


Report •


Ask Question