• February 24, 2025, 06:27:21 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: [1] 2

Author Topic: Wireless restart in log  (Read 16188 times)

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Wireless restart in log
« on: September 14, 2010, 01:17:30 PM »

I am having some issues with my DGL-4500. The issue is with latency. My dad has his 3 computers directly connected to the router, and I have my laptop connected wirelessly. My dad plays WOW. Sometimes when he is playing he gets huge lag, and my laptop looses connection to the internet. We had Metrocast come over a few times to check the signal coming from the outside thinking the lag was from Metrocast. But everytime the signal is great. I checked the log and I noticed that the wireless is being reset every minute or so and that my HP laptop is being constanted connected. The IP address is not being changed. The issue disappears when I directly connect my laptop to the router, and I am now trying a USB Dlink wireless router. I am still seeing a wireless reconnects in the log, but I am not noticing any disconnects. Any suggestions on more troubleshooting?


Here is more information. WPA-Personal TKIP enabled. On the network the only devices that are constantly on are two desktops directly connected, an HP laptop, an iPhone, iPad, a Canon Wireless printer and an HP wireless printer. Other devices on the network include another wireless laptop, 4 wireless desktops, a PS3, 360, and a Wii. At the highest useage there is 2 laptops, 1 or 2 desktops, the PS3 or 350, iphone, ipad, and both wireless printers.
Logged

Trikein

  • Guest
Re: Wireless restart in log
« Reply #1 on: September 14, 2010, 02:48:15 PM »

That sounds like a pretty complex network. And if your running 2 laptops, 1 desktop, a 360 a Iphone and Ipad, thats a decent amount of traffic. I wouldn't worry so much about the lag, and focus more on the disconnects.

 One thing that raises a red flag with me is the "USB Dlink wireless router". Do you mean the wireless USB adapter?  If so, why? Why not just use the one that is internal? Not a big fan of USB adapters myself because they usually come with 3rd party utilities.

 My next question is what do the logs in the router and modem say at the time of the disconnects? And does your laptop ever disconnect even when he isn't playing WoW?
Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #2 on: September 14, 2010, 02:55:10 PM »

I was using the internal before. But I was doing some testing to see if the disconnects contiune with the Dlink USB wireless adapter which it does.

Here is a short sampling of my log:

