Thanks - I believe it is a DNS issue here. Doug On Thu, 2006-02-16 at 11:50 +1100, JeRRy wrote: > <snip> > from ping times: > (localhost while ssh'd into the server and "ping localhost") > 64 bytes from localhost (127.0.0.1): icmp_seq=0 ttl=64 time=0.030 ms > 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.024 ms > 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.023 ms > 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.022 ms > 64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.023 ms</snip> > > > Looks normal! > > <snip> > (arping from my internal network to the server in the DMZ by IP > address) > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 8.874ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.134ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.135ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.131ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.022ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.057ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.133ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.142ms > </snip> > > hmmm... Interesting results! > > <snip> > (arping from my internal network to the server in the DMZ by name) > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.404ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.141ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.155ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.137ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.150ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.139ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.137ms > Unicast reply from 10.XX.XX.XX [00:0A:F4:F9:C3:00] 1.147ms > </snip> > > Considerbly slow. > > <snop> > (ping from outside network on windows pc in cli) > Reply from 65.5.48.10: bytes=32 time=14ms TTL=62 > Reply from 65.5.48.10: bytes=32 time=9ms TTL=62 > Reply from 65.5.48.10: bytes=32 time=11ms TTL=62 > Reply from 65.5.48.10: bytes=32 time=7ms TTL=62 > </snip> > Okay, > > just FYI I pinged this IP, I got INSTANT responses. I'll try again,.... And again had no problems. > > Are you have any problems loading other pages fast on WINDOWS? > > The domain is www.fpunet.com - the httpd.conf file lists the index.php > as the first index type and also it is defined that way in the virtual > server portion of the config. I have the phpinfo page set as the > default index right now. I noticed that "Virtual Directory Support" is > "disabled". Could this be the source of my problem? > Doug > > I loaded your domain and got a instant reply and loaded the website promply. Some people fall in the trap and think if hhtpd.conf is right than nothing to worry about. Which is WRONG! httpd.conf is not the ONLY file loaded within a server load. I can go in and hack the hell out of it, and override the index.php config in another file! > > .htaccess was not made for a waste of space. > > Create a .htaccess file, if not already done, point the server to read *.php, *.phps, *.cgi etc... > > But that is not your issue. I think your issue lies with your ISP to be honest. Loading times vary, why not grab your IP and go to a website that checks how many "hops" before it hits your website, try a few websites. There is many downloads available on this. Did you know one hop down could cause slow loading times or even a page not loading at all? > > Again ISP issue. > > Jerry > > -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
