D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: mattlwil on August 12, 2010, 11:39:50 AM
-
Does anyone else have to reset the router every once in awhile in order to get it to connect to the router? I have firmware 1.22NA and everything is setup verbatim to the sticky except a couple of the wireless settings.
I have 2 Xboxes, one wired, one wireless. The wired xbox is the one I have to reset the router for. The wired xbox is the only one with QoS setup for it via Gaming/Gamerfuel. I can leave the xbox on for a month straight no problems but when I start turning it on/off when I'm not using it every once in awhile it won't connect and I have to reset the router for it to reconnect. There are logs of the xbox trying to connect to the router under log details but I don't remember what exactly they say. But if I remember correctly it looked like the router was blocking all sessions from the xbox.
Thanks
-
There is a new firmware upgrade. 1.23 N/A ftp://ftp.dlink.com/Gateway/dgl4500/firmware/dgl4500_FW_123NA.zip (http://ftp://ftp.dlink.com/Gateway/dgl4500/firmware/dgl4500_FW_123NA.zip) But before you upgrade please troubleshoot the router. Simply follow FurryNutz he will guide you through. Only upgrade as your last resort!
-
I would keep 1.22NA for now, there is something in the configuration of the router that seems to be causing a hang. What are the wireless settings? How do they differ from whats in the sticky? I have a buddy using those Gamefuel rules and he's got 3 xboxes, 2 wired, 1 wireless and it works flawless on v1.22. Don't use the gaming section for the xboxes, only the gamefuel. What ISP service do you use, DSL or cable?
-
I am using the gaming section for port forwarding. You saying to turn that rule off?
Its just a minor nuisance, I have to reset it about every 1-3 weeks time. Usually I just leave the Xbox on all the time.
ISP=Comcast cable
ADVANCED WIRELESS SETTINGS
Transmit power= High
Beacon Period= 100
RTS Threshold : 2346
Fragmentation Threshold : 2346
DTIM Interval : 1
WLAN Partition : Un-checked
WMM Enable : Checked
Short GI : Checked
Extra Wireless Protection : Checked
WISH
Enable WISH : Checked
PRIORITY CLASSIFIERS
HTTP : Checked
Windows Media Center : Checked
Automatic : Checked
WI-FI PROTECTED SETUP
Enable : Checked
Lock Wireless Security Settings : Un-checked
WIRELESS NETWORK SETTINGS
Enable Wireless : Checked Always
Wireless Network Name : dlink
802.11 Band : 2.4GHz
802.11 Mode : 802.11g only
Enable Auto Channel Scan : Checked
Wireless Channel : 2.437 GHz- CH 6
Transmission Rate : Best (Automatic)
Visibility Status : Visible
WIRELESS SECURITY MODE
none
-
Straight up I noticed you do not have a wireless security mode. This is very crucial, It prevents people from connecting to the router and using your internet that you pay for. Unless you don't mind. Did I mention that this may also decrease performance? By having more people connected to the router this may also slow it down. But all things aside this ain't your problem. It is also very normal for the router to block certain things, that means the firewall is just doing its job.
-
Yes, you need to use GAMEFUEL settings for your consoles and don't use Gaming. Experience has let some of us to experience things as disconnections and improper game console connections to the services. You don't need the Gaming and ports there since GAMEFUEL will process this if you use the settings in the Sticky. Also ensure the SPI Firewall is ENDPOINT Independent for both UDP and TCP. If you don't need Protected WiFi or WISH I would turn them off as well. I have mine off and been working great. I even watch Netflix on my xbox. I would also try turning off SHORT GI and see if this helps you or not. Make sure you have reserved the IP addresses and make sure that the Primary and 2ndary DNS in Basic/Internet/Manual are filled in from the WAN section of Device Info. Sometimes they don't auto fill in. Your WiFi Band and Mode should work great.
-
You should also Reserver IP's to both xboxes.
-
I have MAC address filtering on and have all devices that connect to the router on the list. I assumed that any device not listed would not be able to connect, is that true?
Firewall is endpoint independent for both.
Also DNS is manualy entered from WAN info.
Which tab is the reserved IP under? I have the wired Xbox static address ending in .150. Wireless xbox has no QoS and is dynamic ip assigned.
-
I have MAC address filtering on and have all devices that connect to the router on the list. I assumed that any device not listed would not be able to connect, is that true?
Yes you are correct. Thanks for that info. I was looking out for you in terms of security and your router but it seems you already had that covered :D that is great news to me.
Which tab is the reserved IP under? I have the wired Xbox static address ending in .150. Wireless xbox has no QoS and is dynamic ip assigned.
Once you are at the login page, Navigate to Basic > NETWORKSETTINGS > NUMBER OF DYNAMIC DHCP CLIENTS:? Now you should be able to click Reserve and than save it on the tab above which its name is ADD DHCP RESERVATION. You should now see a list with the device that have been reserved. This list of course is named DHCP RESERVATIONS LIST. Have a great day.
--
Chris
-
Mac Address filtering doesn't do anything to block packet sniffing. All I have to do is cypher some data with your mac in it, clone my MAC to yours, then wait till your not offline. Not only can I go online with your time, I have access to any file and printer sharing you have set up and change any setting I wish (including adding my actual mac address to your list) If its your only way sure, but don't just do it that way because it's easier. Its your router though.
-
Alright, I turned port fowarding off and added my Mac and IP to the reserved list.
I am pretty new to wireless. I did everything I could to avoid going wireless but moving into an 1800 square ft house I had to go wireless on 1 Xbox or drill a hole through brick. The only device that uses wireless is the Xbox. Should security still be a concern with that?
Thanks
-
Unless you not near any one else or out in the country, I wouldn't recommend leaving the router open on security.
-
I agree. Its not the way I would suggest at all..and it may even be against his ISP's TOS. But its his router, soooooo. Plus security doesn't slow down connection down as much as people think. Its on a decently low level. It probably slows it down as much as SPI. And maybe even less depending on your signal quality.
-
It's only Brick drill that damn hole lol.
-
Well, I only think the security is only when your conecting and I don't think is a constant or remains running all the time. Just for connecting.
-
I am pretty sure most wireless security decripts the packets. WPA goes a extra step of confirming the keys at a certian group interval. Don't get me wrong, you can still inspect the packets, but there jumbled and encrpted. MAC filter on the other hand is trivial to decrypt. MAC addresses are sent in the clear and cloning yours is as easy as adjusting the advanced settings in your wireless NIC. It can literary be done with no tools in about 30seconds.
-
Very Interesting. Oh well, so much for security LOL.
-
Yea, I actually did this when I was in High School to play Everquest off the Teacher's lounge WiFi. Ahhh, the good ol' days.
-
Ya Ya, I still remember when 20Mb HD was big. I had 2. Hehe.
-
Ok, turned SPI on with endpoint independent for both. Turned on WPA2 for wireless, disabled anti spoof. I'll run it like this for awhile and if I still have problems, start from scratch.
My god does time fly. I was in XBL party chat just the other day and I was explaining why I didn't have a facebook account. There was no internet when I was in high school, or it was just coming out (1992-1995) LOL. I also use age as an excuse when I do bad in multiplayer. I say something to the effect "Hey, I'm playing with a handicap here, your hand/eye coordination and reaction time start slowing down after 25 years old!"
Thanks all
-
Hahaha, I'd like to use that excuse too but I think its more so the fact that you probably have a real job and can't play 12 hours/day, so really you're just inexperienced (relatively speaking of course).
Sorry, off topic!!
-
Looks like I'm getting booted off XBL every hour or so now. Its kind of acting like my modem is acting up again but there are no error logs in the modem. I had problems before with modem disconnects due to noise or ingress somewhere in the line. Message pops up saying dis from XBL, pull up the menu and reconnect, it reconnects right away.
I have not played any multiplayer yet to see if it just completely disconnects from rooms or not. I am trying to finish up a game right now and will get on multiplayer a little later to see what happens.
If I start getting disconnected from sessions I will restore router to default and setup everything from scratch >.<
-
You should check the levels of your modem and see if thats the problem first.
-
I would also check the cables going from the ISP modem to the 4500, shorter is recommended between these 2 units. Mines a 1fter. You could connect the xbox direct to the ISP modem and see if it does the same thing. It does sound like this could be an ISP issue. Sounds like the ISP modem is disconnecting or not able to maintain a good signal strength level. I would call the ISP and have a tech come out and check everything. I've seen this before with ISPs. Don't take no for answer either. Buddy of mine has DSL and ended up being the ISP issue and being well beyond the DSL limits. They fixed it. Let us know how it goes.
-
Everything is fine so far. I was out of town for a week but since I've been back all is well. The ISP must have been hiccuping again >.< I have Comcast and they have been upgrading a lot too so between my signal issues with the ISP AND the network upgrades AND the router issues just makes it that much harder to troubleshoot anything...
Check this link out W.A.S.P. (http://www.pcworld.com/article/203789/giant_wasp_sniffs_out_insecure_wifi.html)
-
Check your modem logs. Any "hippcups" will most likly be in there. But are you having problems between your PC and the 4500? Or just the 360 and your 4500. If the former, and disco and reco the connection in the 360 fixes it, I am more ****e to think its the 360.
-
There were no logs during the latest events last week in the modem. Before I would get t3 timeouts until enough stacked up then the modem would do a T4 reboot.
The modem logs for Comcasts SB 6120 firmware overwrites each other as they happen. Meaning you can only see one event. But if you contact Comcast directly they can see the multiple entries.
The T3's happen so fast that networking is impacted at a minimum. Only way I can see it on the PC is if I am actively browsing the web or I have a GPS program running that updates every 2 minutes and it will have a 'network problem' message pop up if there are problems.
Of course the xbox will let you know right away by diconnecting from xbl all together.
Back in March the problems were worse. They had just upgraded my area to DOCSIS 2.0 and I decided to get a DOCSIS 3 modem. Thats when the problems started. I contacted Comcast and they found noise in the line and supposedly fixed it but the problems still remained. I was able to get back on a DOCSIS 1.1 channel and the problems went away. I decided to stay on 1.1 for a few months to wait out problems with the upgrade. I hooked the DOCSIS 3 modem back up first of august and there are not near as many problems as before so the network is almost done being upgraded or the noise issue is less intermittent.
During this whole time the xbox would sometimes not connect to the network as described before, leading me to believe it was a separate problem.
Hope this helps.
-
wow, seems like you have been thru alot with Comcast. Heard various stories about them. Well if your seeing timeouts in the logs, that makes be think that the router is doing what its supposed to. It's reporting that it can't get any information from the cable modem and is timing out over and over and there could be a possibility that the router is designed to reboot if these time outs and connections are frequent and for long periods of time. It could be trying to reestablish the connection by rebooting itself. Not sure if this is the case. One idea. Honestly, seems like the cable ISP is at the root cause of all this. Buddy of mine has issues with DSL. Noise in the line, improper filtering on the lines and above all, his modem was well beyond the feet limit from the DSL hub for his speed so signal wasn't good to begin with. I would make sure all lines are good up to the house and ensure that you can reduce or remove all TV cable splitters if any on the internet line. I have a dedicated line to my house and nothing else on it. Let us know how it goes.
-
Sounds like maybe they found improper levels with your US SNR. That would be the one level you can see on your side. The fact that you even had someone looking at your logs at Comcast means either you found a competent Rep, were escalated to Tier 2 or even 2.5, or you know someone at the company. Comcast is good ISP overall if were talking infrastructure. There a bit tighter on the regulation then some others, but that comes from being the biggest kid on the block.
DOCSIS 3.0 can be a fickle beast. Even when your area is DOCIS 3.0 like mine, you still don't get as much monitoring on those bands as you do the DOCSIS 2.0 ones. Which means a storm can roll by, cause a problem, they fix it 90% but don't see the problem your having until months later.
But you said you havent seen T3 in your logs. So for the time being, I am going to say Comcast is in the clear. What about your router logs. What do they say at the time of the event?
-
Never paid attention to the router logs during an event. I will have to look at that next time.
Last T3 in the modem logs was Sunday afternoon about 6 o'clock. I get a couple a week but from what I have heard that is normal.
I don't know exactly what was wrong with the connection but they put a new drop from the pole to the house and as soon as the tech left the problems started again so I called them right back. Another tech showed up and just sat in his van on the phone with a supervisor and said they were able to see the problem real time while he was sitting there. Supposedly there was a line tech working in the area at the time fixing an issue and that's what they said was causing the problem.
Comcast Steve from dslreports.com is the employee I was dealing with. I actually requested for him to put me back on the D 1.1 channel because the D 2.0 channel was just terrible at the time.
I forgot to mention before, while troubleshooting I had my spare SB 5120 put on the account to rule out the modem. Thats the modem I had been running till the first of the month (August). When I put the 6120 back on the account it automatically locked onto a D 2.0 channel. I can say thats it a HELLUVA lot more stable now.
-
This is supposedly how the CMTS runs in "maintenance mode" (http://i66.photobucket.com/albums/h258/mattlwil/5120flux.jpg)
I captured this during a hiccup.
And here are some hiccups I captured over the months.The were accompanied by T3's.
(http://i66.photobucket.com/albums/h258/mattlwil/flux5-18.jpg)
(http://i66.photobucket.com/albums/h258/mattlwil/Belkinsame.jpg)
(http://i66.photobucket.com/albums/h258/mattlwil/routererror.jpg)
(http://i66.photobucket.com/albums/h258/mattlwil/DLpause.jpg)
While this was going on sometimes I would be playing COD and I would start lagging. So I would lay down and hit 'select' and watch the pings go to one red bar or it would boot me from the room altogether >.<
-
Hmm, probably the story you got from Comcast is half true. Alot of times they call it it to maintenance, but unless you have a maintenance ticket to track it, its not a official thing. Its like calling up your town and reporting a pot hole. Eventually it will get fixed, but it doesn't mean a guy is on your street the next day paving. Then again, usually you get a pretty good answer from DSL reports, so if he gave it a green light, that is good enough for me...for now.
As for your graphs, could you give me some context? From what I can find online, usually NetMeter measures from your NIC, your WAN(Router) and your Modem. Which is that for? Also I can find documentation on how it graphs upload vs download. And last, whats the X axis. Hours? MS? Is that per throttling cycle?
Also you might want to look into a program called Pingplotter. Netmeter looks to give your a capacity test, which is good, but there can be many reasons for speed decrease. Now if your doing a ping test along side of it to a IP inside your ISP's network (say their DNS or DHCP server) and see a latency spike next to a speed decrease, then you have black and white proof where the problem is. Ofcourse this is only relevant when you have a direct connection between the PC running the test and the modem.
Let me know about those graphs. Visually speaking, it looks like there could be something there. That looks too steady to be environmental (wind, storm,temp,etc). And where did you get that info on "maintenance mode"? Sounds like theres more to that story.
-
"I have 2 Xboxes, one wired, one wireless. The wired xbox is the one I have to reset the router for. The wired xbox is the only one with QoS setup for it via Gaming/Gamerfuel. I can leave the xbox on for a month straight no problems but when I start turning it on/off when I'm not using it every once in awhile it won't connect and I have to reset the router for it to reconnect. "
Actually, I think we may have gotten off topic here. Looking at your OP, it looks like the issue isn't intermident connetivity with the 360, but a issue with it not connecting when you turn it on and off? If so, I think someone else on this forum had a simular issue. Searched the forums and found this post:
http://forums.dlink.com/index.php?topic=14226.0
Problem:
The only strange thing is that every time I start up either XBox, it displays a message that it cannot connect to XBox Live. On that same message screen there is an option to test the XBox Live connection. Invariably, the test passes, and the XBox indicates that XBox Live is "Up and Running". With that step performed, I can connect to XBox Live as normal, and play away. I have now gotten into the habit of booting up the Xbox console, and skipping right to the network connection test screen before even attempting to log in with an XBox Live profile. It's an extra step that I would rather not have to perform each time.
Possible solution found:
I explained the problem to one of the systems guys at work and he said it sounded like a DNS problem. I looked through some XBox Live support forum posts, and hit on the following. On each of the XBox consoles, I changed the DNS settings from automatic to manual, and entered the appropriate primary and secondary DNS for my ISP. So far so good. No need to test the XBox Live connection before signing into an XBL profile.
-
Tricky, I have 2 xboxes and both are wired and have never had to reset the router. You shouldn't have to do this either. Makes me wonder why you do.
"I have 2 Xboxes, one wired, one wireless. The wired xbox is the one I have to reset the router for. The wired xbox is the only one with QoS setup for it via Gaming/Gamerfuel. I can leave the xbox on for a month straight no problems but when I start turning it on/off when I'm not using it every once in awhile it won't connect and I have to reset the router for it to reconnect. "
-
Here is what I found out about the x-axis for Net Meter. The chart can be configured to auto-scale to network activity levels, and you can specify the bandwidth per interface, but the time/x-axis can't be configured, making inspection of details at specific points in time challenging.
Those graphs were captured from my PC doing a multiple file download from dl.tv during a hiccup through the router. The "maintenance mode" graph is my PC direct to the modem. Steve on DSL reports mentioned that the graph looked like the CMTS was in maintenance mode. That's where I got that from.
I have a graph of an Upload speed test right here (http://i66.photobucket.com/albums/h258/mattlwil/2043.jpg)
I have pingplotter now. But I have not gotten a chance to use it.
I was on last.fm last night and got disconnected from live and it reconnected manually through the menu right away. I viewed modem and router logs and didn't see anything indicating a problem. I can post the router logs when I get home leading up to the disconnect.
-
Router logs minutes before the disconnect while using Last.fm. The last T3 on the modem logs was Aug 26th at 7:30 in the morning. There was another T3 on Aug 22nd at 6:30 P.M.
Log viewed by IP address 192.168.0.199
[INFO] Mon May 10 14:54:55 2004 Above message repeated 3 times
[INFO] Mon May 10 14:54:53 2004 Allowed configuration authentication by IP address 192.168.0.199
[INFO] Mon May 10 14:53:54 2004 Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:24760
[INFO] Mon May 10 14:52:45 2004 Above message repeated 8 times
[INFO] Mon May 10 14:50:01 2004 Blocked incoming TCP connection request from 58.218.204.110:12200 to 75.64.160.153:2301
[INFO] Mon May 10 14:50:01 2004 Blocked incoming TCP connection request from 58.218.204.110:12200 to 75.64.160.153:9090
[INFO] Mon May 10 14:50:01 2004 Blocked incoming TCP connection request from 58.218.204.110:12200 to 75.64.160.153:8080
-
Just got disc from last.fm. The other xbox which is wirelss is on COD currently, no problems. Just the wired xbox got booted. I'm also watching football via stream torrent on my PC and its still playing fine. I had netmeter screen up and didn't see any pauses or interruptions.
Router Logs
Tue May 11 12:34:58 2004 Log viewed by IP address 192.168.0.199
[INFO] Tue May 11 12:34:56 2004 Allowed configuration authentication by IP address 192.168.0.199
[INFO] Tue May 11 12:33:54 2004 Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32054
[INFO] Tue May 11 12:32:42 2004 Above message repeated 8 times
Booted again about 10 minutes after I signed back in.
Tue May 11 12:46:14 2004 Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32520
[INFO] Tue May 11 12:44:45 2004 Above message repeated 7 times
[INFO] Tue May 11 12:42:50 2004 Blocked outgoing TCP packet from 192.168.0.150:57632 to 195.24.232.207:443 as PSH:ACK received but there is no active connection
[INFO] Tue May 11 12:41:42 2004 Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:7212
[INFO] Tue May 11 12:41:42 2004 Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:8000
No modem logs.
No modem logs to report lol >.<
Got any ideas?
I suppose it could be a last.fm problem too eh?
-
Tricky, I have 2 xboxes and both are wired and have never had to reset the router. You shouldn't have to do this either. Makes me wonder why you do.
"I have 2 Xboxes, one wired, one wireless. The wired xbox is the one I have to reset the router for. The wired xbox is the only one with QoS setup for it via Gaming/Gamerfuel. I can leave the xbox on for a month straight no problems but when I start turning it on/off when I'm not using it every once in awhile it won't connect and I have to reset the router for it to reconnect. "
Oh, I wasn't saying I had that problem, please, me with a 360? Ppsssh. Hehe, J/k. I was quoting his orginal problem. And re-reading it it seemed like he only had a problem with the wired 360. And if that is the case, that makes it hard to be the modem. Could still be, but less likly. Also, I was quoting from someone who had a similar problem with DNS and having to run the connection test each time before connecting with the 360. It seemed relevant.
-
AH ok, got cha. Sure can get lost in some posts on here. LOL
-
Router Logs
Tue May 11 12:34:58 2004 Log viewed by IP address 192.168.0.199
[INFO] Tue May 11 12:34:56 2004 Allowed configuration authentication by IP address 192.168.0.199
[INFO] Tue May 11 12:33:54 2004 Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32054
[INFO] Tue May 11 12:32:42 2004 Above message repeated 8 times
Booted again about 10 minutes after I signed back in.
Tue May 11 12:46:14 2004 Blocked incoming UDP packet from 65.55.42.180:3074 to 75.64.160.153:32520
[INFO] Tue May 11 12:44:45 2004 Above message repeated 7 times
[INFO] Tue May 11 12:42:50 2004 Blocked outgoing TCP packet from 192.168.0.150:57632 to 195.24.232.207:443 as PSH:ACK received but there is no active connection
[INFO] Tue May 11 12:41:42 2004 Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:7212
[INFO] Tue May 11 12:41:42 2004 Blocked incoming TCP connection request from 122.227.164.71:6000 to 75.64.160.153:8000
Well your 75.64.160.153 and XBL is 65.55.42.180. Port 3074 is the port for XBL as per
http://support.xbox.com/support/en/us/nxe/kb.aspx?category=xboxlive&ID=908874&lcid=1033
So it looks like its a much simpler problem. Your router is blocking the port for 360. When it does, your 360 disconnects. Also found this post that might be relevant.
http://forums.dlink.com/index.php?topic=14654.0
Either way, can you post your Forwarding rules(or gamefuel if your using that instead) which can be found: http://192.168.0.1/Advanced/Gaming.shtml
PS. As for that TCP blocked, that belonged to some spam site out of China so..you can keep that one blocked LOL.
-
I really appreciate you guys looking into this.
Gaming isn't used as per the sticky.
Game Fuel Settings
Enable GameFuel : checked
Automatic Classification : checked
Dynamic Fragmentation : un-checked
Automatic Uplink Speed : checked
Measured Uplink Speed : 5507 kbps
Manual Uplink Speed : 128 kbps << 128kbps
Connection Type : Cable Or Other Broadband Network
Detected xDSL or
Other Frame Relay Network : No
Name Priority Local IP Range Remote IP Range Protocol / Ports
XBL1 1 192.168.0.150 - 192.168.0.150 0.0.0.0 - 255.255.255.255
Both
0 / 65535
0 / 65535
-
Yea, thats what I thought. We were overthunking it.
You need to forward specific ports, not just all of them..and all to one place.
"A GameFuel Rule identifies a specific message flow and assigns a priority to that flow. "
So it priotized traffic, it doesn't direct it. You still need to forward the connection from the WAN to the LAN. And then the gamerules priortize the traffic on your network. The thing is, both the PS3 and 360 have UPnP so most forwarding is redudent. If however you have a game fuel rule that conflicts with UPnP you need to set up a rule around it.
I will actually write up some instructions for you tommorow. I am beat right now. But yea, I think your problem is with that configuration.
-
Aight, I was thinking the same thing... crash time...
TTYL
-
You could do this, try changing the Protocol / Ports from 0/65535 to 3074 for both from and to. I have been experimenting and believe that Trikien is correct in that not all ports should be used. I have been using my 2nd xbox with the settings detailed in the gameing sticky however have set the protocol ports to be specific and to use 3074 for XBL. Been working just as good as the more global port setting. Give that a go and see how it it does. Let us know how it goes. Hope we can help.
-
First, my settings:
This is assuming 192.168.0.150 is your Xbox 360. If not, please replace each occurrence of that IP mentioned with your 360's IP. Also, this is assuming you have a DHCP reservation set for that IP and it is set as static on your 360's settings.
http://192.168.0.1/Advanced/Gaming.shtml
Enable: Yes
Name: Xbox Live
IP Address: 192.168.0.150
TCP Ports: 53, 80, 3074
UDP Ports: 53, 88, 3074
Schedule: Always
Inbound Filter: Allow All
http://192.168.0.1/Advanced/Traffic_Shaping.shtml
Enable: Yes
Name: Xbox Live 1
Priority: 96
Protocol: 257 << Both
Local IP Range: 192.168.0.150 to 192.168.0.150
Local Port Range: 3074 to 3074
Remote IP Range: 65.52.0.0 to 65.55.255.255
Remote Port Range: 3074 to 3074
Enable: Yes
Name: Xbox Live 2
Priority: 105
Protocol: 257 << Both
Local IP Range: 192.168.0.150 to 192.168.0.150
Local Port Range: 53 to 53
Remote IP Range: Your Primary DNS Server here to Your Second DNS Server here
Remote Port Range: 53 to 53
Note1: Here is a break down of which each port does:
Port 53 - DNS
Port 80 - HTTP (Website traffic)
Port 88 - Kerberos (Password system for Xbox Live)
Port 3074 - Xbox Live (Multi-player traffic)
TCP vs UDP: Think of TCP as being a walkie talkie and UDP being a phone. Each time your done saying something and before each time you go to say something with TCP you need to ask for permission. UDP doesn't do that. Not accurate, but just to give you a idea.
Note2: I set the priority to 96 and 105 for a reason. Alot of people make the mistake of setting this to one. QoS is traffic managerment. Another words, you have a finite amount of bandwidth and certian things trying to use it. Also, you have different bottlenecks of that bandwidth. A bottleneck is a point in the chain of connections from your Xbox to the game server you are connecting to, and back again, where the performces decreases. The point of QoS tagging is to try to move that bottleneck to inside your router where you have some control of it. Also, notice I set the IP range to a pretty wide birth since it was a unknown. All Xbox Live in the US gets routed somehow through Seatle WA servers, so most likly you could set it to 1-3 servers, but since 65.52.0.0 to 65.55.255.255 are all IP's ownder by Microsoft, I thought it was pretty safe. Just incase they have multiple servers or change them.
Note3: This is for 1 Xbox 360. If you have two, I suggest disabling the Gaming rule and allowing UPnP to manage the connection and have the Gamefuel settings set give priority to one connection and allow the other to defatlt to the 125 QoS priority to create separation of the streams to help prevent packet collision.
PS. As always, let me know how it works and I can advise it. Thanks
-
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
-
I recommend setting the wireless xbox to static IP as well.
-
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.
-
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
-
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?
-
Check your gaming rule? Almost looks like you have port forward for TCP only to port 3074 and not TCP and UDP.
-
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
-
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.
-
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.