Firefox freezes during DNS lookup

On many pages, especially almost any eBay page, firefox gets part way through loading the page and then freezes. Sometimes it eventually finishes loading, but it may be after many minutes. The title of my question is because the firefox status bar always shows a message about looking up some URL during the freeze. I've tried safe mode, and it has no effect on the problem. I've checked for current updates of all plugins, especially Flash. Nothing changes this behavior.
Some web pages load without this effect. On the same computer, neither IE nor Chrome has any problem with the same pages that freeze Firefox.

can you try to reproduce this issue on Firefox 10?
* getfirefox.com

Similar Messages

When loading Firefox i get (DNS Lookup error) any advise please

on loading Firefox 4 the only page that comes up is
DNS lookup error

Try re-installing Java. See [[Using the Java plugin with Firefox]]
A quick search for jqsnotify.exe on Google indicates that it is related to the Java quick start option.

Firefox freezes during various operations (scrolling, filling form fields, clicking through the options menu, etc.)

Almost any activity in Firefox is subject to brief freezing. The freeze lasts anywhere from (approx.) 1/2 second to 3 seconds. I searched online and I came across an article stating the freezes may be due to Anti-Virus software. The work-around presented was to set browser.sessionstore.enabled to false. The idea is Firefox does not attempt to write to a file, and so my AV software doesn't waste time checking if the access is valid. The change had some positive effect. The freezes now occur less often.
However, the freezes still occur every few seconds, still to the point of major annoyance. So what I did was run Process Monitor while Firefox was running to see if the freezes coincided with file accesses. Indeed they do.
I would like to know if I can change a setting which will cause Firefox to not access these files (or files like these) so often:
firefox.exe QueryOpen C:\WINDOWS\system32\msimtf.dll
firefox.exe ReadFile C:\Documents and Settings\<username>\Local Settings\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\Cache\_CACHE_001_
firefox.exe LockFile C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\content-prefs.sqlite
firefox.exe QueryOpen C:\Documents and Settings\<username>\Local Settings\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\Cache\5ACD1B8Ed01
firefox.exe WriteFile C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\cookies.sqlite-journal
There are hundreds of such accesses over just tens of seconds. These files are accessed while I'm e.g. scrolling down the page. I could understand if they were accessed while loading or drawing the page, but again this is occurring while I'm merely scrolling down the page and typing in this very text box!

Almost any activity in Firefox is subject to brief freezing. The freeze lasts anywhere from (approx.) 1/2 second to 3 seconds. I searched online and I came across an article stating the freezes may be due to Anti-Virus software. The work-around presented was to set browser.sessionstore.enabled to false. The idea is Firefox does not attempt to write to a file, and so my AV software doesn't waste time checking if the access is valid. The change had some positive effect. The freezes now occur less often.
However, the freezes still occur every few seconds, still to the point of major annoyance. So what I did was run Process Monitor while Firefox was running to see if the freezes coincided with file accesses. Indeed they do.
I would like to know if I can change a setting which will cause Firefox to not access these files (or files like these) so often:
firefox.exe QueryOpen C:\WINDOWS\system32\msimtf.dll
firefox.exe ReadFile C:\Documents and Settings\<username>\Local Settings\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\Cache\_CACHE_001_
firefox.exe LockFile C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\content-prefs.sqlite
firefox.exe QueryOpen C:\Documents and Settings\<username>\Local Settings\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\Cache\5ACD1B8Ed01
firefox.exe WriteFile C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Profiles\k33hi6th.default\cookies.sqlite-journal
There are hundreds of such accesses over just tens of seconds. These files are accessed while I'm e.g. scrolling down the page. I could understand if they were accessed while loading or drawing the page, but again this is occurring while I'm merely scrolling down the page and typing in this very text box!

Firefox freezes during computer shut down, stopping shut down.

I have to Force Quit Firefox to complete shut down.
I have also had some mysterious momentary events when the screen goes blue. I have had these when starting up occasionally too.
Firefox 9.0.1, OS X.6.8, MacBook Pro 7.1.