230 Log Entries:
Priority   Time   Message
[INFO]   Tue Sep 14 17:54:08 2010   Blocked incoming TCP connection request from 24.68.73.156:3563 to 24.245.100.148:445
[INFO]   Tue Sep 14 17:54:06 2010   Allowed configuration authentication by IP address 192.168.0.194
[WARN]   Tue Sep 14 17:52:58 2010   A network computer (JoshLaptop7) was assigned the IP address of 192.168.0.194.
[INFO]   Tue Sep 14 17:52:58 2010   Moonraine: Wireless system with MAC address 00215D124E10 secured and linked
[INFO]   Tue Sep 14 17:52:58 2010   Moonraine: Wireless system with MAC address 00215D124E10 associated
[INFO]   Tue Sep 14 17:52:58 2010   Above message repeated 1 times
[INFO]   Tue Sep 14 17:52:56 2010   Wireless restart
[INFO]   Tue Sep 14 17:51:52 2010   Blocked outgoing TCP packet from 192.168.0.194:58840 to 207.46.96.145:80 as RST:ACK received but there is no active connection
[WARN]   Tue Sep 14 17:51:44 2010   A network computer (JoshLaptop7) was assigned the IP address of 192.168.0.194.
[INFO]   Tue Sep 14 17:51:44 2010   Moonraine: Wireless system with MAC address 00215D124E10 secured and linked
[INFO]   Tue Sep 14 17:51:44 2010   Moonraine: Wireless system with MAC address 00215D124E10 associated
[INFO]   Tue Sep 14 17:51:44 2010   Above message repeated 1 times
[INFO]   Tue Sep 14 17:51:42 2010   Wireless restart
[WARN]   Tue Sep 14 17:51:10 2010   A network computer (JoshLaptop7) was assigned the IP address of 192.168.0.194.
[INFO]   Tue Sep 14 17:51:10 2010   Moonraine: Wireless system with MAC address 00215D124E10 secured and linked
[INFO]   Tue Sep 14 17:51:10 2010   Moonraine: Wireless system with MAC address 00215D124E10 associated
[INFO]   Tue Sep 14 17:51:10 2010   Above message repeated 1 times
[INFO]   Tue Sep 14 17:51:08 2010   Wireless restart
[WARN]   Tue Sep 14 17:41:29 2010   A network computer (JoshLaptop7) was assigned the IP address of 192.168.0.194.
[INFO]   Tue Sep 14 17:41:29 2010   Moonraine: Wireless system with MAC address 00215D124E10 secured and linked
[INFO]   Tue Sep 14 17:41:29 2010   Moonraine: Wireless system with MAC address 00215D124E10 associated
[INFO]   Tue Sep 14 17:41:29 2010   Above message repeated 1 times
[INFO]   Tue Sep 14 17:41:26 2010   Wireless restart
[WARN]   Tue Sep 14 17:41:17 2010   A network computer (JoshLaptop7) was assigned the IP address of 192.168.0.194.
[INFO]   Tue Sep 14 17:41:17 2010   Moonraine: Wireless system with MAC address 00215D124E10 secured and linked
[INFO]   Tue Sep 14 17:41:17 2010   Moonraine: Wireless system with MAC address 00215D124E10 associated
[INFO]   Tue Sep 14 17:41:17 2010   Above message repeated 1 times
[INFO]   Tue Sep 14 17:41:15 2010   Wireless restart
[INFO]   Tue Sep 14 17:40:34 2010   Blocked incoming TCP connection request from 222.236.44.115:6000 to 24.245.100.148:2967
[INFO]   Tue Sep 14 17:40:23 2010   Blocked incoming TCP connection request from 24.245.100.70:50773 to 24.245.100.148:40080
[INFO]   Tue Sep 14 17:40:14 2010   Above message repeated 2 times
[INFO]   Tue Sep 14 17:40:02 2010   Blocked incoming TCP connection request from 24.245.100.70:50773 to 24.245.100.148:5900
[INFO]   Tue Sep 14 17:39:53 2010   Above message repeated 2 times
[INFO]   Tue Sep 14 17:39:41 2010   Blocked incoming TCP connection request from 24.245.100.70:50773 to 24.245.100.148:3389
[WARN]   Tue Sep 14 17:39:37 2010   A network computer (JoshLaptop7) was assigned the IP address of 192.168.0.194.
[INFO]   Tue Sep 14 17:39:37 2010   Moonraine: Wireless system with MAC address 00215D124E10 secured and linked
[INFO]   Tue Sep 14 17:39:37 2010   Moonraine: Wireless system with MAC address 00215D124E10 associated
[INFO]   Tue Sep 14 17:39:37 2010   Above message repeated 1 times
[INFO]   Tue Sep 14 17:39:35 2010   Wireless restart
Logged

Trikein

  • Guest
Re: Wireless restart in log
« Reply #3 on: September 14, 2010, 03:37:16 PM »

Well its a wireless restart, that could be cause by so many things. First thing I need to know is  the complete configuration of the wireless. So everything HERE and HERE.

Leaving out the SSID and Passphrase ofcourse. Also, does your laptop ever disconnect when the desktops aren't online? So far I am thinking interference, channel, or security. Which would seem to rule out traffic from the desktop. Can you confirm?
Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #4 on: September 14, 2010, 03:55:02 PM »

Tue Sep 14 2010 18:50:22 GMT-0400 (Eastern Daylight Time)
Firmware Version :1.22NA,  2010/01/19
WAN

Connection Type :DHCP Client
QoS Engine : Active
Cable Status :Connected
Network Status :Established
Connection Up Time :4 Day 0 Hour 11 Min 29 Sec
   
MAC Address :00:26:5A:D2:00:17
IP Address :24.245.100.148
Subnet Mask :255.255.255.0
Default Gateway :24.245.100.1
Primary DNS Server :156.154.119.11
Secondary DNS Server :156.154.129.11
Advanced DNS :Disabled
LAN

MAC Address :00:26:5A:D2:00:16
IP Address :192.168.0.1
Subnet Mask :255.255.255.0
DHCP Server :Enabled
WIRELESS LAN

