Hello Everyone For an issue that is probably pretty simple to fix, it was really hard to come up with a subject that had any relation to the problem... Anyway, here goes.
I have a Fedora 8 and a Fedora 10 system hooked up to a cable (Comcast) internet connection through a Linksys router. The Fedora 8 system is relatively old(?): 1.8 GHZ AMD 32bit processor with 1 gig of RAM. The Fedora 8 system also runs a webserver and a mail server. The Fedora 10 system has an Intel Xeon 2Ghz Quad Core Processor with 8 Gigs of RAM.
The issue is that when I attempt to access either of the two following locations (both served on on Fedora 8 system I referred to earlier) the pages never stop loading: http://www.afolkey2.net/squirrelmail http://www.afolkey2.net/gallery2/main.php
For example, after a few minutes of loading, this is what my Gallery2 installation looks like when viewed in Firefox 3.0.10: http://www.afolkey2.net/~steve/Fedora10-Gallery2atAfolkey2Net.jpg
The next screenshot was taken after I ssh'd into my Fedora 8 box and ran Firefox from that box. Here is the result after just a few moments of loading: http://www.afolkey2.net/~steve/Fedora8-Gallery2atAfolkey2Net.jpg
My Gallery2 installation also works perfectly at every other computer that I've tried it on. In fact, just this morning I ran some administrative tasks from a Windows 2003 thin client at the place that I work at. I was very pleased with the very zippy performance of my Gallery2 install.
So, my humble opinion is that the issue is a network configuration issue on my system, since the two radically different performance scenarios described above are occuring on two systems that are hooked up the the same router.
I have a feeling that this is a relatively simple fix, but it is beyond my current skills...
So, thank you in advance for any help you can give me.
Steven P. Ulrick
P.S.: I just remembered that this issue is not confined to Firefox. I have tried all of this with Opera, Konqueror and Dillo, with the same results. (In the case of Dillo, understanding that of course it appears to have no CSS support, so even if the page ever finished loading, it would look markedly different than it is supposed to.
Steven P. Ulrick wrote:
So, my humble opinion is that the issue is a network configuration issue on my system, since the two radically different performance scenarios described above are occuring on two systems that are hooked up the the same router.
Your webserver is probably waiting a lot of time for each one of the files it is serving.
DNS resolution issues? ECN? (cat /proc/sys/net/ipv4/tcp_ecn) MTU problems? (try if "ifconfig eth0 mtu 576" on the F10 machine helps)
Do pages finally load after a long time or do they really hang for ever?
A "tcpdump -i eth0" on F10 could help in understanding what's happening on the network.
Best regards.
On Sun, 24 May 2009 12:54:42 +0200 Roberto Ragusa mail@robertoragusa.it wrote:
Steven P. Ulrick wrote:
So, my humble opinion is that the issue is a network configuration issue on my system, since the two radically different performance scenarios described above are occuring on two systems that are hooked up the the same router.
Your webserver is probably waiting a lot of time for each one of the files it is serving.
DNS resolution issues? ECN? (cat /proc/sys/net/ipv4/tcp_ecn) MTU problems? (try if "ifconfig eth0 mtu 576" on the F10 machine helps)
Do pages finally load after a long time or do they really hang for ever?
A "tcpdump -i eth0" on F10 could help in understanding what's happening on the network.
First off, thank you very much for your help. Some time after I sent my original message to the list, my brother suggested that I try this: http://192.168.1.100/gallery2/main.php (192.168.1.100 being the IP address of our system that has the server running on it.) This worked perfectly. Of course, I shouldn't have to replace the domain name with the IP address just to run Gallery2 and Squirrelmail from our new Fedora 10 system. So, inspiration struck me, and the problem has been fixed ever since. The complete fix was adding this line to the "Problem System": 192.168.1.100 afolkey2.net www.afolkey2.net
So, I put a line in 192.168.1.101's /etc/hosts file telling it to map requests for afolkey2.net and www.afolkey2.net to 192.168.1.100 (the address of our server.) Perfectly solved my problem :)
Again, thank you for your efforts on my behalf.
Steven P. Ulrick