Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mattlwil]

I'm going to tool around with this tomorrow. Both xboxes are playing COD right now >.<

Yes the .150 is IP and setup static on the wired box. Wireless is dynamic.

I'll let you know how it goes.

Thanks

[FurryNutz]

I recommend setting the wireless xbox to static IP as well.

[Trikein]

I am pretty sure if your setting up DHCP reseverations for devices per MAC, setting static IP in the device is redundant. I still do it because I find it makes the time it takes to connect less, but I don't think it improves performance in anyway. With that said, anytime you have gaming or gamefuel rules applied to a certian IP, you need to make sure there is some procedure in place so only that device gets that IP, whether that be DHCP reservations on the router or static IP's on the devices.

[mattlwil]

I got this today when testing connection.  I have not had a chance to play much lately but this is probably after 2-3 power cycles when it did this. Think I need to reset to default and start over?

I had to turn off Advanced Gaming rule to get it to download the new dashboard the other day and I had turned the xbox on/off probably 2-3 times since then. The setting were returned to same as before after I downloaded the update.

Thanks

[INFO]   Tue Jun 15 23:42:36 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:36 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:34 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:34 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:32 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:32 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:30 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:30 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:29 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:29 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:26 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:26 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:24 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:24 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:22 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:22 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:20 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:20 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:42:18 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:42:18 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:48 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:48 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:46 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:46 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:44 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:44 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:42 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:42 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:41 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:41 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:36 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:36 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:34 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:34 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:32 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:32 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:30 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:30 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:29 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:29 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:19 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:19 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:17 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:17 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:15 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:15 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:13 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:13 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:11 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:11 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:07 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:07 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:05 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:05 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:03 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:03 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:41:01 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:41:01 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO]   Tue Jun 15 23:40:59 2004   Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.150:3074 to 65.55.42.180:3074
[INFO]   Tue Jun 15 23:40:59 2004   Dropped packet from 192.168.0.150 to 65.55.42.180 (IP protocol 17) as unable to create new

[FurryNutz]

And the gameing and gamefuel sticky isn't helping? I don't use advanced gaming for a game console on my system here. Just gamefuel. What FW version is currently loaded?

Side note:
Seen that protocol 17 before with my friends ATT DSL service. We could not figure out where it was coming from. ISP said the signal noise on the line was coming from a neighbors signal and the line was dirty. Come to find out several things,
The line going into his house was not set up correctly and the dsl line was feeding back onto the phone line and getting interference which was on a separate wire and line and not being filtered correctly at the pole.

His ISP has set him up several thousand feet beyond acceptable DSL signal specs for the package he had which degraded the signal and would get disconnected frequently.

We both thought it might be the 4500 until I had him play xbox for a couple of days directly connected to the DSL modem. It finally disconnected him. We new the ISP had an issue. He even bought his own DSL modem and that did the same thing.

Finally he was able to get a tech out and saw what was going on and moved his line to a closer hub. Fixed the wiring issue and been good ever since.

I presume you cable signals are good and your getting good speeds and such on your system?

[Trikein]

Check your gaming rule? Almost looks like you have port forward for TCP only to port 3074 and not TCP and UDP.

[mattlwil]

I had some issues a few weeks ago with my connection again. Last Friday 11-01 a tech came out and observed packet loss on the upstream and escalated the problem to line maintenance. And of course when the issue gets escalated to line maintenance they do not give a estimated time for repairs but the connection appears to be fixed now as I have seen no problems this week.

53,80,3074 are forwarded under advanced gaming tab. I ran for awhile without any gaming rule. I don't remember if I just forgot to enable it or I had issues with it months ago and just left it off?

For now I will turn it off. I just turned on the xbox and same problem. This is after only one powercycle. I believe tomorrow if I get some time I will reset to default and set everything up exactly as the sticky says and put both xboxes on static. The other xbox is still dynamic and wireless with zero issues (as long as the ISP signal is good).

Thanks

[Trikein]

No, you misunderstood me. I didn't mean forwarding TCP causes a issue, it seems like your 360 wants UDP 3074 but either you don't, or you only have TCP and not set to both (TCP and UDP). A issue with the ISP would NOT cause those logs. Your issue may be causing your issues, and you don't NEED the port forwarding (if you using UPnP) but if your having issues with the 360 and your getting those logs, you need to fix your Gaming rules. Let us know if we can help.

[FurryNutz]

Keep It Simple, start with Static IP for the xbox, disable the gaming rule, set up the gamefule rule for the xbox, make sure uPnP is enabled. Check and make sure Primary and 2ndary DNS IP addresses are filled in the Basic/Internet/Manual section. DNS Relay should be enabled. You can also use 3074 for BOTH ports in gamefuel instead of 65535. Even thought this works, we can narrow it down to the specific port for XBL.