Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Wireless LAN problem

  • 27-07-2005 10:27pm
    #1
    [Deleted User]
    Posts: 0 ✭


    I have a Buffalo 802.11b wireless router, have had it for a long time but only started using it now. I've noticed that when pinging wireless clients that there is occasionally a packet which takes a lot longer to get there, and very rarely it is lost altogether. Here's a ping I performed from my PC (wired) to my sister's (wireless):

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

    C:\>ping /t sue

    Pinging sue [192.168.0.6] with 32 bytes of data:

    Reply from 192.168.0.6: bytes=32 time=3ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=177ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=621ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=246ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=5ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=888ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=4ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=249ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=2ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128
    Reply from 192.168.0.6: bytes=32 time=1ms TTL=128

    Ping statistics for 192.168.0.6:
    Packets: Sent = 84, Received = 84, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 888ms, Average = 27ms
    Control-C
    ^C
    C:\>

    The access point is 802.11b as I mentioned above, but the cards I'm using are D-Link DWL-G520+ 802.11g (54Mb/s) cards. I also have a DWL-G650 Cardbus card in a laptop, same problem. If I ping the access point from a wireless PC I also have this problem, but if I do it from a wired PC then it works away fine.

    Is this a compatibility issue or a fault with the access point? Or is there any other advice you could give me?


Comments

  • #2
    CiaranC
    Closed Accounts Posts: 6,300 ✭✭✭CiaranC


    Do you notice degraded performance when using the network?


  • #3
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    I'm not 100% sure at the moment, its only been online for a few hours. So far its just been used for the internet so its hard to tell.

    Signal strength seems fine by the way.


  • #4
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    I think I've answered my own question. I found an 802.11b PCMCIA card lying around so I put it in a 486 laptop (lol, yes it actually can take it!). The card doesn't have any brand name, seems to be one of those cheap unbranded jobs.
    If I use the laptop to ping a PC with one of the D-Link cards I'll get the delayed or dropped packets. But if I ping my PC (which is on the wired LAN) I don't lose anything, I sent 213 packets and got a maximum of a 5ms ping.

    So it looks to me like the D-Link cards don't "like" my access point, maybe because they're 802.11g rather than 802.11b. But I'd assume they'd be backwards compatible?? :confused:


Advertisement