Yes, the log will just list what is being outputt to screen in to a file - call it anything you like:

e.g.

Exporting User Scott....

Table EMP ......1 row exported
Table DEPT ......10 rows exported
etc.

It's good to have because errors disppear off the screen quickly, and it also logs how many rows each table had on export.

FTP in binary mode:

Create a parfile (I assume the table doesn't exist?.. If it does, be sure to include ignore=y)

userid=user/password
file=/..../ext.dmp
commit=y
log=/.../ext_imp.log
buffer=
tables=tablename

you can use commit=n either i) if you're importing into a table which already has data ii) You have Rollback segments big enough to cope with the load.

then just run:
imp parfile=parfilename

One other thing - If you're importing in direct more (because that is the way you're export was done), you must be sure that you have all you're character sets set correctly.
Are the two database's the same NLS_ ?
Make sure the environment variable NLS_LANG is the same as your database setup too, or you'll get an error when trying to import.

Terry