Internal file transfer seems too slow

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.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Talk about the tail wagging the dog....

by robo_dev In reply to Internal file transfer se ...

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.

Collapse -

BSA transmission problems

by Nimmo In reply to Internal file transfer se ...

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.

Collapse -


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)

Collapse -

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.

Collapse -

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.

Collapse -

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.

Collapse -

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?


Collapse -

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.

Collapse -

Response rate

by Nimmo In reply to TTL Is time to live, also ...

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.

Collapse -

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.

Related Discussions

Related Forums