Wireless Radio :Enabled
802.11 Mode : Mixed 802.11n, 802.11g and 802.11b
Channel Width :20MHz
Channel :11
WISH : Active
Wi-Fi Protected Setup :Enabled/Configured
SSID List

Network Name (SSID)   MAC Address   Security Mode
SSID   00:26:5a:d2:00:16    WPA Only - Personal
LAN COMPUTERS

IP Address   Name (if any)   MAC
192.168.0.179   Josuas-iPad   78:ca:39:dc:7e:5b
192.168.0.188   00:1e:8f:58:e0:a4
192.168.0.190   JoshLaptop7   1c:bd:b9:e3:4a:f5
192.168.0.193   Hatshepsut   00:1e:8c:8b:5a:ce
192.168.0.194   JoshLaptop7   00:21:5d:12:4e:10
192.168.0.195   Joshs-iPhone   04:1e:64:73:c3:41
192.168.0.197   Artemis-PC   00:1b:fc:b3:73:fc
192.168.0.198   SilverTower   00:23:54:89:b6:51
192.168.0.199   HP0DA5B3   f4:ce:46:0d:a5:b4

*************************************

Transmit Power : High
Beacon Period :(20..1000)
RTS Threshold :(0..2347)
Fragmentation Threshold :(256..2346)
DTIM Interval :(1..255)
WLAN Partition : Disabled
WMM Enable : Enabled
Short GI : Enabled

***************************************

Enable Wireless :   
Wireless Network Name :(Also called the SSID)
802.11 Band : 2.4GHz   5GHz
802.11 Mode : Mixed
Enable Auto Channel Scan : Disabled
Wireless Channel : 2.462 Ghz - 11
Transmission Rate : (Mbit/s) Best
Channel Width : 20
Visibility Status : Visible 
WIRELESS SECURITY MODE

Security Mode :
WPA

WPA Mode : WPA Only
Cipher Type : TKIP
Group Key Update Interval : (seconds) 3600
Logged

Trikein

  • Guest
Re: Wireless restart in log
« Reply #5 on: September 14, 2010, 06:39:29 PM »

Ok, I will give my best crack at this.

1.802.11 Mode: If possible, can you set it Mixed 802.11n, 802.11g? With the exception of maybe the Iphone, all those devices should be able to connect atleast at G right?

2.Enable Auto Channel Scan: Is there any reason you have a manual channel set in? Its sometimes needed, but usually Channel Scan is best.

3. Transmission Rate: Unless your doing alot of networking from computers to computers via the wireless connection, setting the MCS to 10 or below is usually a good idea. Anything over that is overkill and hurts wireless range and dependability.

4. Channel Width: 20/40 usually works better, atleast I have never run into a problem with it. Was this done intentionally? Since its not default.

5. WISH: We might turn this off later, once I understand the timing of the problem and your usage habits.

6. Short GI: Disable this. It might knock throughput down a bit, but if wireless interfence is a factor here, then the decrease in error rate is worth more.

7. WPA Mode: AES is going to get you a boost in performance and security. I assume some of the devices are not compatible? Maybe the Iphone and Printers?


Last, try to give more detail on the problem?
A. Does it ever happen when the desktops aren't online? Or aren't on WoW atleast?
B. Besides going hardwired to the router, does anything else resolve the issue? Power cycle of the router? reboot of the PC? Disabling and re-enabling the wireless connection?
C. Are there times when the desktop lag or loose connection when your not on your laptop?
D. Are there times when all computers loose connections?
E. Has this problem been occurring since the setup of the network? Or does it coincide with the addition or a change to the network?
F. Last, what are your Network Stats found Here
Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #6 on: September 16, 2010, 01:26:12 PM »

Ok I changed the 802.11 Mode to 802.11n, 802.11g. Iphone is G.

Auto Channel Scan enabled

Transmission mode is set to 10

Channel width has been set to Auto 20/40

Short GI disabled.

I remember reading somewhere in TKIP that it was better for gaming, but I can change it to AES.

Here is some additional testing. This morning I think I just had the laptop on, and I was getting the wireless disconnect. And in addition I assume the iPhone, iPad, and two wireless printers were online. I had made the change suggestions about. Current I only have a desktop one, and general background of iPhone, iPad, and wireless printers. So far I have not had any wireless disconnects since:

