DIrectFTP problem : AT&T Uverse...

User 227784 Photo


Registered User
10 posts

Hello:

Short version
I need to be able to configure my FTP reported IP address because AT&T uVerse reports the wrong IP address (local IP address of the PC (ex. 192.168.1.xx).

I cannot figure out how to do it with v 6.6. I should update to 6.9 but does that have that feature, or do I have to alter a setting in the router/other network gear?

AT&T can't help without me paying for a support call or subscription but I won't repeat my thoughts on that here.

Thank you

Murray
---------
Long detailed version:
Since we were 'upgraded' to AT&T uVerse, at both home and business (two locations) I have not been able to use any FTP program. Direct FTP simply says authentication failed (error 530).

By trying other programs I found one that reports the wrong IP address was being sent instead of the actual one (the correct one matches a 'what's my IP' online query).

I used WIreShark to see what was being sent out, and I was surprised to see the AT&T network equipment was passing my 'local' IP address 192.168.1.xx!

I figured out how to change my 'real' IP address in the other program but it's no longer available for XP so it's not an option. I changed both home PC's to Linux, found an FTP program that allows configuration of the 'real IP address' and got it working.

On to the business location, still running XP, and the only FTP software I have is DirectFTP. How can I address (ha-ha) this problem?
User 2147626 Photo


Senior Advisor
2,942 posts

Your internet server ... is it a Linux based server, or Windows IIs ?

If Windows IIs, then read through this ... http://support.microsoft.com/kb/200475

If not, then post back and let us know.
Graphics for the web, email, blogs and more!
-------------------------------------
http://sadduck.com
User 271657 Photo


Senior Advisor
3,816 posts

I would move on to the latest version (6.9.2) before trying anything else.

I've been with Uverse for a few years and have had no problems with Direct FTP (or any other FTP) at all. No special settings required, no need to do anything with IP addresses. Uverse never comes into the picture. The only thing that ever matters is making sure the FTP info is correct. It really shouldn't matter who your internet provider is.
Have you checked with your hosting account to make sure your info is correct?

Found this on the interwebs:
If you have installed, or convenienty has been installed for your benefit, XP SP2, FTP will be blocked by the "new and improved" Microsoft built-in firewall.

Have you tried uploading with all your security off?

Let us know if you get it figured out or not :)
I love deadlines. I like the whooshing sound they make as they fly by. (Douglas Adams)
https://www.callendales.com
User 227784 Photo


Registered User
10 posts

Hello:

1) Server is Linux-based

2) PC at business has XP Pro + SP3, was same at home until I went to Ubuntu Linux

3) I don't remember if I've tried FTP with AV, Firewall, etc. disabled, not recently. I am using McAfee & firewall.

4) I agree one's ISP shouldn't matter, but I mentioned AT&T because as our ISP, they provide the hardware & basic network configuration requirements. The "wrong IP address" diagnosis reported by Filezilla was confirmed and corrected by 'forcing' the correct IP address through a configuration option Filezilla has.

5) I downloaded DirectFTP 6.9.2 on the XP Pro PC at the business and it worked. On the Ubuntu PC at home I ended up using Filezilla, and had the same problem I did with the same PC (XP Home at that time) using Direct FTP (6.x) and Filezilla. Under XP, forcing the correct IP address by manually entering it where prompted worked, and now that I have Ubuntu on it, same thing resolved it.

I don't know the internal workings of v.6.9.2 vs. whichever earlier v.6 I had or if removing it and reinstalling it would have fixed it, but 6.9.2 solved my problem on the XP Pro machine.

I also read in the CoffeeCup DirectFTP 'I Can't Connect' troubleshooting tips (I think) that configuration issues behind a firewall can impact connection. While my problem is solved, it would still be interesting to understand what the preset connection info is if case this happens again, or as feedback in case the number of people who have connection problems is larger than just me (some connection failures may not be 'labeled' with the same description I've created so they're not correlated as similar. Maybe it wouldn't really be that interesting ;O). Network stuff is not really something I get thrilled about.

Thanks for the help.


Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.