D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: vlj9r on August 21, 2010, 01:10:04 PM
-
Let me start by saying that I have 2 xbox 360s connected to my network via wire. One connects fine but the 192.168.x.xxx that has a gaming rule set up so that it can host games is suddenly having problems. THe gaming rule was set up as shown in the sticky.
Not sure why it's not able to allocate session and why it's dropping packets.
Thanks in advance,
Jerry
Here is the log.
Priority Time Message
[INFO] Sat Aug 21 16:02:34 2010 Log viewed by IP address 192.168.0.199
[INFO] Sat Aug 21 16:02:29 2010 Above message repeated 2 times
[INFO] Sat Aug 21 16:02:27 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:27 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:25 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:25 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:23 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:23 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:21 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:21 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:19 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:19 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:17 2010 Dropped packet from 192.168.0.194 to 255.255.255.255 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:17 2010 UPnP added entry 255.255.255.255 <-> 173.168.47.84:4500 <-> 192.168.0.194:4500 UDP timeout:0 'iC4500'
[INFO] Sat Aug 21 16:02:15 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:15 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:13 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:13 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:11 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:11 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:09 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:09 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:07 2010 Port forwarding ALG failed to allocate session for UDP packet from 192.168.x.xxx:3074 to 65.55.42.180:3074
[INFO] Sat Aug 21 16:02:07 2010 Dropped packet from 192.168.x.xxx to 65.55.42.180 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:06 2010 Dropped packet from 192.168.x.xxx to 255.255.255.255 (IP protocol 17) as unable to create new session
[INFO] Sat Aug 21 16:02:06 2010 UPnP added entry 255.255.255.255 <-> 173.168.47.84:3074 <-> 192.168.x.xxx:3074 UDP timeout:0 'Xbox (192.168.x.xxx:3074) 3074 UDP'
-
One of your 360's is automatically creating a port forwarding entry for port 3074 via UPnP, leaving the other one unable to use a manual forwarding entry for the same port (UPnP forwarding is taking precedence over manual forwarding in the case of a conflict - you cant map two different LAN IPs to the same external WAN port)
My recommendation is that you remove the manual forwarding entrie(s) for any/either 360 and simply let both 360's use UPnP's automatic forwarding...
Good luck.
-
I would recommend using the Gamefuel settings in the sticky. They work well.