Do you have that problem when running in the Firefox SafeMode? <br />
[http://support.mozilla.com/en-US/kb/Safe+Mode] <br />
''Don't select anything right now, just use "Continue in SafeMode."''
If not, see this: <br />
[http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

RV082 - Newest Firmware - V1 Hardware? - Slow DNS Lookups

I was running firmware 1.3.98-tm - and everything seemed to be working fine (no complaints from me - things ripped)
Serial Number :      DEZ00610370x
Firmware version :      1.3.98-tm (Jun 20 2008   18:37:29)
CPU :    Intel IXP425-533
Not sure if I have V1 or V2 hardware - or how to tell.
But that said - I upgraded to 2.0.0.19-tm yesterday. Upgrade went smoothly. All settings seemed to be retained after upgrade.
It now seems that DNS lookups intermittently fail - and/or are definitely slower.
I am assuming it is the DNS lookup that is taking more time (or failing) - as I use a product from Firetrust called Mailwasher Professional - which every 15 minutes - connects to all of my POP3 servers (about 8 of them - simultaneously) - and attempts to download a portion of each message for some Bayesian analysis. During the initial connection attempts - multiple failures occur with multiple e-mail accounts - indicating messages like "No Such Host". On a retries - it either works - or - produces the same error. What is further weird - when I set the Mailwasheer product to check each of the accounts "serially" - one by one - no errors occur. Problem seems to evidence itself only when router is presented with multiple lookups. The same behavior is evidenced within Firefox - when checking for updates to my extensions(much slower with the new firmware)
I backed out the firmware upgrade - and every is now working satisfactorily. Re-apply the new firmware - and the DNS weirdness returns.
Anyone out there having similar problems - or have any ideas?
I like running with the latest firmware - but I just can't live with this level of performance degradation.
Regards,
Doug
Environment:
Windows® Vista® Ultimate SP2 64-bit {EN}
Intel® Core™2 Quad Q9400 / Memory: 4GB
Intel® 82562V-2 10/100 Network Connection

Just tried that - but problem still ocurrs ??? Somehow the "router" is still "in the way".
Regards,
Doug
Network Setting Status
LAN                  IP :
192.168.1.1
WAN1 IP :
69.113.140.xxx
WAN2 IP :
0.0.0.0
Mode :
Gateway
DNS (WAN1) :
DNS (WAN2) :
167.206.254.2      167.206.254.1
DDNS(WAN1   |   WAN2)                 :
Off       |       Off
DMZ                  Host :
Disabled
DNS
DNS Server                    (Required) 1:
2:

[SOLVED] Slow DNS lookup, I think

Hi
I have a really annoying problem. My DNS lookup in Arch is painfully slow. I know it's not a network problem, as I don't have any problems in my Ubuntu installation. I have tried to run two simple tests to show you what I mean. The first is a simple ping google.
########### Ubuntu ###########
carsten@carsten-laptop:~$ time ping -c 3 www.google.com
PING www.l.google.com (216.239.61.104) 56(84) bytes of data.
64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=1 ttl=245 time=17.4 ms
64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=2 ttl=245 time=20.6 ms
64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=3 ttl=245 time=11.4 ms
--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 11.465/16.529/20.641/3.809 ms
real 0m2.290s
user 0m0.000s
sys 0m0.004s
########### Arch ###########
carsten ~/Desktop $ time ping -c 3 www.google.com
PING www.l.google.com (216.239.61.104) 56(84) bytes of data.
64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=1 ttl=245 time=12.3 ms
64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=2 ttl=245 time=10.7 ms
64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=3 ttl=245 time=12.4 ms
--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2007ms
rtt min/avg/max/mdev = 10.776/11.867/12.476/0.778 ms
real 0m15.305s
user 0m0.013s
sys 0m0.007s
Ubuntu: 0m2.290s vs. Arch: 0m15.305s.
In the second test I tried to fake a pacman update by downloading the .db files from my primary server. On both Ubuntu and Arch I used this simple script
repos=( core extra community )
time for repo in ${repos[@]}
do
wget http://archlinux.unixheads.org/$repo/os/i686/$repo.db.tar.gz
done
When I run it in, I get this result
########### Ubuntu ###########
carsten@carsten-laptop:~/Desktop$ ./updatetest
--2008-11-10 07:58:23-- http://archlinux.unixheads.org/core/os/i686/core.db.tar.gz
Resolving archlinux.unixheads.org... 204.152.186.174
Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 32515 (32K) [application/x-gzip]
Saving to: `core.db.tar.gz'
100%[=============================================================>] 32.515 --.-K/s in 0,1s
2008-11-10 07:58:23 (331 KB/s) - `core.db.tar.gz' saved [32515/32515]
--2008-11-10 07:58:23-- http://archlinux.unixheads.org/extra/os/i686/extra.db.tar.gz
Resolving archlinux.unixheads.org... 204.152.186.174
Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 422622 (413K) [application/x-gzip]
Saving to: `extra.db.tar.gz'
100%[=============================================================>] 422.622 242K/s in 1,7s
2008-11-10 07:58:25 (242 KB/s) - `extra.db.tar.gz' saved [422622/422622]
--2008-11-10 07:58:25-- http://archlinux.unixheads.org/community/os/i686/community.db.tar.gz
Resolving archlinux.unixheads.org... 204.152.186.174
Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 369845 (361K) [application/x-gzip]
Saving to: `community.db.tar.gz'
100%[=============================================================>] 369.845 206K/s in 1,8s
2008-11-10 07:58:27 (206 KB/s) - `community.db.tar.gz' saved [369845/369845]
real 0m3.837s
user 0m0.016s
sys 0m0.036s
########### Arch ###########
carsten ~/Desktop $ ./updatetest
--2008-11-10 08:01:33-- http://archlinux.unixheads.org/core/os/i686/core.db.tar.gz
Resolving archlinux.unixheads.org... 204.152.186.174
Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 32515 (32K) [application/x-gzip]
Saving to: `core.db.tar.gz'
100%[==============================================================================>] 32,515 --.-K/s in 0.1s
2008-11-10 08:01:47 (303 KB/s) - `core.db.tar.gz' saved [32515/32515]
--2008-11-10 08:01:47-- http://archlinux.unixheads.org/extra/os/i686/extra.db.tar.gz
Resolving archlinux.unixheads.org... 204.152.186.174
Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 422622 (413K) [application/x-gzip]
Saving to: `extra.db.tar.gz'
100%[==============================================================================>] 422,622 253K/s in 1.6s
2008-11-10 08:02:02 (253 KB/s) - `extra.db.tar.gz' saved [422622/422622]
--2008-11-10 08:02:02-- http://archlinux.unixheads.org/community/os/i686/community.db.tar.gz
Resolving archlinux.unixheads.org... 204.152.186.174
Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 369845 (361K) [application/x-gzip]
Saving to: `community.db.tar.gz'
100%[==============================================================================>] 369,845 262K/s in 1.4s
2008-11-10 08:02:17 (262 KB/s) - `community.db.tar.gz' saved [369845/369845]
real 0m44.153s
user 0m0.047s
sys 0m0.017s
Ubuntu: 0m3.837s vs. Arch: 0m44.153s
I get the same update time whenever I update pacman normally.
I have googled a lot to figure out an answer, but nothing helps, so I was hoping somebody could help me figure this out, as it's very annoying. My hosts file looks like this
hosts:
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost arch
# End of file
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Asia/Singapore"
KEYMAP="dk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(e100 mii iwl3945 fuse acpi-cpufreq cpufreq_ondemand cpufreq_conservative cpufreq_powersave loop !pcspkr !snd_pcsp)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="arch"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network hal !netfs crond fam wicd cups laptop-mode oss gdm)
SPLASH="splashy"
Thanks in advance!
Last edited by Sharpeee (2008-11-15 10:39:42)

Just tried to remove the "search..." line from my /etc/resolv.conf file, but nothing! It's okay if I remove the line after it connects right? Wicd overwrites the file anyways if I reconnect.
I don't really think changing to a different network-manager will help me. It works perfectly fine in Ubuntu with both network-manager and wicd, do don't think that's the problem. It must be a configuration file somewhere.
#### EDIT ####
I just tried to disable wicd and enable the wired network in /etc/rc.conf. After a reboot and it's still the same, even on the wired, so it's got be some other settings somewhere that's messing things up!
Also, for some reason my theme, in Gnome, isn't loaded after I disabled wicd? I have to manually run "gnome-appearance-manager"??
Last edited by Sharpeee (2008-11-11 05:01:46)

Wireless Intermittent Super Slow DNS lookup bug in 10.6.4

I don't normally post things on forums these days, as usually I can find just about any solution by searching long enough, but this issue has perplexed me to the point I actually had to come on here.
Believe me, that's a big deal, I don't give up easily.
I have spent -countless- hours searching, on here, on google, on any "solutions" or "technical" sites I could find, and the closest I can find to a solution are countless people complaining about the EXACT SAME PROBLEM that I have observed and, repeatedly, reproduced again and again, which in every single case boil down to this:
You had 10.6.x (x being 3 or less) with a wireless connection on your home network and all is well.
You upgraded to 10.6.4 and all seemed fine for maybe 24 hours or so... then it happens. You go to load a website, and it's "looking for site" or "waiting for site" in your status bar... hmm, maybe it's just this site you say, so you try another, or a few others in other tabs, but they all have the same problem.
You try to ping the sites, but the network utility can't resolve the domain to even ping them.
Your roommate, all the while, is surfing and gaming just fine on the exact same router you are on, so no, it's not the network hardware, it's not your ISP, hmm, what could it be?
All of a sudden, ALL of the sites you had in like 20 tabs load up at screaming speeds, "WOW" you say, "guess there must have just been some gunk in the wires or something" (notice the irony of the situation: no wires)... anyway, all seems fine again suddenly, surfing is fine for a few minutes, you're back to normal... and it happens again, suddenly NO site will resolve, NO dns will resolve, you can't check email or ping any domain... and so the cycle begins. Of course, you can just plug an ethernet cable straight into the router, but doesn't that kind of defeat the purpose of having wireless networking in the first place?
It continues like this, indefinitely, and it all starts roughly 24 hours after 10.6.4 has been installed.
I have read reports of people on macbooks, people on imacs, people on all sorts of different wireless hardware, but the symptoms are the same.
I know the problem is with the OS update, it's purely software. I know that it has nothing to do with hardware because simply reverting to 10.6.3 solves the problem -every single time- and then "upgrading" to 10.6.4 causes the problem to come back within 24 hours -every single time- (have been reverting using Time Machine to simplify this testing process), so no, where the problem is isn't what perplexes me; what perplexes me is that there are posts that started almost a few days after 10.6.4 came out, and so far there's STILL no fix? Are you freaking serious? Does the Apple programming team not have access to anything other than Apple-Branded Airport Extreme Base Stations to perform wireless network QA testing on?
Get a Linksys guys, grab a D-Link, go get some of the hardware people actually USE and test it on that and see what happens, it doesn't take long to see what's happening.
I blame the programmers because I am one myself and know how easy it is to screw up a rock-solid system with one little typo. Heck, which patch was it, 10.5.7 or 10.5.8 I think? Can't remember exactly, but it was supposed to be such a great "bug fix" patch... and it came with the config file for Apache set to DENY ALL INCOMING EXTERNAL CONNECTIONS by default (in a hidden file that can only be modified by the root user mind you... so much for the average user running a personal web server on THAT version), so yeah, one tiny mistake and it has huge consequences, my question is: what's taking so long to track down what's going on in 10.6.4 and fix it? Can we at least get a patch or something?
I find it really lame and really such a cop-out to see so many irrelevant "solutions" offered, "try specifying different DNS servers" (doesn't matter, whatever causes this bug doesn't care which servers you have specified, it simply sits there and does NOTHING for 2-3 minutes, and THEN when it actually DOES do a dns lookup, it gets the results in the time expected: instantly), to more extreme matters, like resetting hardware, which again has absolutely nothing to do with this bug.
Here is why anyone can see this is an obvious bug that the programming team needs to admit, investigate and correct:
A. happens immediately after the software update
B. happens to EVERYONE who uses traditional wireless routers for internet use
C. is 100% repeatedly reproducible
D. occurs on all different models of computers and all different ISP's and with all different DNS servers specified.
E. has the same symptoms on every system (lightning fast internet for 2-3 minutes, then "waiting for site" for 1-3 minutes)
F. affects EVERY network-using program on the computer (email, network utility, firefox, safari) SIMULTANEOUSLY
G. does not affect surfing to or interacting with IP addresses directly, only with trying to perform DNS lookups from ANY program with ANY dns server (or no dns server) set in network preferences.
Come on guys, just read it through, think about it for a few minutes, for anyone that has worked with and knows the underlying source code, and what changes went in between 10.6.3 and 10.6.4 specifically to networking, should have a light bulb pop up over their head and say "oh YEAH, we never uncommented that one line..." or something to that effect.

I see a very similar issue, but it's been occurring on my laptop for 4 or 5 months, which must be way before 10.6.4. My roommate and friend's laptops all work fine on my network. And my laptop works fine on anyone else's network. But MY laptop on MY network always gives the abysmal DNS performance as described in the original post: 40% of requests time out. Wireless or wired, it doesn't matter. Exact same behavior.
It also doesn't matter whether I use my Netgear router as DNS server, or my ISP, or OpenDNS, or Google. Exact same behavior.
When I do a network trace, it looks like most DNS requests my computer sends out simply never get responded to. (Could they be malformed when they hit the wire? I don't even see an error reply) A few make it through. And when there's a IPv6 (AAAA) record sent, my computer returns a "port unreachable" ICMP message. A screenshot of all of this dialogue is here:
http://img545.imageshack.us/i/screenshot20100913at114.png/
I recently had opportunity to cancel my cable service, and reinstate it for a lower price. They came out, tested the line (strong signal), gave me a new cable box. Yet the issue persists. Exact same behavior.
Firewall is disabled. I've deleted the network interfaces and added them back. Nothing helps.
(As I recall, this issue may even have been present before I reinstalled 10.6 over 10.5, so I'm not too confident a total reinstall would help.)
Any help? I'm about ready to buy a new laptop to fix this damned problem. Web browsing is nearly impossible, as is.

WLC 5508 and WPA/WPA2 causes client DNS lookups to fail

Hi all, we just recently received a brand new 5508 with 6.0.199.4 firmware. We currently have three LAP-1250s that associate just fine to the WLC.
For testing purposes only, we enabled WPA2 with both types of encryption TKIP and AES with an ASCII PSK.   The clients are able to connect, authenticate and get an IP address from our local (same subnet) DHCP server. They also get the DNS info from our DHCP server.   However, the problem is that they are not able to do any DNS lookups.   I haven't run wireshark yet to confirm, but it sounds very familiar to this problem: https://supportforums.cisco.com/message/3202369
I've even had clients use nslookup with both of my DNS servers and they are not able to resolve. I'm not sure if the request or the reply is being blocked/dropped, but I can find out tomorrow.
Now the strange part - if I turn off WLAN security altogether, it works!   That's right, I just disable L2 security for the WLAN and re-connect the clients and they are able to do full DNS lookups.
AND - if I leave L2 security configured (WPA2 with PSK), and enable L3 Passthrough security - the clients get to the auth web page, click the "accept" button and are then able to do full DNS lookups too.
What could be the problem here?   There's nothing I see configured for the L2 or L3 security settings that could be the culprit. We're using default (from Cisco) configuration, so there's no ACLs configured or anything like that to block DNS.
Another strange thing here which may or not be related - during initial configuration the setup asked for a virtual IP - so I gave it one - 1.1.2.2.   Now when I do an ipconfig /all on the client, I see this 1.1.2.2 address listed as the DHCP server. Why is this?   It's definitely getting an IP address and DNS info from the correct DHCP server, so not sure why this is showing up.
Thanks, Matt

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Hi Matt,
Just wanted to jump in, and also mention it may be worth attempting to disable the fastpath feature on the 5508, and test your failing client again. You may be hitting CSCti34667.
debug fastpath cfgtool --fc.disable
This command can be run via Telnet/SSH. Please keep in mind that fastpath will automatically re-enable periodically, so we recommend disabling every 10 minutes as a workaround for any known fastpath issues. You can do so by running the following Macro in TeraTerm:
:mainloop
   sendln "debug fastpath cfgtool --fc.disable"
   pause 600
goto mainloop
If you find that disabling fastpath resolves your concern, you can reach out to TAC for an Escalation Image with the fix for this one.
Best,
Drew

Why am I getting lots of dns lookup error's after upgrading to 6.0?

Half or more of the websites I try to access give me a DNS lookup error page. It didn't happen before the upgrade.

Cannot connect after upgrading Firefox
* https://support.mozilla.com/en-US/kb/Cannot%20connect%20after%20upgrading%20Firefox
Firefox cannot load websites but other programs can
* https://support.mozilla.com/en-US/kb/Firefox%20cannot%20load%20websites%20but%20other%20programs%20can
Clear Cookies & Cache
* https://support.mozilla.com/en-US/kb/Template:clearCookiesCache
Clear the Network Cache
* https://support.mozilla.com/en-US/kb/How%20to%20clear%20the%20cache#w_clear-the-cache
Check and tell if its working.

Firefox freezes when printing

After installing the package "agfa-fonts-2003.03.19-156.21.noarch.rpm" (for SLES 11.2 DVD) during the printing progress, firefox freezes in about 20 minutes and then page is printed .
HW: Intel (R) Core (TM) i5-2450M CPU @ 2.50GHz / 4GB
O.S:. SLED 11 SP2
Firefox 31.0 (x86_64)
Firefox 35.0 (x86_64)
Profile clean
No Add-ons
No plugins
Package content:
/usr/share/doc/packages/agfa-fonts
/usr/share/doc/packages/agfa-fonts/LICENSE.txt
/usr/share/fonts/truetype
/usr/share/fonts/truetype/albw.ttf
/usr/share/fonts/truetype/albwb.ttf
/usr/share/fonts/truetype/albwbi.ttf
/usr/share/fonts/truetype/albwi.ttf
/usr/share/fonts/truetype/andybol_.ttf
/usr/share/fonts/truetype/andyreg_.ttf
/usr/share/fonts/truetype/ans_____.ttf
/usr/share/fonts/truetype/ansb____.ttf
/usr/share/fonts/truetype/ansbi___.ttf
/usr/share/fonts/truetype/ansi____.ttf
/usr/share/fonts/truetype/arblwgl.ttf
/usr/share/fonts/truetype/bl______.ttf
/usr/share/fonts/truetype/blb_____.ttf
/usr/share/fonts/truetype/blbi____.ttf
/usr/share/fonts/truetype/bli_____.ttf
/usr/share/fonts/truetype/cumbwb__.ttf
/usr/share/fonts/truetype/cumbwbi_.ttf
/usr/share/fonts/truetype/cumbwi__.ttf
/usr/share/fonts/truetype/cumbwr__.ttf
/usr/share/fonts/truetype/impact.ttf
/usr/share/fonts/truetype/mtsorts_.ttf
/usr/share/fonts/truetype/thowb___.ttf
/usr/share/fonts/truetype/thowbi__.ttf
/usr/share/fonts/truetype/thowi___.ttf
/usr/share/fonts/truetype/thowr___.ttf
/usr/share/fonts/truetype/uhb.ttf
/usr/share/fonts/truetype/uhr.ttf

It is possible to reset the printer settings: [[Fix printing problems in Firefox]]
Please post back with your results.

Different DNS lookup stratergi for recognized and not recognized root domain

Firefox DNS lookup stratergy is different if the root domain in the URL is recognized (like .se) or not recognized (like .local). How can I add my selfintroduced root domain in the list of recognized root domains?

Firefox DNS lookup stratergy is different if the root domain in the URL is recognized (like .se) or not recognized (like .local). How can I add my selfintroduced root domain in the list of recognized root domains?

Issue with very slow DNS lookup. SBS 2008 R2.

(Preface: sorry if this is the wrong forum...new at this! X-posted from Reddit)
I'm stumped with this one. Last week, the server installed a few updates, no problem, a handful of security stuff. Since then, I've been having issues with DNS lookups on every computer on the network. It will hang on "looking up <domain>.com..."
and then after 20-30 seconds, it will show a "can't find the server" error. BUT THEN! When you click try again, it loads right up. And then it works fine. For a day or so. Then, the next day, or maybe just a few hours later, sometimes while browsing
the same site, it will do the same thing. It's like the DNS server just forgets the lookups it's already done after a time.
Things I've tried:
restarting server (duh)
rolling back updates
reinstalling said updates
restarting all network hardware from the gateway outwards
restarting the service itself while the server is running
The only thing the event log shows is a single error during startup - event ID 4015. The text reads:
"The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is ' '."
This error has only occurred once that I saw and did not occur on the most recent startup, but the issue is still present
Active directory seems to be fine. No errors or warnings in it and no info from the event log is showing anything that seems to be helpful.
I've looked around the KB but every article seems to be troubleshooting a much more specific problem or a different problem altogether, such as a misnamed, stuck, or incorrect DNS zone, or a DNS lookup that fails to complete altogether.

Hi Craigglesofdoom,
Would you please let us know current situation of this issue? Did you refer to above suggestions and solve this problem? If any update, please feel free to let us know.
Please also run SBS BPA tool and check if find relevant issues.
For Event ID 4015, please refer to following article and check if can help you.
Event ID 4015 — DNS Server Active Directory Integration
-->The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly.
Please use dcdiag command-line tool. Any find?
Domain Controller Diagnostics Tool (dcdiag.exe)
Dcdiag for DNS: Test details explained
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

System optimization freezes during Itunes 7.6 upgrading

Hi, the last step (system optimization) freezes during the Itunes/Quicktime/Imovie upgrading.
What can I do ? Thanks for any advise.

+Now I get bluescreen every time I try to open or configure Quicktime or even I if my Quicktime-Plugin for IE or Firefox starts...+
What numerical and text codes are you getting with it? (ie 0x\[zeros/letters/numbers] CAPSANDUNDERSCORES)
If the blue screen mentions a specific file (such as, for example ati3duag.dll), let us know what that is called too. (Exact spelling, please.)
Here's a reference on the sorts of things i'm asking about:
Troubleshooting Windows Stop Messages
If you're just seeing a "flash" of a blue screen, we can use this technique to make hidden blue screens appear for us:
1) Open your system control panel (On Vista, go "Start > Control Panels", click "Classic View", click "System").
2) Click "Advanced System settings".
3) Click the "Startup and Recover" section's "Settings" button
4) Verify that under "System Failure" the "Automatically restart" checkbox is not checked.

