Red Hat Bugzilla – Bug 47862
FTPD will work only if connected to ISP.
Last modified: 2007-04-18 12:34:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.5 i686)
Description of problem:
With 7.1+ it seems that some services require connectivity to the Internet
properly, even if one wants merely to talk to another machine on the local
Steps to Reproduce:
1.Configure a local LAN (more than one machine) using 192.168.80.*
2.Use one machine as dialup Internet server for all others (using IP masq
3.Try to use ftp between machines on the LAN while the server is NOT
Internet. This will cause FTPD to hang forever.
Actual Results: FTPD hangs without prompting for username and password
Expected Results: FTPD should prompt for usename and password
When I try to use Sun's latest Java JDK v1.4.0 and run the demo's, they run
if I were trying to run them on a remote machine with X-windows redirected
using the DISPLAY variable, even when I run them on the local machine. This
slows down the JDK and causes font problems as well.
In general, it appears that 7.1+ RedHat forces connections to go to the
back, slowing things down and causing other problems.
Forgot to mention: I cannot install Borland's JBuilder4, even after upgrading to
256MB of RAM.
The installation program hangs for a long time, then the first install window
appears, but then
everything just stalls. I suspect that this is because the OS is in effect
installing this large
program "remotely" even though it is actually installed locally. I tested this
install under Linux 6.1
and it worked. Perhaps it is my X server? (Intel 815?). The relationship to the
is the round-trip to the Internet, or so it seems to me.
Being just another Red Hat Linux user, I can't confirm this misbehaviour. Maybe
you have a bad default route configured?
The ftpd problem is almost certainly caused by a broken DNS setup.
wu-ftpd will hang for 60 seconds (hardly forever ;) ) if it can't perform a
reverse lookup of the IP trying to connect.
The JBuilder problem doesn't have anything to do with this; If it worked in
6.1, my guess is they're linking dynamically to libraries we no longer ship,
such as ancient versions of libstdc++ or glibc, possibly even libc5.
Since I don't have JBuilder and it isn't free, I can't debug this; please
report this to Borland. It's their problem.