[INFO]   Sat Sep 11 04:26:49 2010   Wireless link is up

Now turning on HP laptop. So far I have not seen any wireless disconnects. I will monitor the log over the rest of the night.

Power cycling the modem/router does not resolve this issue.
Yes the desktops will lag or disconnect, but that could be the signal from Metrocast as well.
Yeah all computers do loose connection. Next time this happens I will immediately check the logs. This has been occuring since this model of router was inducted. This is the second one. The first one we removed because I was thinking the router was bad. We had a Linksys wireless router before and I do believe we had the same issues, although since then Metrocast has replaced all the wires from the street to the house, and I have done wire management to reduce interfere from other wires.

Here are my wireless stats

LAN Statistics

Sent :4737184

TX Packets Dropped :14

Collisions :0
   

Received :5447742

RX Packets Dropped :0

Errors :0
WAN Statistics

Sent :5452233

TX Packets Dropped :0

Collisions :0
   

Received :4903987

RX Packets Dropped :0

Errors :0
Wireless Statistics

Sent :1128

TX Packets Dropped :1

   

Received :607

RX Packets Dropped :0

Errors :63

Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #7 on: September 16, 2010, 03:46:05 PM »

After changing the settings I have received two wireless restarts at [INFO] Thu Sep 16 17:54:26 2010 Wireless restart and at [INFO] Thu Sep 16 18:07:24 2010 Wireless restart. I have not seen any other wireless restarts but I have reset my wireless stats are:

LAN STATISTICS

Sent :1900271
TX Packets Dropped :0
Collisions :0
Received :2036406
RX Packets Dropped :0
Errors :0
WAN STATISTICS

Sent :2532343
TX Packets Dropped :0
Collisions :0
Received :2402139
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS

Sent :673616
TX Packets Dropped :160
Received :685966
RX Packets Dropped :1
Errors :10514

Where do I see these 10514 errors?
Logged

Trikein

  • Guest
Re: Wireless restart in log
« Reply #8 on: September 16, 2010, 07:45:19 PM »

Hmm, well wireless errors aren't horrible. Their like potholes in the road. As long as they don't stop you from driving, your all set. In this case, as long as their not causing too many dropped packets, you should be good. But I think the error count is a symtom of the underlying problem. And I don't think its just one problem. Lets troubleshoot it one thing at a time. First wireless:

1. With all the wireless connections connected in their normal locations, go here and look at the signal levels to all the devices. Anything below 35-40%?

2. Next, Try to do something that demands heavy traffic, like transfer a 50+MB file from one PC to another. Or stream a couple Youtube videos. Then look at your wireless stats. If we can find a PC that is having more of a problem then the others, perhaps we can isolate it to a PC, or atleast a certain room.

3. Last, try disabling WISH, and setting your Beacon under Advanced Wireless Settings to 50.

Now for the wired connection problem. You said theres times where all your computers, wired and wireless, go down? What kind of modem do you have. Have you check it's logs? Its hard to troubleshoot wireless connections without a solid foundation. When you lose the connection, do the lights cycle on your modem? Give me some background on this problem. Thanks
Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #9 on: September 18, 2010, 03:08:07 PM »

1. I checked the wireless signal strength and at the moment the lowest is at 66%.

2. I started a download via Steam for a Civ 5. The only signal strength changes I notices was the HP and Canon printer signal strengths jumping down and up a bit. The lowest I saw was at 62%. I also checked which devices were connected:

Josuas-iPad    - Wireless - Active but not being used
58E0A4000000 - Wireless - Active but not being used
Artemis-PC
JoshLaptop7 - Wireless   - Being actively used
Joshs-iPhone - Wireless    - Active but not being used
SilverTower
Hatshepsut   
HP0DA5B3 - Wireless - Active but not being used

Also my dad is running 3 copies of WOW and his lag jumped up to 217 M/S with a download.   

3. I will adjust this setting later tonight or tomorrow. Dad gets mad when I disconnect him from WOW.

After talking with my Dad, when we loose connection the issue is with Metrocast. We loose connections on the modem. I am using a Motorola SB 6120.

