Sporadisch Netzwerk nur lokal, warum?

JackDaniels

Lt. Junior Grade
Registriert
Jan. 2002
Beiträge
385
Hallo,

hab das Problem, dass sporadisch die Netzwerkverbindung nur lokal verfügbar ist und ich nicht mehr ins Internet komme.

Folgende Konfig:
Vista 64, Motherboard Gigabyte MA69G-S3h mit 1GBit-Lan onboard
Router DGL-4100 D-Link, PC mit Kabel angeschlossen

Meine Freundin, die auch am Router hängt (WindowsXP), fliegt dann auch aus dem Internet, wenn bei mir die Verbindung weg ist, also liegts ja eher an der Routerkonfig oder so, oder?
Betreibe den Router aber so schon seit ca.1 Jahr und hatte bisher null Probleme.
Das Internet kann während dem Spielen oder auch während dem Surfen einfach mal weg sein. Oftmals kommt es dann nach ein paar Sekunden wieder, ohne dass ich was gemacht habe.
Der Router macht hierbei keinen Reconnect oder so, Router ist weiterhin erreichbar und zeigt eine bestehende Verbindung an. Hab den Router auch schon mal auf Werkseinstellungen zurückgesetzt, hat nicht geholfen.

Hat hier jemand Ahnung was das sein könnte?
 
Schau mal im Ereignisprotokoll vom Router nach was da zur Fehlermeldung genommen wird. Ich hatte ähnliche Probs. Bei mir lags am Anbieter. Da die Verbdinung alle 3 Minuten abgekippt ist und versucht hat sich neu zu Synchronisieren, über 100 mal am Tag ;)

Mfg
 
Ich erlaube mir mal das hier zu posten, is die Info der letzten paar Minuten, wo das Problem auch auftrat (Zeit stimmt nicht, is aber wurscht):

