Penny Arcade Forums› Help / Advice Forum
The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

Wireless Woes!

SikarianSikarian Registered User regular
edited February 2009 in Help / Advice Forum
Losing connection every so often over wireless.

PCI Card: PC60G MSI PCI Wireless card.
Router: Netgear WGR614v9
OS: Windows 7 (This issue occured in XP as well)

The wireless card antenna is about 4 feet away from the wireless router. Excellent signal.

When I ping 192.168.50.1 (my LAN IP, I get these kind of rates)

Pinging 192.168.50.1 with 32 bytes of data:
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=40ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=21ms TTL=64
Reply from 192.168.50.1: bytes=32 time=36ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=15ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=20ms TTL=64
Reply from 192.168.50.1: bytes=32 time=18ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=22ms TTL=64
Reply from 192.168.50.1: bytes=32 time=22ms TTL=64
Reply from 192.168.50.1: bytes=32 time=16ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=26ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=21ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=8ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=24ms TTL=64
Reply from 192.168.50.1: bytes=32 time=15ms TTL=64
Reply from 192.168.50.1: bytes=32 time=25ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=33ms TTL=64
Reply from 192.168.50.1: bytes=32 time=16ms TTL=64
Reply from 192.168.50.1: bytes=32 time=8ms TTL=64
Reply from 192.168.50.1: bytes=32 time=11ms TTL=64
Reply from 192.168.50.1: bytes=32 time=21ms TTL=64
Reply from 192.168.50.1: bytes=32 time=18ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=36ms TTL=64
Reply from 192.168.50.1: bytes=32 time=8ms TTL=64
Reply from 192.168.50.1: bytes=32 time=19ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=23ms TTL=64
Reply from 192.168.50.1: bytes=32 time=10ms TTL=64
Reply from 192.168.50.1: bytes=32 time=13ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=4ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=4ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=10ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=687ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=4ms TTL=64
Reply from 192.168.50.1: bytes=32 time=17ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=8ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=14ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=13ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.50.2: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.50.2: Destination host unreachable.
Reply from 192.168.50.2: Destination host unreachable.
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=22ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=19ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=19ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=40ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=33ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=13ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=16ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=18ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=4ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=26ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=25ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=21ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=24ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=15ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=4ms TTL=64
Reply from 192.168.50.1: bytes=32 time=4ms TTL=64
Reply from 192.168.50.1: bytes=32 time=28ms TTL=64
Reply from 192.168.50.1: bytes=32 time=39ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.50.2: Destination host unreachable.
Request timed out.
Reply from 192.168.50.2: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.50.2: Destination host unreachable.
Reply from 192.168.50.2: Destination host unreachable.
Reply from 192.168.50.1: bytes=32 time=38ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=25ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time=9ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=3ms TTL=64
Reply from 192.168.50.1: bytes=32 time<1ms TTL=64


And so on and so forth, this continues indefinitely. Any ideas? I'm at a loss as why the connection is so jumpy, and also why it completely times out after a while for a bit.

An additional bit of information I found interesting...if...while the system is going through it's hissyfits of losing connection, I go into the wireless networks page and drop the link to the router, then reconnect, it picks back up immediately and continues to work until it's next spaz.

[SIGPIC][/SIGPIC]
Sikarian on

Posts

  • ThanatosThanatos Registered User regular
    edited January 2009
    Find out what channels other wireless routers in the area are on. I'll bet at least one of them is close to the channel you're using.

    Thanatos on
  • SikarianSikarian Registered User regular
    edited January 2009
    Thanatos wrote: »
    Find out what channels other wireless routers in the area are on. I'll bet at least one of them is close to the channel you're using.


    No wireless routers nearby at all. Kinda secluded area.

    Sikarian on
    [SIGPIC][/SIGPIC]
  • ThanatosThanatos Registered User regular
    edited January 2009
    Try running it wired, see if you get the same thing. If you do, try running it straight into the modem.

    Thanatos on
  • SikarianSikarian Registered User regular
    edited January 2009
    Thanatos wrote: »
    Try running it wired, see if you get the same thing. If you do, try running it straight into the modem.


    I run into the problem that a) I has no network cable, b) I has no drivers for my wired NIC (and for some reason the MFG (ASUS WTF) doesn't want to provide them, and c) Windows 7 doesn't even -see- my wired card.

    No one else using the wireless connection is experiencing these issues at all

    Sikarian on
    [SIGPIC][/SIGPIC]
  • InfidelInfidel Heretic Registered User regular
    edited January 2009
    Sikarian wrote: »
    c) Windows 7 doesn't even -see- my wired card.

    No one else using the wireless connection is experiencing these issues at all

    Beta OS could potentially be your problem. Having a driver at least for your wireless is better than what you got left with wired, but that doesn't mean it's 100% either.

    Infidel on
    OrokosPA.png
  • SikarianSikarian Registered User regular
    edited January 2009
    Seems like it may possibly be 7, I guess. Unfortunately it's the only OS I have a copy of that works with everything I need it to that supports 6 gigs of memory. Sigh. Hoping maybe someone has experienced this and knows of a work around.

    I may go out and get PCI Wired NIC tomorrow to try

    Sikarian on
    [SIGPIC][/SIGPIC]
  • ThanatosThanatos Registered User regular
    edited January 2009
    Have you tried just plugging it in anyway, sans driver?

    I've had that work in the past.

    Thanatos on
  • randommanrandomman Registered User regular
    edited February 2009
    Do you have any cordless phones? They run on the same frequency as wireless routers and can cause signal loss and significant slow down.

    randomman on
  • fallaxdracofallaxdraco Registered User regular
    edited February 2009
    I had this problem a while back. I researched it for a while to no avail, so eventually I just ended up reformatting my laptop and reinstalling, and it worked fine after that.

    Though if you are having the same problem with both XP and windows 7, it is probably hardware related. Perhaps your wireless card is defective.

    fallaxdraco on
Sign In or Register to comment.
Penny Arcade Forums› Help / Advice Forum