Problems...
  • maliskmalisk December 2007
    I keep getting disconnected while playing CS. I either get a "Conection to server timed out" or a "connection timed out during map change" (when the map hadnt changed). I get disconnected from anywhere between right when I join to about 10 minutes after and ive tried three different servers all with the same problem. It was happening earlier and I suspected it had something to do with me installing some new sound drivers so I reinstalled windows and everything and its still happening....any ideas?
  • romerashromerash December 2007
    open a console (in xp go to start --> run --> cmd)

    type ping -t google.com

    leave it running for a while, see how many timeouts you get. If you get many timeouts then you're getting packet loss and should fight with your isp. ctrl+c anytime to stop it
  • maliskmalisk December 2007
    Microsoft Windows XP [Version 5.1.2600]
    © Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\b>ping -t google.com

    Pinging google.com [64.233.167.99] with 32 bytes of data:

    Reply from 64.233.167.99: bytes=32 time=79ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=51ms TTL=242
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=51ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=48ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=53ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=60ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=58ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=48ms TTL=242
    Request timed out.
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=60ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=52ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=48ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=54ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=46ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=59ms TTL=242
    Request timed out.
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=83ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=49ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=47ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=54ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=94ms TTL=242
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=50ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=52ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=49ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=53ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=49ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=58ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=52ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=53ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=73ms TTL=242
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=51ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=50ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=96ms TTL=242
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=62ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=60ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=56ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=48ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=60ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=50ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=58ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=56ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=53ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=54ms TTL=242
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=52ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=55ms TTL=242
    Request timed out.
    Reply from 64.233.167.99: bytes=32 time=88ms TTL=242
    Reply from 64.233.167.99: bytes=32 time=70ms TTL=242

    Ping statistics for 64.233.167.99:
    Packets: Sent = 63, Received = 52, Lost = 11 (17% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 96ms, Average = 57ms

    I'm guessing that counts as a lot?

    EDIT:I've done it 4 or five times let it run for about a minute each time and its always 16-18 percent loss. I pinged some cs server and its really low. Not sure why google is so high. Is this something the ISP can actually do something about?
  • MeatonMeaton December 2007
    This might just sound dumb.. but coming from me what else is not dumb when i type..

    Did this stuf fjsutjsut start happen after al lteh bad weath the midwest had gotten ? it could just be a bad conntions to server adns uch.. give it a few days unles this is been going on for some time..


    Meaton
  • maliskmalisk December 2007
    It started last night around 6 or 7 pm. I haven't heard of anyone else complaining of the problem though. Ill call my ISP but they'll probably just offer to send some one out next week to switch out my modem like they always do for every little problem.
  • BlueBoxBobBlueBoxBob December 2007
    There is some kind of test somewhere on the steam site and it tells you what is wrong with your connection. It helped when I had to open different ports for CS. I don't remember where I had found it but it could be usefull for you.
  • Kevbo2210Kevbo2210 December 2007
    Yea it sounds like it might be with your provider...I would just call them and see what they say to start
  • LethaLLethaL December 2007
    reading meaton's post almost give me a headache
This discussion has been closed.
← All Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

Categories