Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[vetl]

I just purchased this router, before I had B router and I didn't have those problems. The issue is when I play online video on my laptop that is connected by wireless network, the internet connection goes down only on the laptop! the icon shows that I have only local access which I do have. The computer that is connected by wire to the router can access internet at that time. After a few minutes I get internet access back again. It seems to me that router can't handle multiple streams for some weird reason. I tried to run test from MS web site on TCP connection and when I got to the part where 70 or 80 connections were open at the same time my internet connection just went down immediately. I tried to use default settings on my router as well as modifying it a little bit no effect at all. The firmware on the router is 1.11MSbeta, however I had exactly the same problem with 1.11. My laptop is VAIO VGN-BX660P with wireless adapter Intel(R) PRO/Wireless 3945ABG Network Connection with the latest drivers. I disabled most of firewall settings in the router, set the WAN speed to 100, channel 11, at 20mHz used WISH still no changes, when watching online movie and brows at the same time connection drops , pls if you have any suggestions I will be glad to her them, if you need more info please ask.

[Lycan]

Do you know how to run a constant ping?
Try pinging the router while you're trying to connect. See if the pings time out.

[vetl]

heh, it pings it perfectly Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Vitaliy>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

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

I can't even guess where is the issue, the internet connection on my laptop drops to local access only and thats it, while the router is still online with a computer that  connected by wire to it.

[Lycan]

Sounds like a QoS configuration issue.
Also atry adding a -t after the ping (ping 192.168.0.1 -t) and see how many drop off.

[vetl]

I just tried to disable QoS, did help much, and I was pinging router at the time of disconect, same picture on all lines, seems to be fine
C:\Users\Vitaliy>ping 192.168.0.1 -t

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

[Lycan]

Now cause the drop to happen with the pings running.

[midhenry]

Some time ago I had a similar problem (right after I got my 655).  I managed to create the problem myself.  I was replacing a Netgear router with a built in printer port that I wanted to keep, so I just plugged the Netgear into the hub after installing the 655 and voila, I had a working printer port again.  All was fine for a day, and then I lost internet access on the wireless laptop (the wired desktop was fine - still had internet access).  I could still ping and connect to the 655 and I could ping outside (e.g. mail.google.com) via the 655 interface.

So, I tried a DOS box ipconfig.  The default gateway came back as 192.168.0.2!!  Oops, I had not shut off the DHCP server in the Netgear, so I had two DHCP servers.  Lease time on the 655 was set to (yup) 24 hours. Lease renewal came up and the Netgear DHCP server won and configured the client's (the wireless laptop) gateway to 192.168.0.2, and now no working gateway.

I am not 100% confident of my analysis as it makes sense that the client would do a DHCP renew directly to 192.168.0.1 rather than a broadcast.  This from the TCP guide:

Renewal: After a certain portion of the lease time has expired, the client will attempt to contact the server that initially granted the lease, to renew the lease so it can keep using its IP address.

So apparently the client either broadcast instead of a renew request, or the 655 didn't respond to a renew request.