Giga Lan Problem

Hi all .

I have a Network Cafe 21 Pc , and a switch 1000/100/10 ,i Connected the cables and windows gave me the 1 Gb lan Connected , when users play Any game like fifa or Counter against the pc the game doesnt lag , but when they play it multiplayer on the local network it laggs , not all the pc together but Randomly.

when i ping a pc i get this result:

ping 192.168.1.8

Pinging 192.168.1.8 with 32 bytes of data:

Reply from 192.168.1.8: bytes=32 time=2ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms

is this Normal?

My Switch is Assus and Cables are Cat6
Pc Spec:
P 3.4 2Mb*2 Cach
Assus P5pld2
1 Gb DDr2
256 mb X1600 pro
250 Gb Sata II

What is happening? all my Pc are high end and got a very good specification

Plz help
2 answers Last reply
More about giga problem
  1. Looks pretty normal to me. The first packet where the connection is established is 2ms, the rest all show <1ms.

    The PING command does not give values in nano seconds... it's just not intended as a precision packet measurement tool.
  2. you could try running this tool on both of the pcs

    http://dast.nlanr.net/Projects/Iperf/

    run one wiht

    ipeft -c IP_OF_SERVER

    and the other

    iperf -s

    to run it as server


    Quote:

    iperf.exe" --help
    Usage: iperf [-s|-c host] [options]
    iperf [-h|--help] [-v|--version]

    Client/Server:
    -f, --format [kmKM] format to report: Kbits, Mbits, KBytes, MBytes
    -i, --interval # seconds between periodic bandwidth reports
    -l, --len #[KM] length of buffer to read or write (default 8 KB)
    -m, --print_mss print TCP maximum segment size (MTU - TCP/IP header)
    -o, --output <filename> output the report or error message to this specifie
    d file
    -p, --port # server port to listen on/connect to
    -u, --udp use UDP rather than TCP
    -w, --window #[KM] TCP window size (socket buffer size)
    -B, --bind <host> bind to <host>, an interface or multicast address
    -C, --compatibility for use with older versions does not sent extra msgs
    -M, --mss # set TCP maximum segment size (MTU - 40 bytes)
    -N, --nodelay set TCP no delay, disabling Nagle's Algorithm
    -V, --IPv6Version Set the domain to IPv6

    Server specific:
    -s, --server run in server mode
    -D, --daemon run the server as a daemon
    -R, --remove remove service in win32

    Client specific:
    -b, --bandwidth #[KM] for UDP, bandwidth to send at in bits/sec
    (default 1 Mbit/sec, implies -u)
    -c, --client <host> run in client mode, connecting to <host>
    -d, --dualtest Do a bidirectional test simultaneously
    -n, --num #[KM] number of bytes to transmit (instead of -t)
    -r, --tradeoff Do a bidirectional test individually
    -t, --time # time in seconds to transmit for (default 10 secs)
    -F, --fileinput <name> input the data to be transmitted from a file
    -I, --stdin input the data to be transmitted from stdin
    -L, --listenport # port to recieve bidirectional tests back on
    -P, --parallel # number of parallel client threads to run
    -T, --ttl # time-to-live, for multicast (default 1)

    Miscellaneous:
    -h, --help print this message and quit
    -v, --version print version information and quit

    [KM] Indicates options that support a K or M suffix for kilo- or mega-

    The TCP window size option can be set by the environment variable
    TCP_WINDOW_SIZE. Most other options can be set by an environment variable
    IPERF_<long option name>, such as IPERF_BANDWIDTH.

    Report bugs to <dast@nlanr.net>
Ask a new question

Read More

LAN Networking