« zurück zur Hauptseite...


Connect dauert lange

Autor: Boris Kirkorowicz

Hallo,
mich ärgert die lange Zeit, die mein ASUS WL-330g (im Ethernet-Adapter
Modus) braucht, um zu dem ASUS WL-300g AP eine stabile Verbindung
aufzubauen. Das sind nach dem Start des PC stets mehrere Minuten. Dabei
ist der erste Kontakt bereits nach wenigen Sekunden da, nur reißt er
immer wieder ab, und bis die Verbindung endlich brauchbar steht, dauert
es nervend lang. Im CMD-Fenster sieht ein Ping auf das Gateway kurz nach
dem Start des PC so aus:

==============================SCHNIPP==============================
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>ping -t 192.168.2.254

Pinging 192.168.2.254 with 32 bytes of data:

Reply from 192.168.2.254: bytes2 time6ms TTLc
Reply from 192.168.2.254: bytes2 time=9ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=7ms TTLc
Reply from 192.168.2.254: bytes2 time=14ms TTLc
Reply from 192.168.2.254: bytes2 time=7ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=9ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=7ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=4ms TTLc
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Reply from 192.168.2.254: bytes2 time=6ms TTLc
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc

Ping statistics for 192.168.2.254:
Packets: Sent = 84, Received = 38, Lost = 46 (54% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 36ms, Average = 5ms
Control-C
^C
C:\>
==============================SCHNAPP==============================

Wie kann man das bessern?


Gruss Greetings
Boris Kirkorowicz

--
Mail im HTML-Format wird nicht gelesen. Die Adresse gilt bis 31.01.05
Danach bitte das Formular unter http://www.kirk.de/mail.shtml nutzen.
eMail containing HTML will not be read. This address expires 31 Jan 05.
After this date, use the form at http://www.kirk.de/mail.shtml

Connect dauert lange

Autor: Admin

Connect dauert lange

Autor: Boris Kirkorowicz

Hallo,
mich ärgert die lange Zeit, die mein ASUS WL-330g (im Ethernet-Adapter
Modus) braucht, um zu dem ASUS WL-300g AP eine stabile Verbindung
aufzubauen. Das sind nach dem Start des PC stets mehrere Minuten. Dabei
ist der erste Kontakt bereits nach wenigen Sekunden da, nur reißt er
immer wieder ab, und bis die Verbindung endlich brauchbar steht, dauert
es nervend lang. Im CMD-Fenster sieht ein Ping auf das Gateway kurz nach
dem Start des PC so aus:

==============================SCHNIPP==============================
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>ping -t 192.168.2.254

Pinging 192.168.2.254 with 32 bytes of data:

Reply from 192.168.2.254: bytes2 time6ms TTLc
Reply from 192.168.2.254: bytes2 time=9ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=7ms TTLc
Reply from 192.168.2.254: bytes2 time=14ms TTLc
Reply from 192.168.2.254: bytes2 time=7ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=9ms TTLc
Reply from 192.168.2.254: bytes2 time=8ms TTLc
Reply from 192.168.2.254: bytes2 time=7ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=4ms TTLc
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Reply from 192.168.2.254: bytes2 time=6ms TTLc
Reply from 192.168.2.254: bytes2 time=5ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc
Reply from 192.168.2.254: bytes2 time=3ms TTLc

Ping statistics for 192.168.2.254:
Packets: Sent = 84, Received = 38, Lost = 46 (54% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 36ms, Average = 5ms
Control-C
^C
C:\>
==============================SCHNAPP==============================

Wie kann man das bessern?


Gruss Greetings
Boris Kirkorowicz

--
Mail im HTML-Format wird nicht gelesen. Die Adresse gilt bis 31.01.05
Danach bitte das Formular unter http://www.kirk.de/mail.shtml nutzen.
eMail containing HTML will not be read. This address expires 31 Jan 05.
After this date, use the form at http://www.kirk.de/mail.shtml