I just did a quick search though the logs and I have not seen any wireless disconnects as of yet. I will need to do a more extensive search.
Logged

Trikein

  • Guest
Re: Wireless restart in log
« Reply #10 on: September 18, 2010, 10:36:51 PM »

Ok, well hopefully my suggestion helped decrease the problem, even if they didn't eliminate them. Yes, keep us updated. I always like a good challenge. But what I mean before was to try to use something with heavy traffic and then look for wireless errors under "WIRELESS STATISTICS" If you start doing something on one particular laptop, and see your wireless errors going up, then you know it either that connection, or that room. Then bring another laptop into the room and repeat. If no errors, hardware of laptop or settings. If still errors, likly wireless interfence. I am sure that is easier said then done though since your dealing with a hostile element (you day,heh). Trust me...I know ALLLLLLL about trying to help people and them getting pissed. It sucks.

Oh, and BTW, if anything AES is better for gaming since the encryption is done by the hardware of your wireless NIC rather then the software. To be honest though, you probably won't see any difference and it is much more secure.
Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #11 on: September 19, 2010, 05:31:28 AM »

My Beacon is set to 100. Should I decrease it it to 50?
Logged

Trikein

  • Guest
Re: Wireless restart in log
« Reply #12 on: September 19, 2010, 10:37:40 AM »

 Beacon Period
Beacons are packets sent by a wireless router to synchronize wireless devices. Specify a Beacon Period value between 20 and 1000. The default value is set to 100 milliseconds.

From the Dlink's help page. So if your having a hard time with a device dropping a channel and lossing the connection, it "could" help. But if your problem has gone away, I wouldn't touch it. Were you ever able to look at the modem logs and see if you see anything in those logs that match the timing of the disconnects in the router's logs? To go to the modem logs go here. Nevermind if some of the dates say 1970, just try to guesstimate for those based on the time stamps above and below. Most DHCP systems don't broadcast Time of Day (TOD), so the modem logs get confused.
Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #13 on: September 22, 2010, 05:26:28 PM »

Ok I was having some more issues with connections. My dad and my niece were playing WOW on the two of the directly connected computers and I was trying to update some of my apps in iTunes, and check the logs on the wireless router. I was able to get to the website, but when I checked the logs I receive the message that the memory was low.Then I was disconnected. Windows attempted to reconnect a few times, and then failed. I manually had to reconnect. This happen twice before the directly connected computers lost connect. Both computer gain connected shortly. I stopped trying to access the wireless router, and anything internet base. My computer did not connect. Once my dad and niece got out of a dungeon, I was able to get the logs but I did not see anything about a disconnect. The only thing I saw was a time sync at 600. The disconnect occurred around 815ish. Any suggestions? Add logs, and wireless stats in next post.
Logged

herrjosua

  • Level 1 Member
  • *
  • Posts: 16
Re: Wireless restart in log
« Reply #14 on: September 22, 2010, 05:27:38 PM »

Have to break logs into different post

***** Logs*****

