iZ Technology Corporation

Howdies!

Like many people, I often move files from the Radar to another computer via FTP... however, a problem has crept up that just plain baffles me.

As you know, there are basically three ways to move files to a computer (I use a Mac)...
1) Using BROWSE and COPY on the Radar,
2) Using an FTP client to snag the files from the Radar (I use an old version of Fetch).
3) Using FILE EXPORT to export directly.

All methods yield the same problem:

Randomly, during the middle of a transfer, the Radar will lose connection... using PING reveals that much. I have no idea why.

Often, I will be moving a folder with, say, 12 tracks of, say, 100 gig each to my Mac (we save a lot of big improv sessions here). The project transfer will chug along just fine for a random amount of time... sometimes an hour or longer... then Fetch will report the connection has stalled out.

Before I can try again, I always have to re-boot the Radar.

I use standard RJ-45 cables on the network. I've tried changing all the cables out... but no joy. I've tried it using wireless (the Mac's Airport)... but that seemed to make it worse (slower transfer rate seems to cause it to err more often, but that could merely be coincidental).

The weird thing is that browsing the folders on the Radar from my Mac works great, and I can browse the Mac from the Radar, too, with no problem. Moving small files isn't a problem either... but of course they take MUCH less time.

I've had this issue for a while, unfortunately... so I can't say exactly when it started... but, it's time I got it fixed, work is piling up.

Could it be a bad network card? Has anyone seen or heard anything like this before?

ANY SUGGESTIONS whatsoever would be stellar!

DETAILS:
--------
Radar24, ver 3.42
MacPro running Snow Leopard.
D-Link router, model DIR-825
Fetch v.5.3.1

Any time you are using the BeOS FTP server, with your computer as the FTP client, you are likely to encounter this problem (although it doesn't seem to affect every RADAR unit).

However, in the case where you're working from the RADAR (copy/paste, export, etc.) this shouldn't be an issue. There might be some other networking issue in those cases.

Additionally, RADAR software has not yet been tested with Snow Leopard. So, we're unsure if any networking problems exist with the current OS X upgrade or not.

Thanks for the reply!

Just FYI...

The issue affects me regardless of whether I send from the Radar or not. In that case, the Radar will chug along great until the error, at which time it reports that the connection is lost.

This problem existed for me when I was running Mac OS Leopard as well as Snow Leopard... but I don't recall having it when I was running Tiger.

I suppose it's possible I have a network issue, but I can easily communicate with both the Radar and the Internet from the Mac, and the Radar can see and manipulate the Mac file structure.

I've swapped cables, as well as tried two different routers.

I have not tried connecting the Mac and Radar directly, leaving out the router... I suppose that might be next.

The problem only seems to occur during transfer of files of a few hundred megs or more, and especially during batch transfers of such files.

BTW: in my above post, I mentioned that I moved files of 100 gig or more... that was a mistake, it's actually files of 100 MEG or more. The largest files I've ever attempted to move are around 2 gig. Doh!

Yes, try connecting the Mac and RADAR directly via a crossover cable. You can obtain networking walk-thoughs from our technical memos page:

http://www.izcorp.com/support-documents-memos.php