Filezilla connection time out on 52.kb image upload

[Sennaria]

I use Filezilla as my ftp client for my website design.

Today I went to one of my sites to replace the Christmas images with the original one's I'd had on the website before the holidays, using the same images I'd had uploaded prior but now they are getting a connection timeout error.
Status: Connected
Status: Starting upload of /home/xx/xx/xx/xx/slide3.jpg
Command: CWD /public_html/xx/xx/xx
Response: 250 OK. Current directory is /public_html/xx/xx
Status: Retrieving directory listing...
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Command: PASV
Response: 227 Entering Passive Mode (173,247,250,112,129,42)
Command: MLSD
Response: 150 Accepted data connection
Response: 226-Options: -a -l
Response: 226 42 matches total
Command: PASV
Response: 227 Entering Passive Mode (173,247,250,112,133,79)
Command: STOR slide3.jpg
Response: 150 Accepted data connection
Error: Connection timed out
Error: File transfer failed

It will attempt twice before failing.

When I originally had these uploaded I was still running windows and filezilla. Now I am on Linux Mint 14- Mate with filezilla. Smaller files are uploading fine. I am totally at a loss as to where to look to fix this.

Any help would definitely be appreciated.

I'll gladly provide any information needed to help figure this out.

Below is System and Network Information:

-Computer-
Processor : 4x Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz
Memory : 6096MB (964MB used)
Operating System : Linux Mint 14 Nadia
Date/Time : Fri 18 Jan 2013 12:23:46 PM CST
OpenGL Renderer : GeForce GT 610/PCIe/SSE2
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA Intel PCH
Audio Adapter : HDA-Intel - HDA NVidia
Logitech Unifying Device. Wireless PID:1025
-SCSI Disks-
ATA Hitachi HDS72101
hp CDDVDW TS-H653T
-Processors-
Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz : 1600.00MHz

-Network Interfaces-
eth0 45.51MiB 12.19MiB 192.168.1.125
lo 0.42MiB 0.42MiB 127.0.0.1
-IP routing table-
0.0.0.0 / 192.168.1.1 0.0.0.0 UG eth0
169.254.0.0 / 0.0.0.0 255.255.0.0 U eth0
192.168.1.0 / 0.0.0.0 255.255.255.0 U eth0
-Name servers-
127.0.1.1
208.67.222.222
208.67.220.220



-IP-
64585 : Total packets received
1 : With invalid addresses
0 : Incoming packets discarded
0 : Incoming packets discarded
64581 : Incoming packets delivered
62052 : Requests sent out
35 : Dropped because of missing route
-ICMP-
0 : ICMP messages failed
0 : ICMP messages failed
173 : ICMP messages sent
0 : ICMP messages failed
-ICMPMSG-
-TCP-
2403 : Active connections openings
24 : Passive connection openings
355 : Failed connection attempts
117 : Connection resets received
8 : Connections established
60754 : Segments received
53974 : Segments send out
4218 : Segments retransmited
0 : Bad segments received.
1311 : Resets sent
-UDP-
3800 : Packets received
173 : Packets to unknown port received.
0 : Packet receive errors
3650 : Packets sent
-UDPLITE-
-TCPEXT-
752 : TCP sockets finished time wait in fast timer
588 : Delayed acks sent
1440 : Packets directly queued to recvmsg prequeue.
1902236 : Bytes directly received in process context from prequeue
43795 : Packet headers predicted
1180 : Packets header predicted and directly queued to user
3919 : Acknowledgments not containing data payload received
1192 : Predicted acknowledgments
2 : Classic Reno fast retransmits failed
177 : Times recovered from packet loss by selective acknowledgements
2 : Classic Reno fast retransmits failed
14 : Congestion windows recovered without slow start after partial ack
23 : Timeouts after SACK recovery
49 : Timeouts in loss state
191 : Fast retransmits
21 : Forward retransmits
115 : Retransmits in slow start
1503 : Other TCP timeouts
2 : Classic Reno fast retransmits failed
128 : SACK retransmits failed
311 : DSACKs sent for old packets
10 : DSACKs received
1 : DSACKs for out of order packets received
56 : Connections reset due to unexpected data
63 : Connections reset due to early user close
39 : Connections aborted due to timeout
-IPEXT-

[Sennaria]

Well, turns out all I had to do was disable the timeout. Didn't think of that at first as it wasn't necessary before. But at least now the images and files upload.