• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

FTP to WAN IP is all screwed up

K

kenshorin

Golden Member
For some reason, I can't get FTP to work over my WAN IP using Red Hat 7.2. It establishes an initial connection, but then something in DNS is causing the session to hang. I've already put into ftpaccess to not worry about recursive by the dns resolveroptions -recurse option. Its weird. Telnet, ssh, even sftp work to the WAN IP but not plain ol' ftp, and thats what I want to work more than anything. It has something to do with the way AT&TBI has their network set up, this same setup worked pretty much OK on the old MediaOne. I need it to skip doing dns lookups for the ftp sessions, because its seems to be failing there somehow.

Unrelated question, anyone know how to make Red Hat 7.2 broadcast the hostname? Using RH 6.2 I can see the hostname on my Netopia router, but not with 7.2. Right now with 7.2 it only shows the MAC address for my NIC. I want it to show the hostname in case I set up a few more machines, which I want to do after I get this ftp deal straightened out. Any ideas?
 
Already did that. Didn't help at all. The problem is, wu-ftpd is still trying to resolve, even without a resolv.conf and with the -recurse options. For some reason the option works for local ip's but not for internet ones. The main issue I think is that since AT&T is taking over Mediaone's IP's, my WAN IP is resolving to two hostnames (a new AT&T one, and an old Mediaone one.) Is it possible that ftp CLIENTS and not the server are checking to resolve hostnames? Weird...
 


<< Already did that. Didn't help at all. The problem is, wu-ftpd is still trying to resolve, even without a resolv.conf and with the -recurse options. For some reason the option works for local ip's but not for internet ones. The main issue I think is that since AT&T is taking over Mediaone's IP's, my WAN IP is resolving to two hostnames (a new AT&T one, and an old Mediaone one.) Is it possible that ftp CLIENTS and not the server are checking to resolve hostnames? Weird... >>



Its possible. Im going to blame it on wu "You've probably already been 0wn3d" ftp.
 
It is most likley a reverse lookup problem in that you are running into.

The servers will do a reverse lookup when you connect to see if your Reverse lookup answer comes back as what you say your DNS entry is. If you are in the middle of a change most likley it will fail and the service on their end will drop your connection request.

There is unfortunatly nothing you can do besides get your ISP to fix the resolution issue.
 


<< It is most likley a reverse lookup problem in that you are running into.

The servers will do a reverse lookup when you connect to see if your Reverse lookup answer comes back as what you say your DNS entry is. If you are in the middle of a change most likley it will fail and the service on their end will drop your connection request.

There is unfortunatly nothing you can do besides get your ISP to fix the resolution issue. >>



It cant do dns lookups if there is no dns server setup. Its a legitimate fix for the problem for most daemons (known to work with sshd).
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top