[INFO] Wed Sep 22 20:14:09 2010 Log viewed by IP address 192.168.0.194
[INFO] Wed Sep 22 20:14:07 2010 Allowed configuration authentication by IP address 192.168.0.194
[INFO] Wed Sep 22 20:13:49 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50729 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:49 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50719 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:49 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50729 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:48 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50719 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:48 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50729 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:48 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50719 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:47 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50701 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:46 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:13:46 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50706 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:45 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:13:43 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50703 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:43 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50702 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:42 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50703 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:42 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50702 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:42 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50703 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:13:42 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50702 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:25 2010 Blocked incoming TCP connection request from 24.245.123.173:4159 to 24.245.100.148:445
[INFO] Wed Sep 22 20:12:25 2010 Blocked incoming TCP connection request from 24.245.123.173:4158 to 24.245.100.148:445
[INFO] Wed Sep 22 20:12:23 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50607 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:23 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50603 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:23 2010 Above message repeated 1 times
[INFO] Wed Sep 22 20:12:23 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50607 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:23 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50603 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:23 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50607 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:22 2010 Blocked incoming TCP packet from 65.175.141.209:80 to 24.245.100.148:50643 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:22 2010 Blocked incoming TCP connection request from 24.245.123.173:4159 to 24.245.100.148:445
[INFO] Wed Sep 22 20:12:22 2010 Blocked incoming TCP connection request from 24.245.123.173:4158 to 24.245.100.148:445
[INFO] Wed Sep 22 20:12:22 2010 Blocked incoming TCP packet from 65.175.141.209:80 to 24.245.100.148:50643 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:21 2010 Above message repeated 1 times
[INFO] Wed Sep 22 20:12:20 2010 Blocked incoming TCP packet from 65.175.141.202:80 to 24.245.100.148:50645 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:19 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:12:16 2010 Blocked incoming TCP packet from 65.175.141.209:80 to 24.245.100.148:50641 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:16 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:12:14 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50661 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:13 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:12:12 2010 Blocked incoming TCP packet from 65.175.141.208:80 to 24.245.100.148:50644 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:10 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:12:07 2010 Blocked incoming TCP packet from 65.175.141.209:80 to 24.245.100.148:50642 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:07 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:12:06 2010 Blocked incoming TCP packet from 65.175.141.209:80 to 24.245.100.148:50602 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:12:05 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:11:59 2010 Blocked incoming TCP packet from 65.175.141.209:80 to 24.245.100.148:50637 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:11:59 2010 Above message repeated 2 times
[INFO] Wed Sep 22 20:10:14 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50717 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:11 2010 Blocked incoming TCP packet from 173.194.33.100:443 to 24.245.100.148:50728 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:11 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50716 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:09 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50713 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:09 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50714 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:07 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50723 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:05 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50718 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:05 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50722 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:05 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50708 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:04 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50717 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:02 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50724 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:01 2010 Blocked incoming TCP packet from 173.194.33.100:443 to 24.245.100.148:50728 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:10:01 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50716 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:59 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50713 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:59 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50714 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:57 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50723 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:55 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50718 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:55 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50722 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:55 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50708 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:54 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50717 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:52 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50724 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:51 2010 Blocked incoming TCP packet from 17.152.19.34:443 to 24.245.100.148:50698 as FIN:PSH:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:51 2010 Blocked incoming TCP packet from 173.194.33.100:443 to 24.245.100.148:50728 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:51 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50716 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:49 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50713 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:49 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50714 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:47 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50723 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:45 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50718 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:45 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50722 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:45 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50708 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:44 2010 Blocked incoming TCP packet from 173.194.34.100:80 to 24.245.100.148:50715 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:44 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50717 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:43 2010 Blocked incoming TCP packet from 17.152.19.34:443 to 24.245.100.148:50698 as FIN:PSH:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:42 2010 Blocked incoming TCP packet from 173.194.35.100:80 to 24.245.100.148:50712 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:42 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50724 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:41 2010 Blocked incoming TCP packet from 173.194.34.100:80 to 24.245.100.148:50721 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:41 2010 Blocked incoming TCP packet from 173.194.33.100:443 to 24.245.100.148:50728 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:41 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50716 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:39 2010 Blocked incoming TCP packet from 17.152.19.34:443 to 24.245.100.148:50698 as FIN:PSH:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:39 2010 Blocked incoming TCP packet from 173.194.33.132:80 to 24.245.100.148:50713 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:39 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50714 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:38 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50723 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:37 2010 Blocked incoming TCP packet from 17.152.19.34:443 to 24.245.100.148:50698 as FIN:PSH:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:36 2010 Above message repeated 1 times
[INFO] Wed Sep 22 20:09:36 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50718 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:36 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50722 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:36 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50708 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:35 2010 Blocked incoming TCP packet from 173.194.34.100:80 to 24.245.100.148:50715 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:35 2010 Blocked incoming TCP packet from 74.125.127.101:80 to 24.245.100.148:50717 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:35 2010 Blocked incoming TCP packet from 173.194.33.100:443 to 24.245.100.148:50728 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:35 2010 Blocked incoming TCP packet from 173.194.33.104:80 to 24.245.100.148:50724 as FIN:ACK received but there is no active connection
[INFO] Wed Sep 22 20:09:34 2010 Blocked incoming TCP packet from 173.194.34.100:80 to 24.245.100.148:50721 as FIN:ACK received but there is no active connection
Logged
Pages: [1] 2