Question

  • Creator
    Topic
  • #2152491

    Internal file transfer seems too slow

    Locked

    by stealthwifi ·

    Internal network – Server 2003 2 gigabit cards connected to a gigabit wireless router and transfering an 80GB file to a client connected to the Wireless G router at 54mbs.

    The file get’s finished transfering and the resultent calculations shows a transfer speed of aprox 2mbs. There are only 6 other boxes sharing this wireless connection and none were transfering any files at the time.

    Cards are in full duplex mode and router us also full duplex. Performance log on the server shows both cards have fill 1BG bandwidth so cards seem fine. Everything works great just seems awefully slow.

    Any ideas, I’m having a hard time understanding why the transfer is sooo slow.

All Answers

  • Author
    Replies
    • #2767414

      Clarifications

      by stealthwifi ·

      In reply to Internal file transfer seems too slow

      Clarifications

    • #2767390

      Talk about the tail wagging the dog….

      by robo_dev ·

      In reply to Internal file transfer seems too slow

      What sort of transfer rate do other clients get?

      Is the client a VISTA box?

      Until tweaking the network settings, one of my vista boxes could only transfer data at like 200kbs on a GIG ethernet port.

    • #2767330

      BSA transmission problems

      by nimmo ·

      In reply to Internal file transfer seems too slow

      First up reboot your access point and try again and try another transfer from a different machine.

      The distance between the wireless access point and the computer will have a large impact on the speed of data transfer.

      You may have a 54mb capable wireless card in the computer and a 54mb access point, it doesn’t mean your gona get 54mb connection.

      Factors such as overhead from protocols and file encrption will drop your speed.
      also the further the laptop is from the access point the slower the connection becomes.

      Take a look at the connection speed on the computers network card prior to the data transfer.

      Also you will get signal degradation from things been placed between the two devices such as walls,(microwaves will effect anything on channel 11).

      Signals can also get reflect off objects too which will cause you issues.

      Also ping the access point and take not of the TTL if it’s pretty high I think you’ll find one of the above a cause of you problems.

      If not you could have a doggy network card in your laptop, or doggy access point.

      • #2766217

        OS’s

        by stealthwifi ·

        In reply to BSA transmission problems

        All boxes are XP Pro (SP3)

        Network cards report 54mb/s. Tried on 2 pc’s and both have line of sight to router about 10ft away and same results.

        TTL to access point is 64 is that high?

        Tried to make sure no other file transfers were going on and server was at a low period, it’s a dual Xeon quad core (3GHz)
        with not much load on it.

        I’m starting to think the router just sucks, been looking for a nicer Cisco upgrade (like the Secure Router 520 wireless)

        • #2766212

          Even if…

          by cmiller5400 ·

          In reply to OS’s

          Even if they report 54mb/s, they may not transfer at that speed. You can’t guarantee any wireless transfer rate speed.

        • #2766177

          Yes, 64 sucks

          by slayer_ ·

          In reply to OS’s

          I just tried it on my wireless, I took my laptop to the end of my street, about 4 houses away, and pinged my wireless and got 8ms.
          I think something in your network is sucking.

        • #2766006

          High response rate

          by nimmo ·

          In reply to OS’s

          64 is pretty high especially for a very close connection with only a single hop.

          Just to give you an idea how high it is, I can ping from our Sydney server to a clients Hong Kong server at 110ms(steady).

          I’d maybe if possible try another machine and also if you can borrow another access point (before you go and spend money on a new) put it in, ping, and check the response rate.

        • #2765836

          RE: High response rate

          by stealthwifi ·

          In reply to High response rate

          The actual time is 2ms the TTL is 64.

          I tested the defualt TTL (by pinging localhost) and it’s 128. I read that is standard now. How does the TTL of 64 come into play?

          Cheers,

        • #2765806

          TTL Is time to live, also wireless is always fairly slow

          by slayer_ ·

          In reply to RE: High response rate

          I believe it refers to how long it waits for a response before the packet is considered lost.

          And wireless is always fairly slow compared to wired, The size of the group of packets sent is much smaller, requiring more answering from the reciving computer, using up more bandwidth. And of course if a packet is dropped, the system adjusts to an even slower speed.

        • #2769996

          Response rate

          by nimmo ·

          In reply to TTL Is time to live, also wireless is always fairly slow

          Yeah TTL is the response rate, the time in which is response is sent back is due to connection speed and distance between nodes.

          Depending on network policies you may not get responses from certian devices because they are blocking ICMP (although there are ways to ping via TCP).

          Wireless is generally slower compaired to wired although the new 802.11n standard is capable of speeds higher than the 100baseT network.

          The next thing I would try if everything everyone has suggested has been tried is to get another access point and configure and test the connection with it.

          You do have to remember that 80GB is huge over any connection, use this calculator to get an idea of how fast the transfer should be.

          http://www2.arnes.si/~kriskem1/hihi/calc_trans.htm

        • #2769768

          New Problum

          by stealthwifi ·

          In reply to Response rate

          Ok so now when transfering the file it get’s aprox half way completed and stops – gives the “Another proccess has locked a portion of this file…”

          I am unable to find the other proccess, is this just becuase the connection died?

          I tried ProccessExplorer to search handles with that file before after and during the drop. Canceled all scheduled jobs, and made sure nothing else was being transfered.

          It took a while before but at least finished.

          No changes to router or boxes since last successfull transfer.

    • #2769672

      RE: new problem

      by nimmo ·

      In reply to Internal file transfer seems too slow

      Are any of these files that you are transfering shares? If they are you can take a look at what files are open and who has them open via the computer management console or command line (start>run>cmd>net file | more).

      Are any of the files database files, if they are you may find that the database ins’t locked so they are still in use.

      It’s kind of a hard one to answer unfortunatly you will need to look at the files been transfered and see if they are open.

      Also make sure you are viewing hidden files/folders you may accidently be trying to transfer system files that are locked by running process or application.

      • #2774854

        It’s a windows backup file

        by stealthwifi ·

        In reply to RE: new problem

        File is an 80gb .bkf windows backup file.

        It’s not on a share, just get’s half way completed and stops with the error.

        I tried transferring at multiple times of the day and even from different disks on the server and same thing.

        I made certain the backup was not cataloged and not archived. Even set permissions so only one account had access and still same thing.

        • #2770220

          Did you verify the backup

          by nimmo ·

          In reply to It’s a windows backup file

          I’m wondering since it isn’t even transfering between disks on the same drive if you have a corrupt backup file that is crashing out during the transfer.

          When you did the backup with NTBackup did you run it with verification.

          What is the exact error? is it showing up in the event viewer at all?

        • #2770182

          The file is probably filesystem corrupted

          by slayer_ ·

          In reply to Did you verify the backup

          Occasionally Windows will allocate the full size of the file, even though the data may only use half the file, and the rest is blank garbage. The blank garbage would either not transfer, or transfer instantly.

          A
          chkdsk C: /F
          should fix the file, if this is the case.

        • #2770031

          used verify

          by stealthwifi ·

          In reply to The file is probably filesystem corrupted

          I did use verify on the backup and it came out with no errors. It will transfer between disks and browses fine, just won’t transfer to a storage box (over the WLAN).

          No errors in Event Viewer – I am completley baffeled by this whole thing.

          I put the file in read only mode and it got farther than ever (3/4 of the way) then Bam, same proccess locked file message.

          Ran ChkDsk /f and it ran with no problums

        • #2770598

          More Info

          by stealthwifi ·

          In reply to used verify

          I recorded the file transfer over night with Proccess Explorer open to see what proccess is killing it.

          The only thing that appears to change is an IIS Worker Proccess starts. I can not tell if it is actually the proccess in question or just happens to start when the file screws up.

          (Used Camtasia to record)

        • #2763975

          Tried another way – new error

          by stealthwifi ·

          In reply to More Info

          I tried moving the file via cmd prompt with the move command and got the following error:

          The semaphore timeout period has expired.
          0 file moved.

          The file has only 2 characters in the name MF.bkf

          Cheers,

    • #2762886

      Solved It

      by stealthwifi ·

      In reply to Internal file transfer seems too slow

      Moved the file to another drive on the same box and it’s perfect.

      First drive was horribly fragmented, it’s being stripped and formatted as we speak.

Viewing 4 reply threads