• February 24, 2025, 07:50:29 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: tcp packets  (Read 10891 times)

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
tcp packets
« on: December 27, 2009, 06:07:22 PM »

My router keeps blocking incoming tcp packets how can i fix this and please keep this simple becouse i am new to all of this.would post a copy of my logs but dount know how
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: tcp packets
« Reply #1 on: December 27, 2009, 06:49:28 PM »

just copy and paste ur logs from ur routers web page. Select and highlight the logs. My router does the same thing it blocks incoming packets. Is it blocking something that your using or a site your visiting? You can add sites to the firewall as to block or accept any connections too.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
Re: tcp packets
« Reply #2 on: December 27, 2009, 06:51:49 PM »

most of the time it blocks packets from xbox live
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: tcp packets
« Reply #3 on: December 27, 2009, 06:53:03 PM »

have you set up the gaming and gamefuel? I have set both of them up as I too play XBL.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
Re: tcp packets
« Reply #4 on: December 27, 2009, 07:02:47 PM »

hear is my log Message
[INFO] Sun Dec 27 21:59:31 2009 Log viewed by IP address 192.168.0.197
[INFO] Sun Dec 27 21:59:26 2009 Allowed configuration authentication by IP address 192.168.0.197
[INFO] Sun Dec 27 21:53:37 2009 UPnP added entry 255.255.255.255 <-> 192.168.1.15:3074 <-> 192.168.0.199:3074 UDP timeout:-1 'Xbox (192.168.0.199:3074) 3074 UDP'
[INFO] Sun Dec 27 21:49:40 2009 Wireless restart
[INFO] Sun Dec 27 21:37:33 2009 Above message repeated 4 times
[INFO] Sun Dec 27 21:34:39 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52445 with unexpected sequence 3451739927 (expected 3581317613 to 3581352653)
[INFO] Sun Dec 27 21:34:33 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52445 with unexpected sequence 3451739927 (expected 3581317612 to 3581352653)
[INFO] Sun Dec 27 21:34:30 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52445 with unexpected sequence 3451739927 (expected 3581325825 to 3581342210)
[INFO] Sun Dec 27 21:32:22 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52381 with unexpected sequence 50713672 (expected 630805084 to 630840125)
[INFO] Sun Dec 27 21:32:16 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52381 with unexpected sequence 50713672 (expected 630801842 to 630837261)
[INFO] Sun Dec 27 21:32:16 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 2564253194 (expected 3986801385 to 3986877306)
[INFO] Sun Dec 27 21:32:12 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52381 with unexpected sequence 50713672 (expected 630786448 to 630802833)
[INFO] Sun Dec 27 21:32:04 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 2564253194 (expected 3986801385 to 3986877306)
[INFO] Sun Dec 27 21:32:03 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 3119367901 (expected 3986801385 to 3986877306)
[INFO] Sun Dec 27 21:32:03 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 3170216997 (expected 3986801385 to 3986877306)
[INFO] Sun Dec 27 21:32:02 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52373 with unexpected sequence 898187076 (expected 2193179401 to 2193307882)
[INFO] Sun Dec 27 21:31:58 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 2564253194 (expected 3986801385 to 3986877306)
[INFO] Sun Dec 27 21:31:57 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 3119367901 (expected 3986801385 to 3986877306)
[INFO] Sun Dec 27 21:31:57 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 3170216997 (expected 3986801385 to 3986877306)
[INFO] Sun Dec 27 21:31:54 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 2564253194 (expected 3986765222 to 3986781607)
[INFO] Sun Dec 27 21:31:54 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 3119367901 (expected 3986765222 to 3986781607)
[INFO] Sun Dec 27 21:31:54 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52375 with unexpected sequence 3170216997 (expected 3986765222 to 3986781607)
[INFO] Sun Dec 27 21:31:51 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52374 with unexpected sequence 3080298463 (expected 1552083319 to 1552118360)
[INFO] Sun Dec 27 21:31:50 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52373 with unexpected sequence 898187076 (expected 2193179400 to 2193307881)
[INFO] Sun Dec 27 21:31:50 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52374 with unexpected sequence 2240703243 (expected 1552066505 to 1552101546)
[INFO] Sun Dec 27 21:31:49 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52373 with unexpected sequence 2548058782 (expected 2193179400 to 2193307881)
[INFO] Sun Dec 27 21:31:45 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52374 with unexpected sequence 3080298463 (expected 1552004765 to 1552039806)
[INFO] Sun Dec 27 21:31:44 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52373 with unexpected sequence 898187076 (expected 2193154679 to 2193190465)
[INFO] Sun Dec 27 21:31:44 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52374 with unexpected sequence 2240703243 (expected 1552002041 to 1552037082)
[INFO] Sun Dec 27 21:31:44 2009 Wireless restart
[INFO] Sun Dec 27 21:31:43 2009 Blocked incoming TCP packet from 199.93.43.126:80 to 192.168.1.15:52373 with unexpected sequence 2548058782 (expected 2193147379 to 2193190465)
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: tcp packets
« Reply #5 on: December 27, 2009, 07:05:31 PM »

