Access fails to upload via FTP

G

gillmcd

I' ve got an odd problem.

Previously (my old computer) I have used Win 98/CuteFTP 4.0 to upload
Access (2000) database files to my site. I can still do this now with
no problem.

I now also have a computer with Win XP Home/Access 2003/ CuteFtp 8.0. I
can upload all files except the .mdb ones. When I try to upload the
file "hangs" and "murders" the internet connection. In order to
reconnect I have to reboot.

Initially I presumed it was a CuteFTP problem and have been in contact
with them. We've done all the usual uninstall etc but problem remains.
I have now tried uploading an mdb file with Filezilla and get exactly
the same problem.

The problem still occurs if I disable my firewall (Sygate) and anti
virus (Nod32).

I am at a loss to understand what is happening. Clearly there is no
server problem with my old system.

I have tried both passive and port modes. I have also tried changing
the .mdb extension to .txt - it still fails.

Has there been some change in Access to cause this to happen? Please no
flames on the downsides of using Access on the internet. I know the
arguments.
 
A

Albert D. Kallal

From what you explained here, ms-access does not even have to be installed
on your computer.

From he information given, you are simply transferring a windows file, and I
see little, if any relationship to ms-access.

Try the mdb as a zip file. perhaps you have the FTP set as text only...and
not binary.

Has there been some change in Access to cause this to happen? Please no
flames on the downsides of using Access on the internet. I know the
arguments.

But you not using ms-access, and you not using any code related to
ms-access.

A horse is a horse is a horse
A file is a file is a file.

Unless you left out some big huge earth shattering detail here, what does
this have to do with ms-access (except that you can't transfer some dumb
file sitting on the hard drive that happens to have a mdb extension?)
 
G

gillmcd

Well forgive my ignorance.

Surely this does have something to do with Access. All other files
upload without a problem. OK I'm not trying to upload using code but
I'm still trying to upload an access database which I use in Access
software on my computer.

Certainly it is just a file with an .mdb extension. The question is why
is it failing when other files don't.

This is an access forum and seemed a valid place to post the question.
If I'm wrong please tell where I should post.
 
S

susiedba

Gill

Access MDB has locking whenever anyone is using it.

that is one of the main reasons that I dislike MDB format so much

-Susie

btw, did you used to work at MS Operations?
 
G

gillmcd

Hi,

Thanks for your response.

No not me at MS Operations :)

Has there been a change to the way that locking is handled? Uploading
has always been fine under '98/Access 2000? It's the XP /Access 2003
that's the problem.
 
A

Albert D. Kallal

Surely this does have something to do with Access. All other files
upload without a problem. OK I'm not trying to upload using code but
I'm still trying to upload an access database which I use in Access
software on my computer.
Certainly it is just a file with an .mdb extension. The question is why
is it failing when other files don't.

If you are able to rename, or zip the file, and it fails, then something
else has
to be at fault here.
This is an access forum and seemed a valid place to post the question.
If I'm wrong please tell where I should post.

I accept the question, but you not made any case. If you told me a
ms-access process is trying upload the file, and it can't..then we have
a different story.

You said that even when you ren-name the file as a text document, it don't
work.

However, .txt *often* means to transfer as ftp as "text" mode...

So, my suggesting was to try a zip file. does that work?

It is possible your ftp transfer is working as text, and not binary..and
that will mess things up.

So, no, I not upset, or the least bit bother here. But, really, you question
is that you simply can't transfer a file, and it happens to be a mdb
file..but, with the give information, it seems that ANY binary file is at
fault here.

Sure, the mystery is worth trying a question here. But, really, your problem
would exist even if ms-access was not even installed on your machine!!!

I would try the zip file......

I do think this problem does need good hard whack, and I don't think it is
specific related to ms-access.

And, if I any sounded un kind, or un-charitable here, please accept my
sincere apologies.

And, I am interested in what your fix/solution eventually is. This newsgroup
is all about sharing, and I am wreaking my brains as to why you are having
this problem!!!

(we both likely are a bit frustrated..but, more so rather interested as to
what the solution is!!)
 
G

gillmcd

Thanks

I have tried PORT and PASV in CuteFTP (which I understand caters for
binary??) and binary in FileZilla. Same thing happens.

I can't test your zip suggestion as I will not be able to unzip the
file. I use a hosted website. My provider says he can upload the file -
so can I with '98/Access 2000 configuration.
 
G

gillmcd

Found a fix for this which I've posted below in case anyone else is
having the same problem. What a mission.

The problem was the Windows Firewall which seemed to be controlling
Port 21 even though Win Firewall was turned off as I am running Sygate.

To get control of Port 21:

Go to Control Panel | Security Center | Windows Firewall
Click on Advanced tab
Select the appropriate Network Setting and the click on Settings.
Tick FTP Server

Everything fine after this. It still doesn't answer the question of why
Port 21 was allowing all files except for .mdb

Elsewhere I saw a post saying do this:
 
G

gillmcd

A further post - I guess it's not directly related to Access so
apologies if I'm treading on anyone's toes - but for the sake of
continuity it seemed best to post this here.

It seems that in order to have ftp for .mdb files in Windows XP Home SP
2 I am forced to use the Windows Firewall.

Sygate was a "no go" as detailed above. I have now tried Kerio/Sunbelt
and again Windows Firewall, despite being disabled, retains control of
Port 21.

The downsides of using Windows Firewall are:
Windows Firewall only blocks incoming traffic not outgoing
WF apparently does a good job at "stealthing ports" however Port 21 is
no longer stealthed when applying the fix detailed above.

If anyone knows of a good firewall that manages to overide WF please
let me know!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top