Print

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

[Trikein]

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.

[FurryNutz]

Very Interesting. Oh well, so much for security LOL.

[Trikein]

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.

[FurryNutz]

Ya Ya, I still remember when 20Mb HD was big. I had 2. Hehe.

[mattlwil]

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

[zippoking]

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!!

[mattlwil]

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 >.<

[JoeScan]

You should check the levels of your modem and see if thats the problem first.

[FurryNutz]

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.

[mattlwil]

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.

[Trikein]

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.

[mattlwil]

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.

[FurryNutz]

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.

[Trikein]

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?

[mattlwil]

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.