UNIX for Dummies Questions & Answers

The problem client cant access other files that we also know 100% work on the other machines, the same thing happens after the command is issued: "Can't build data connection"



So, we know it can connect to the UNIX and log into the FTP but it has a problem accessing the files within that user login, could this be a permissions issue? I have no idea how the permissions would change (the user certainly wouldn't have a clue how to even access UNIX never mind change permissions). v strange.

"Can't build data connection" means it can't start the data (second stage) of the ftp. (See the active vs passive explanation link I posted).

Why can't you take down the firewall on that client? Does it give you an error (eg, permission denied) or do you need to be given the steps.

No guarantees but I reckon the firewall could be the problem and if I were you I'd definitely need to eliminate it from the investigation.

---------- Post updated at 10:10 AM ---------- Previous update was at 09:54 AM ----------

I just took down the firewall on a Windows 7 client that I have here and this is exactly how I did it. I'm not saying that this will work for you but post any error that you get.

Start > Control Panel
Click on the actual words "Network and Internet"
Click on "System and security" in the left column
Click on the actual words "Windows firewall"
Click on "Turn Windows firewall on or off" in the left column
Set any/all firewall options to "off"
Click OK

Obviously this is just for testing purposes.

---------- Post updated at 10:13 AM ---------- Previous update was at 10:10 AM ----------

And for the record, what AV are you using?

I have even logged on as Administrator and still get the greyed out box!

Hmmmmmm!!!

Does a client that works on ftp allow you to turn off it's firewall?

No, the others that we know work on FTP also display this same firewall lockdown.

I have tried to access the Firewall on the main domain controller, but it blocks me saying:

"Windows Firewall cannot run because another program or service is running that might use the Network Address Translation Component (Ipnat.sys)" - This may be opening other cans of worms but WTF ?

Our AV is AVG 2013 Business Edition.

There's quite a discussion on Microsoft forum about firewall:

Can't turn off Win 7 domain firewall

I'm not an expert on Windows and I recommended you switch off the firewall for good measure. It's just a logical step. However, messing with domain controllers in a production environment is not recommended.

It might be easier to take that client off the domain, test ftp, and then put it back on the domain rather than mess with domain settings.

Need a Windows expert.

---------- Post updated at 10:36 AM ---------- Previous update was at 10:31 AM ----------

Another thing I would do is ping the client from the unix box then shutdown the client to check the ping fails just in case duplicate ip address exists. Perhaps when the unix box "calls back" during the ftp it's routing elsewhere and not getting to that client. Just a thought.

There is not response from pinging when client is shutdown.

I feel messing with DHCP isnt the answer here as it would be the same for everyone, the fact that these settings are applied across the board, makes me think its not the correct avenue to explore.