MBP - Too Long doing DNS lookups?

I've noticed that my brand-new MBP seems to take an excessively long time to do DNS lookups. I'll load Firefox and type in google.com in the URL bar. In the status bar below it will say "looking up google.com" for at least 10 seconds. Meanwhile, I've opened a terminal window and done an nslookup on google.com and received the IP address. Any idea why I can do a quick lookup in the terminal but the browser takes quite awhile?

Change your DNS servers in the network system preferences.
Use Verizon's Level 3 servers.. they're very fast
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6
Or the OpenDNS servers:
208.67.222.222
208.67.220.220

DNS lookups slow in some (console) applications

pacman, wget, abs (rsync) and many applications have issues getting DNS information. Since 3 months this is bugging me now, but at least I finally seem to have found out that these programs all do ipv6 DNS lookups, although I disabled ipv6 support (and the module).
When I use "curl" in pacman for fetching packages, it is super fast, also when I call "wget -4", to explicitly tell it to use ipv4. Firefox is fast, too, because I set it to disallow ipv6.
How can I tell all the other programs to use ipv4 only?
I want to use yaourt, pacman and co without having to wait for ages to download a package.
And why are only a few (console) applications affected? Do they use a common lib that tries to use ipv6 all the time?

Hello, ppl. Been having the same problem for over 6 months, and i never thought it was a bug, until it stumbled in this post. And i solved it thanks to Nezmer's tip about adding 'options single-request', which didn't work at first, but it got me searching the web. And here it is the result: Since /etc/resolv.conf is rewritten in every boot, simply create /etc/resolv.conf.tail with the following:
options rotate
options single-request
This file's content will be automatically added at the end of /etc/resolv.conf in every boot, et voilá, enjoy pacman, yaourt, etc without pauses...

Firefox freezes during DNS lookup

Similar Messages

Maybe you are looking for