[INFO] Wed Jan 07 02:14:00 2009 Log viewed by IP address 192.168.0.168
[INFO] Wed Jan 07 02:13:55 2009 Blocked incoming packet from 88.130.207.228:27738 to 88.130.213.132:135 (protocol 6)
[INFO] Wed Jan 07 02:13:53 2009 Blocked incoming packet from 88.130.114.15:15510 to 88.130.213.132:445 (protocol 6)
[INFO] Wed Jan 07 02:13:50 2009 Blocked incoming packet from 88.130.175.54:2106 to 88.130.213.132:135 (protocol 6)
[INFO] Wed Jan 07 02:13:50 2009 Blocked incoming packet from 88.130.68.196:64812 to 88.130.213.132:445 (protocol 6)
[INFO] Wed Jan 07 02:13:48 2009 Log viewed by IP address 192.168.0.168
[INFO] Wed Jan 07 02:13:47 2009 Blocked incoming packet from 88.130.175.54:2106 to 88.130.213.132:135 (protocol 6)
[INFO] Wed Jan 07 02:13:35 2009 Blocked incoming packet from 88.130.58.126:6643 to 88.130.213.132:135 (protocol 6)
[INFO] Wed Jan 07 02:13:34 2009 Blocked incoming packet from 88.130.102.124:36336 to 88.130.213.132:445 (protocol 6)
[INFO] Wed Jan 07 02:13:34 2009 Previous message repeated 1 time
[INFO] Wed Jan 07 02:13:22 2009 Blocked incoming packet from 88.160.53.76:1569 to 88.130.213.132:445 (protocol 6)
[INFO] Wed Jan 07 02:13:03 2009 Blocked incoming packet from 67.68.178.196:57763 to 88.130.213.132:135 (protocol 6)
[INFO] Wed Jan 07 02:12:52 2009 Log viewed by IP address 192.168.0.168
[INFO] Wed Jan 07 02:12:50 2009 Allowed configuration authentication by IP address 192.168.0.168
[INFO] Wed Jan 07 02:12:20 2009 Blocked incoming packet from 88.130.73.184:21888 to 88.130.213.132:135 (protocol 6)
[INFO] Wed Jan 07 02:12:16 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50425 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:16 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50424 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:16 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50348 to 64.233.183.113:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:16 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50350 to 74.125.8.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:12 2009 Blocked incoming packet from 172.21.174.28:32703 to 88.130.213.132:44481 (protocol 6)
[INFO] Wed Jan 07 02:12:06 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50425 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:06 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50424 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:06 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50348 to 64.233.183.113:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:06 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50350 to 74.125.8.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:02 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50425 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:02 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50424 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:02 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50348 to 64.233.183.113:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:12:02 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50350 to 74.125.8.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:59 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50425 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:59 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50424 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:59 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50348 to 64.233.183.113:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:59 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50350 to 74.125.8.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:58 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50425 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:58 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50424 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:58 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50348 to 64.233.183.113:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:58 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50350 to 74.125.8.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:58 2009 Blocked incoming packet from 88.130.37.19:15606 to 88.130.213.132:445 (protocol 6)
[INFO] Wed Jan 07 02:11:57 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50425 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:57 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50424 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:57 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50348 to 64.233.183.113:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:57 2009 Previous message repeated 1 time
[INFO] Wed Jan 07 02:11:57 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50350 to 74.125.8.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:57 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50425 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:57 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50348 to 64.233.183.113:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:57 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50424 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:54 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50441 to 74.125.79.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:54 2009 Previous message repeated 5 times
[INFO] Wed Jan 07 02:11:35 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50441 to 74.125.79.154:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:35 2009 Previous message repeated 1 time
[INFO] Wed Jan 07 02:11:21 2009 Blocked incoming packet from 88.130.73.184:12914 to 88.130.213.132:445 (protocol 6)
[INFO] Wed Jan 07 02:11:05 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50220 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:05 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50221 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:05 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50315 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:05 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50314 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:05 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50316 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:11:05 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50332 to 74.125.77.155:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:55 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50220 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:55 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50221 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:55 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50315 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:55 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50314 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:55 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50332 to 74.125.77.155:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:55 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50316 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:51 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50220 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:51 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50221 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:51 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50315 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:51 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50314 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:51 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50332 to 74.125.77.155:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:51 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50316 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:50 2009 SPI dropped TCP packet with flags 0x14 from 192.168.0.168:50296 to 74.125.79.164:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:48 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50220 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:48 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50221 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:48 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50315 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:48 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50314 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:48 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50332 to 74.125.77.155:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:48 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50316 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:47 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50220 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:47 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50221 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:47 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50315 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:47 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50332 to 74.125.77.155:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:47 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50314 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:47 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50316 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50220 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50221 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50315 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50314 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50332 to 74.125.77.155:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50316 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50315 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50314 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50220 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50316 to 87.230.75.10:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50221 to 87.230.75.2:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:46 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50332 to 74.125.77.155:80 (unexpected in state 0)
[INFO] Wed Jan 07 02:10:45 2009 Blocked incoming packet from 88.130.8.43:14026 to 88.130.213.132:445 (protocol 6)
[INFO] Wed Jan 07 02:10:45 2009 Previous message repeated 5 times
[INFO] Wed Jan 07 02:10:31 2009 SPI dropped TCP packet with flags 0x11 from 192.168.0.168:50296 to 74.125.79.164:80 (unexpected in state 0)
 
oh ka was das zu bedeuten hat sieht aber nicht gut aus und sieht so aus als würdest du die Verbindung zu deinem Hoster nicht finden
 
Das gleiche Problem habe sich auch mit meinem Linksys WRT54G. Mir kommt es so vor, als ob das passiert, wenn das Internet zu doll ausgelastet ist bzw. zuviele Verbindungen aufgebaut werden.

Meistens passiert das, wenn mein Bruder, Vater, meine Mutter und ich gleichzeitig im Netz sind und man dann Online spielen will oder mehrere Dateien runterlädt.
 
hi

haste mal ein Firmeware update bei deinem Router gemacht?
Wenn nicht würde ich es machen!
SPI ist deine Firewall die Pakete blockt!




mfg

awo
 
Zuletzt bearbeitet:
Dass die Firewall hier agiert ist mir bekannt, nur ist das so i.O. oder läuft hier was falsch? Kennt sich da jemand aus?

Firmware habe ich bisher noch nicht probiert, lief ja aber so auch schon 1 Jahr ohne Probs .....!?
 
hi

das mit der Firewall passt schon so das SPI kannste glaub auch ausschalten in den settings!
Ich würde einfach mal nen firmeware update fahren da dein router woll im Moment probleme hat da er die vielen verbindungen nicht verarbeiten kann!


mfg
awo
 
Hallo,

seit zwei Tagen habe ich keine Probleme mehr mit lokalem Zugriff.
Die Lösung:
Hab die Windows-Firewall wieder aktiviert (hatte die letztens ausgeschaltet).
Neue Firmware 1.7 für den D-Link DGL-4100 aufgespielt.
 
Zurück
Oben