Previous 1 33 34 35 36 37 Next 966 Replies Latest reply: Sep 15, 2014 6:52 AM by miroslavfromprague 9 Go to original post
  • LaraJones Level 1 Level 1 (0 points)

    Number three for today.

    Concerning WAP

     

    My neighbour just called my over the garden fence and asked me to come over with my Notebook to check out his new Wlan Router. He is only owning PC´s on ethernet and bought the router for the Notebook of his girlfriend.

    The new router is a Netgear as well and whats interesting , he uses a WAP password on it. We ourself are using only WEP on our routers as we are having an old machine which is not up to the new WAP standard and here some people were of the opinion that one of the causes of the network problems could be the usage of the WAP standard.

    I logged in with my Macbook and had no problem with this WAP standard either. I started a stream from online TV in HD and  my Macbook worked on HIS router under WAP as well as on ours at home!

  • yozhbk Level 1 Level 1 (0 points)

    No you are not doing what I said. Try to transfer a file localy while on a N connection and the do the pings, stream etc... and see what happens.

  • LaraJones Level 1 Level 1 (0 points)

    Alrigtht! What do you understand under transfering a file lokaly? Copying a file within the machine? Within a network or what?

  • ThExSenatoR Level 1 Level 1 (0 points)

    yozhbk says copy a bigger file from another computer to the mbp 2011 over wifi (n) and watch your pings in terminal. The thing is that you will get ping dropouts (packet loss) while copying a large file on the local network. Another Macbook unibody (2008) doesnt have this issue, no packet loss while copying a big file on wireless network.

  • ThExSenatoR Level 1 Level 1 (0 points)

    Pinging my NAS while copying a large (700mb) file from the NAS to my macbook pro 2011.

     

    MacBook-Pro:~ senator$ ping naspro

    PING naspro.power.net (192.168.0.201): 56 data bytes

    Request timeout for icmp_seq 0

    Request timeout for icmp_seq 1

    Request timeout for icmp_seq 2

    Request timeout for icmp_seq 3

    64 bytes from 192.168.0.201: icmp_seq=4 ttl=64 time=6.228 ms

    64 bytes from 192.168.0.201: icmp_seq=5 ttl=64 time=4.095 ms

    Request timeout for icmp_seq 6

    64 bytes from 192.168.0.201: icmp_seq=7 ttl=64 time=6.066 ms

    64 bytes from 192.168.0.201: icmp_seq=8 ttl=64 time=4.742 ms

    64 bytes from 192.168.0.201: icmp_seq=9 ttl=64 time=6.221 ms

    Request timeout for icmp_seq 10

    64 bytes from 192.168.0.201: icmp_seq=11 ttl=64 time=4.609 ms

    Request timeout for icmp_seq 12

    Request timeout for icmp_seq 13

    Request timeout for icmp_seq 14

    64 bytes from 192.168.0.201: icmp_seq=15 ttl=64 time=5.630 ms

    ^C

    --- naspro.power.net ping statistics ---

    16 packets transmitted, 7 packets received, 56.2% packet loss

    round-trip min/avg/max/stddev = 4.095/5.370/6.228/0.812 ms

     

    Doing the same on MacBook Aluminum Late 2008, 0% packet loss. Same network, same settings...

     

    The interesting thing is, that both of them achieve the same network throughtput, 9-11mbytes/sec.

    (MCS Index: 15, Transmit rate: 300)

     

    Before the update I had maximum 7 mbytes/sec transfer speed on my 2011 mbp and also had the fluctuating ping problem, which was resolved by the update, however I never noticed weak wireless connection or connection drops before or after the update.

     

    When not copying pings are normal (after the software and efi update) or almost the same as on the 2008 macbook to anywhere.

     

    Message was edited by: ThExSenatoR

  • LaraJones Level 1 Level 1 (0 points)

    I ll try it tomorrow. Will let let you know what happens...

    Good night for now!

    Lara

  • ThExSenatoR Level 1 Level 1 (0 points)

    Lara, please post your values under About this mac -> more info -> Airport -> Card type and firmware. Mine is:

     

    Card Type:                    AirPort Extreme  (0x14E4, 0xD6)

    Firmware Version:          Broadcom BCM43xx 1.0 5.100.198.104.3)

     

    and also under Hardware in about this mac:

     

    Boot ROM Version:          MBP81.0047.B0E

    SMC Version (system):          1.70f3

     

    Should be the same...

  • lwrach Level 1 Level 1 (0 points)

    After installing the software updates, there was a day without dropped connections, but now another dropped connection has just happened.

     

    I'm wondering, however, if I have a different problem from some other people here. When this connection drops, I can't reconnect at all to LAN. (Other computers on the LAN are unaffected.) Has anybody else had this particular problem--not being able to reconnect to the LAN at all after the MBP loses its connection?

     

    What happens after the disconnect, specifically, is that Airport now shows the LAN among the networks it can see, but when I click on the network name and enter the password, the password prompt window just pops back up again (no matter how many times the password is entered), without ever connecting to the network.

     

    By the wat: the LAN uses a WPA2 password, set to mixed 11b+11g.

     

    All suggestions very welcome at this point!

  • ThExSenatoR Level 1 Level 1 (0 points)

    Never had a problem like that

    Using Airport Express, 5 GHZ N Only channel 36.

  • [ML] Level 1 Level 1 (0 points)

    I've solved my problem with weak connection by changing router to the airport extreme. But have the same issue with lost packets while transferring file locally.

     

    results while transferring something from internet:

     

    PING 10.0.1.1 (10.0.1.1): 56 data bytes

    64 bytes from 10.0.1.1: icmp_seq=0 ttl=255 time=0.700 ms

    64 bytes from 10.0.1.1: icmp_seq=1 ttl=255 time=0.738 ms

    64 bytes from 10.0.1.1: icmp_seq=2 ttl=255 time=0.793 ms

    64 bytes from 10.0.1.1: icmp_seq=3 ttl=255 time=0.660 ms

    64 bytes from 10.0.1.1: icmp_seq=4 ttl=255 time=0.572 ms

    64 bytes from 10.0.1.1: icmp_seq=5 ttl=255 time=0.670 ms

    64 bytes from 10.0.1.1: icmp_seq=6 ttl=255 time=0.589 ms

    64 bytes from 10.0.1.1: icmp_seq=7 ttl=255 time=0.818 ms

    64 bytes from 10.0.1.1: icmp_seq=8 ttl=255 time=0.572 ms

    64 bytes from 10.0.1.1: icmp_seq=9 ttl=255 time=0.788 ms

     

    --- 10.0.1.1 ping statistics ---

    10 packets transmitted, 10 packets received, 0.0% packet loss

    round-trip min/avg/max/stddev = 0.572/0.690/0.818/0.089 ms

     

    when wifi is idle:

     

    PING 10.0.1.1 (10.0.1.1): 56 data bytes

    64 bytes from 10.0.1.1: icmp_seq=0 ttl=255 time=4.218 ms

    64 bytes from 10.0.1.1: icmp_seq=1 ttl=255 time=4.510 ms

    64 bytes from 10.0.1.1: icmp_seq=2 ttl=255 time=4.642 ms

    64 bytes from 10.0.1.1: icmp_seq=3 ttl=255 time=4.333 ms

    64 bytes from 10.0.1.1: icmp_seq=4 ttl=255 time=4.491 ms

    64 bytes from 10.0.1.1: icmp_seq=5 ttl=255 time=4.236 ms

    64 bytes from 10.0.1.1: icmp_seq=6 ttl=255 time=4.192 ms

    64 bytes from 10.0.1.1: icmp_seq=7 ttl=255 time=4.270 ms

    64 bytes from 10.0.1.1: icmp_seq=8 ttl=255 time=4.560 ms

    64 bytes from 10.0.1.1: icmp_seq=9 ttl=255 time=4.215 ms

     

    --- 10.0.1.1 ping statistics ---

    10 packets transmitted, 10 packets received, 0.0% packet loss

    round-trip min/avg/max/stddev = 4.192/4.367/4.642/0.159 ms

     

    while transferring 6GB file locally:

     

    64 bytes from 10.0.1.1: icmp_seq=0 ttl=255 time=4.771 ms

    Request timeout for icmp_seq 1

    64 bytes from 10.0.1.1: icmp_seq=2 ttl=255 time=5.519 ms

    64 bytes from 10.0.1.1: icmp_seq=3 ttl=255 time=11.668 ms

    64 bytes from 10.0.1.1: icmp_seq=4 ttl=255 time=5.247 ms

    Request timeout for icmp_seq 5

    64 bytes from 10.0.1.1: icmp_seq=6 ttl=255 time=3.512 ms

    Request timeout for icmp_seq 7

    64 bytes from 10.0.1.1: icmp_seq=8 ttl=255 time=2.076 ms

    64 bytes from 10.0.1.1: icmp_seq=9 ttl=255 time=4.010 ms

     

    --- 10.0.1.1 ping statistics ---

    10 packets transmitted, 7 packets received, 30.0% packet loss

    round-trip min/avg/max/stddev = 2.076/5.258/11.668/2.832 ms

     

    MCS index:23

    Transmit rate: 450

     

    Card Type, Firmware and Boot Rom Versions are the same, but SMC Version is 1.69f1


  • ThExSenatoR Level 1 Level 1 (0 points)

    Thanks for sharing your results ML. Do you get these under Lion? What is your transfer speed in mbytes/sec in activity monitor?

  • yozhbk Level 1 Level 1 (0 points)

    See the issues is this, while transfering from internet, ofcourse you can not reach high speeds, and hence the link saturation is low and you are not seeing drops, same as people are not really seeing many issues on G networks. something with link saturation. I think its firmware related. I wish some one with new iMacs can do the same tests.

  • LaraJones Level 1 Level 1 (0 points)

      Good morning:

     

    Here are my Macbook Airport Values:

     

     

    Softwareversionen:

      Menüerweiterung:          6.2.2 (622.2)

      configd Plug-in:          6.2.5 (625.6)

      System-Profiler:          6.0.1 (601.1)

      Netzwerkeinstellung:          6.2.2 (622.2)

      AirPort-Dienstprogramm:          5.5.2 (552.11)

      IO80211-Familie:          3.2 (320.1)

      Schnittstellen:

    en1:

      Kartentyp:          AirPort Extreme  (0x14E4, 0xD6)

      Firmware-Version:          Broadcom BCM43xx 1.0 5.100.198.104.3)

      Locale:          APAC

      Länderkennung:          DE

      Unterstützte PHY-Modi:          802.11 a/b/g/n

      Unterstützte Kanäle:          1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140

      Ruhezustand bei drahtlosem Zugriff beenden:          Unterstützt

      Status:          Verbunden

    and the hardware:

     

    MacBook Pro

      Modell-Identifizierung:          MacBookPro8,1

      Prozessortyp:          Intel Core i5

      Prozessorgeschwindigkeit:          2,3 GHz

      Anzahl der Prozessoren:          1

      Gesamtanzahl der Kerne:          2

      L2-Cache (pro Kern):          256 KB

      L3-Cache:          3 MB

      Speicher:          8 GB

      Boot-ROM-Version:          MBP81.0047.B0E

      SMC-Version (System):          1.68f96   thats different to yours!

  • [ML] Level 1 Level 1 (0 points)

    ThExSenatoR wrote:

     

    Thanks for sharing your results ML. Do you get these under Lion? What is your transfer speed in mbytes/sec in activity monitor?

    No, I`m using 10.6.7. The transfer speed is about 15-18Mbytes/sec (from MBP2011 to HD plugged to airport extreme).

  • LaraJones Level 1 Level 1 (0 points)

    Hi guys,

     

    I could only test the transfering of big  files in my Windows Network as I dont have a network here with Macs..( my macbook is the only one and I am not using a timecapsula....only use the MacOS network between Macbook and the apple TV.

     

    And yes...that killed it completely....

     

    I transfered a folder with photos from my Macbook ( Windows in bootcamp) to my Tablet PC in the local Windows 7 network over Wirelss Lan. Means I tried to do it...

     

    Results:

    Foldersize 23 GB

    estimated transfer time 5 hours

    Speed between 1.08 and 1.12 MB/Sec

     

    Whilst running  the transfer every single pingtest in Windows failed. 100 % Packet loss.

     

    Not even normal surfing was  possible, impossible to  come to the websites to start a stream...

    Quiete horrible!

     

    Good, that I do my backups on my dockingstation via USB...  I think under that condition to use time capsule is not to possible is it??????

     

    Stopped the transfer and everything worked again perfectly at once .....

     

    Found in some of your older threads that the former modell had problems like this as well????? And its not solved yet... Pah, thats not a good light on a shiny company????

     

    But now tell me, whats the difference when I stream a movie from my Macbook to the apple TV over my network ..its big amount of data as well and that works without problems...!!!?????

    I am not an technical expert... the technical expert in this house is in Chicago at present and only back home on Saturday... see what he will say to that...

Previous 1 33 34 35 36 37 Next