Joe, Here is the XP output of "ipconfig /all":
Windows IP Configuration Host Name . . . . . . . . . . . . : rosmond Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain_not_set.invalid Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : domain_not_set.invalid Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller Physical Address. . . . . . . . . : 48-5B-39-B9-FB-74 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.100 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 216.177.225.9 Lease Obtained. . . . . . . . . . : Saturday, September 14, 2013 3:55:02 AM Lease Expires . . . . . . . . . . : Sunday, September 15, 2013 3:55:02 AM And here is the SL "dhclient-eth0.leases" file: lease { interface "eth0"; fixed-address 192.168.1.100; option subnet-mask 255.255.255.0; option routers 192.168.1.1; option dhcp-lease-time 86400; option dhcp-message-type 5; option domain-name-servers 192.168.0.1,216.177.225.9; option dhcp-server-identifier 192.168.1.1; option domain-name "domain_not_set.invalid"; renew 0 2013/09/15 04:02:33; rebind 0 2013/09/15 13:42:29; expire 0 2013/09/15 16:42:29; } I must say, to my untrained eye, it looks like the files display equivalent information. Still a mystery why the SL browser response is so much slower! T. Rosmond On Fri, 2013-09-13 at 19:49 -0700, Joseph Areeda wrote: > Tom, > > No, that's the next step. It looks up the URL then sends a request, > that message is displayed while it's waiting for a response. > > BTW the command to find DNS servers in XP is "ipconfig /all" > > Sorry to take you down the wrong path, > > Joe > > On 09/13/2013 07:13 PM, Tom Rosmond wrote: > > Joe, > > > > Same behavior. And earlier I was mistaken, because I notice that during > > most of the delay the message: > > > > "Waiting for www.google.com" > > > > is what is shown by Firefox, not "looking up google.com". Is that > > consistent with a lookup problem? > > > > T. Rosmond > > > > > > > > On Fri, 2013-09-13 at 18:42 -0700, Joseph Areeda wrote: > >> Hi Tom, > >> > >> With those numbers which are very good, I would expect the "looking up > >> google.com" message to be up for less than a second. > >> > >> It is very possible that the address is cached somewhere, the router > >> perhaps or SL itself. > >> > >> Would you do one more thing for good measure, please? Run these dig > >> commands and verify the query times are still in the sub 50ms range. > >> Then start up firefox and see what happens. If this is truly the > >> problem firefox should not show any delay and should get there as fast > >> as XP. > >> > >> If it takes it usual 6 to 8 seconds it is probably something else. > >> > >> Good luck, > >> > >> Joe > >> > >> On 09/13/2013 06:08 PM, Tom Rosmond wrote: > >>> Joe, > >>> > >>> Here is the output from 'dig google.com': > >>> > >>> --------------------------------------------------- > >>> > >>> ; <<>> DiG 9.7.3 <<>> google.com > >>> ;; global options: +cmd > >>> ;; Got answer: > >>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33839 > >>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 0 > >>> > >>> ;; QUESTION SECTION: > >>> ;google.com. IN A > >>> > >>> ;; ANSWER SECTION: > >>> google.com. 137 IN A 173.194.33.1 > >>> google.com. 137 IN A 173.194.33.9 > >>> google.com. 137 IN A 173.194.33.0 > >>> google.com. 137 IN A 173.194.33.6 > >>> google.com. 137 IN A 173.194.33.4 > >>> google.com. 137 IN A 173.194.33.5 > >>> google.com. 137 IN A 173.194.33.2 > >>> google.com. 137 IN A 173.194.33.3 > >>> google.com. 137 IN A 173.194.33.8 > >>> google.com. 137 IN A 173.194.33.14 > >>> google.com. 137 IN A 173.194.33.7 > >>> > >>> ;; Query time: 22 msec > >>> ;; SERVER: 192.168.0.1#53(192.168.0.1) > >>> ;; WHEN: Fri Sep 13 17:38:19 2013 > >>> ;; MSG SIZE rcvd: 204 > >>> > >>> ----------------------------------------------------------------------------- > >>> > >>> > >>> And here from 'dig @8.8.8.8 google.com': > >>> > >>> ---------------------------------------------------------------------------- > >>> > >>> ; <<>> DiG 9.7.3 <<>> @8.8.8.8 google.com > >>> ; (1 server found) > >>> ;; global options: +cmd > >>> ;; Got answer: > >>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11128 > >>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 0 > >>> > >>> ;; QUESTION SECTION: > >>> ;google.com. IN A > >>> > >>> ;; ANSWER SECTION: > >>> google.com. 256 IN A 173.194.33.38 > >>> google.com. 256 IN A 173.194.33.39 > >>> google.com. 256 IN A 173.194.33.35 > >>> google.com. 256 IN A 173.194.33.33 > >>> google.com. 256 IN A 173.194.33.40 > >>> google.com. 256 IN A 173.194.33.34 > >>> google.com. 256 IN A 173.194.33.41 > >>> google.com. 256 IN A 173.194.33.46 > >>> google.com. 256 IN A 173.194.33.36 > >>> google.com. 256 IN A 173.194.33.32 > >>> google.com. 256 IN A 173.194.33.37 > >>> > >>> ;; Query time: 28 msec > >>> ;; SERVER: 8.8.8.8#53(8.8.8.8) > >>> ;; WHEN: Fri Sep 13 17:38:24 2013 > >>> ;; MSG SIZE rcvd: 204 > >>> > >>> ------------------------------------------------------------------------------ > >>> > >>> > >>> > >>> > >>> As you see, there seems to be little to choose between them, and even > >>> though the SERVER is different, I don't see any notice of a timeout. > >>> > >>> I do have access to my DSL modem, and I think I will contact my ISP for > >>> suggestions. > >>> > >>> Thanks for the help > >>> > >>> T. Rosmond > >>> > >>> > >>> > >>> > >>> On Fri, 2013-09-13 at 17:31 -0700, Joseph Areeda wrote: > >>>> Hi Tom, > >>>> > >>>> I'm not sure how to find it in XP either especially when DHCP is > >>>> involved. I have been meaning to set up an XP VM maybe that will get > >>>> done soon enough to be of some help. > >>>> > >>>> It's not uncommon for home routers to act as a local DNS server but I > >>>> suspect it may be misconfigured and what's happening is SL requests a > >>>> resolution from the router, it times out and then goes onto the ISP's. > >>>> > >>>> You can verify this from SL by comparing "dig google.com" with "dig > >>>> @8.8.8.8 google.com" where 8.8.8.8 is google's public dns server and > >>>> the only one who's IP I know by heart. Toward the end of the crap it > >>>> prints out is > >>>> ;; Query time: 47 msec > >>>> ;; SERVER: 8.8.8.8#53(8.8.8.8) > >>>> I suspect you'll find the default probably reporting a time out for > >>>> your router then reporting the ISP's dns. > >>>> > >>>> Hopefully you know the passwords for your DSL Router (and your ISP is > >>>> nice enough to give it to you). I would guess it's an easy change to > >>>> configure the DNS servers it uses correctly. > >>>> > >>>> Joe > >>>> > >>>> On 09/13/2013 05:14 PM, Tom Rosmond wrote: > >>>> > >>>>> On Fri, 2013-09-13 at 16:41 -0700, Joseph Areeda wrote: > >>>>>> One more thing: Firefox will display what it's doing in the status > >>>>>> line > >>>>>> at the bottom, I think "looking up google.com" will be displayed > >>>>>> during the name resolution operation. > >>>>> Yes, that is what is displayed. > >>>>> > >>>>> > >>>>>> Joe > >>>>>> > >>>>>> On 09/13/2013 04:36 PM, Joseph Areeda wrote: > >>>>>>> My first guess is a DNS issue are they both using the same DNS server > >>>>>>> as > >>>>>>> their first choice? 6 to 8 sec smells like a timeout on the first > >>>>>>> lookup. > >>>>>>> > >>>>>>> Just a SWAG that has bit me before. > >>>>>>> > >>>>>>> Joe > >>>>>>> > >>>>>>> On 09/13/2013 11:46 AM, Tom Rosmond wrote: > >>>>>>>> I run a dual boot (SL 6.4/Windows XP) workstation. SL is 64 bit, XP > >>>>>>>> is > >>>>>>>> 32 bit. I have Firefox and Konqueror browsers on SL; Firefox, IE, > >>>>>>>> and > >>>>>>>> Google Chrome on XP. For all browser choices I notice that when my > >>>>>>>> browser home page loads (Google.com for all cases), the XP load times > >>>>>>>> are very quick (< 1 sec), but painfully slow for SL (6-8 secs). I > >>>>>>>> recently upgraded SL from 5.5 to 6.4, but I had the same symptoms > >>>>>>>> before > >>>>>>>> the change. > >>>>>>>> > >>>>>>>> Here are some data points: > >>>>>>>> > >>>>>>>> 1. Firefox: 17.0.8 on SL, 23.0.1 on XP > >>>>>>>> 2. Temporarily disabling SELinux made no difference > >>>>>>>> 3. Temporarily disabling all plugins on SL Firefox made no > >>>>>>>> difference. > >>>>>>>> 4. After the SL home page loads switching to other URL's is > >>>>>>>> noticeably > >>>>>>>> slower than with XP. > >>>>>>>> > >>>>>>>> Is this some kind of authentication hangup? I have looked at the > >>>>>>>> various logs, but can't see anything. But I am not an expert in this > >>>>>>>> area, so maybe I don't know what to look for. > >>>>>>>> > >>>>>>>> Any insights or suggestions? > >>>>>>>> > >>>>>>>> > >>>>>>>> T. Rosmond > > >