I keep getting disconnected every couple of games. I shut off my Avast AV and it doesnt seem to help any. I am running wireless from a Linksys router that runs 802.11 B and G. Its in the other room but I never have an problems while surfing the net or playing other games online. Also when I exit out of CoD4 right after my internet seems to be down for a second or two then I can talk to people on Aim again and check out websites. Anyone else get this or have any ideas on how to fix it? Im thinking its something to do with the wireless but Im not 100% sure.
-
[img]http://img.photobucket.com/albums/v215/Mobojo/Sigs/Sig2.jpg[/img] -
Wish I could help you bud, as I've got 3 computers hanging off my
wireless, and haven't had any problems.
-
I will say that COD4 is very tolerant of network outage issues. Once in a great while my DSL modem freaks out ( like once a month). I can see it loses sync and has to resync. By the time my DSL modem has re-synced I'm amazed that COD4 hsn't booted me out of the game and I can actually keep player in the server.Comment
-
I haven't had that issue either, but I did notice once that I "thought" I was having a connection issue. I looked at my modem and my router, all looked fine, I could hear teammates talking, then I realized I was looking at the Kill Cam and my killer was having a connection issue!
There netcode does seem to work very well.
A change of Pace.
"All the fun of a clan without the BS" - CainComment
-
Hmm... I get disconnected at least once a gaming session. Like I said I usually have AIM running in the background so my usual check to see if im still connected is to try and check someone's info and I usually cant. Then after a minute or two im all fine and dandy. Plus I never actually lose the connection. It kinda seems like it is bottle necking and has to take a second to straighten back out.[img]http://img.photobucket.com/albums/v215/Mobojo/Sigs/Sig2.jpg[/img]Comment
-
can you hardwire directly to the modem and see what happens? If the issue still occurs it will eliminate the router as the cause of the problem then we can troubleshoot from there.Delivering bacon goodness one round at a time.Comment
-
Ill see what I can do later today.[img]http://img.photobucket.com/albums/v215/Mobojo/Sigs/Sig2.jpg[/img]Comment
-
you need to do a log report from your firewall or router to determine if there are any apps on your machine requesting packetss from a server.
Adware like HP's print suite does this
Quicken and Realplayre are offenders
Windows Update is an offender if you have it set wrong
Apple's iPod update utility does this
If you have 2 or more requests at once, depending again on your computer and the connection or port assignments, you can have the problems you described.Comment
-
Hmmm thats a little misleading. I't's not that you have two or more connections to other servers but, how much data is being sent or received. The best way to find out what type of network traffic your computers are generating is to load up a network sniffer and actually look at what packets are being sent. A free windows based utility is wiresharkOriginally posted by AngryHamster
http://www.wireshark.org/
This software will show you what packets are traversing the wire(or less).Comment
-
wow i wish i new as much about networks as you guys. I'm still a pup when it comes to networks. I't would sure help my competition if i knew what you guys knowComment
-
Originally posted by YetiChamp
Dude you wana learn about TCP/IP? Go and install wireshark. It will decode the packets running over your network. there are a couple of good online tutorials on TCP/IP networks as well ...just googleComment
-
Alrighty, ill try the wireshark program for next time im gaming. Will it save a log that I can go back and read through to see the network congestion and whats causing it?[img]http://img.photobucket.com/albums/v215/Mobojo/Sigs/Sig2.jpg[/img]Comment
-
What wireshark will show is all traffic on that segment of the network. You kinda have to learn how filter some of the traffic so you don't get overwhelmed.
Check out this
http://www.wireshark.org/news/20060714.htmlComment
Comment