What FW version are you currently using and what Hardware version is the router? Need to check and see if your gaming and gamefuel is set up.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
Re: tcp packets
« Reply #6 on: December 27, 2009, 07:07:01 PM »

Yes i have gameing and gamefuel setup for xbox . It will not let me connect to some of my freinds when me or them host or priv. chat but if someone else host a mitch we both can connect firmware 1.15
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: tcp packets
« Reply #7 on: December 27, 2009, 07:12:23 PM »

Heres my Gaming setup:
TCP Ports    UDP Ports    Schedule    Inbound Filter    
    3074      88, 3074      Always       Allow All

Heres my Gamefuel setp:
Name    Priority           Local IP Range           Remote IP Range            
xbox 360    1            6.x.x.x - 6.x.x.x    0.0.0.0 - 255.255.255.255

Protocol / Ports    
TCP
0 / 65535
0 / 65535

Firewall settings are ON and set for Endpoint for both UDP/TCP filtering.

Have you tried putting the xbox on the DMZ?
« Last Edit: December 27, 2009, 07:14:20 PM by FurryNutz »
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
Re: tcp packets
« Reply #8 on: December 27, 2009, 07:19:13 PM »

mine is the same but local and remote mine is 0.0.0.0-255.255.255.255 is that not right
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: tcp packets
« Reply #9 on: December 27, 2009, 07:21:44 PM »

local IP Range should be the address your xbox is on. I would set up a DHCP IP reservation so the IP address of the XBOX doesn't change, then set the Local IP Range to that reserved IP address.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
Re: tcp packets
« Reply #10 on: December 27, 2009, 07:29:09 PM »

what is DMZ and where do i find it ? i have done everythang else you said
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: tcp packets
« Reply #11 on: December 27, 2009, 07:31:06 PM »

DMZ is under Advanced/Firewall settings. Again, if you use that, put in the IP address of the xbox. You really shouldn't have to use that. Mines not on the DMZ, wondering if there could be something else. Well, let us know how it all works.
« Last Edit: December 27, 2009, 07:49:04 PM by FurryNutz »
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
Re: tcp packets
« Reply #12 on: December 27, 2009, 07:54:39 PM »

I will try that and see if it is any beter  thanks for your help one more thang how can i do all of this for xbox #2 and #3
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: tcp packets
« Reply #13 on: December 27, 2009, 07:58:23 PM »

Well, DMZ can only handle one item. I only have one xbox however a buddy of mine that I play xbox with, he said he had to reserve 3 Ip addresses for the boxes, then enter them or include them in the Local IP Range. You could enter each on into GameFuel if you wanted to do it that way. He just made one entry for his 3. I think He put his on the DMZ an the other 2 are not and just included in the Local IP Range. Works well for him. Play with him often.

Let me know if you'd like to connect on XBL and help sometime. PM me.
« Last Edit: December 27, 2009, 08:07:18 PM by FurryNutz »
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

theworm29070

  • Level 1 Member
  • *
  • Posts: 8
Re: tcp packets
« Reply #14 on: December 28, 2009, 02:47:45 PM »

TAHNKS for your help i will be getting on xbox a little latter to try it out . Send me a frends request my tag is the same as it is hear . I play a lot of M.W.2
Logged
Pages: [1] 2