Slow DNS Lookups after connecting via PPP VPN

I have this very annoying problem and just can't seem to find a method to resolve it.
When I connect to my work network via a PPP VPN connection, all internet connectivity thereafter takes forever to do a DNS lookup. So when I browse the internet it takes ages before the page is displayed back.
If I also do a ping in finder for a random URL, www.google.com for example, it sits there for nearly a minute before I get a response. If I then immediately perform the ping again, I get a response straight away. So it seems once it's resolved the domain name, it gets stored in a cache somewhere. If I try another domain name, I get the same delay and then it eventually gets through.
As soon as I close the VPN connection, service is resumed and DNS lookups work fast.
I've also made sure I've unchecked the option to "Send all traffic over VPN connection".
I've also set my 'Service Order' to have my wireless Airport connection in the No #1 position.
The other thing I've tried is deleting the default route (via Terminal) and adding one manually that points to my wireless router, again without success.
Does anyone have any other ideas I could try? I've also recently re-installed a fresh copy of Leopard in case something was stuffed up, but the problem is still there after installation.
Hoping someone has an easy solution!
Many thanks

I seem to have found a work-around. There is probably a neater way of doing this but here goes.
Here is my setup:
Airport Wireless to my home router
PPP VPN connection to my office windows network
3G connection via mobile phone
My aim was to be able to connect to my office network via wireless at home or via my cellular data connection, but continue to route all non-work traffic via the main connection (wireless/3G).
The #1 problem I had once I connected to my office VPN on either wireless or 3G, was that DNS lookups to general internet sites took forever. So to get around this, I created TWO VPN connections to my office network in Network Preferences and in both connections I made sure the option to send all traffic over VPN was left UNCHECKED.
The first connection I then designated for use when connecting wirelessly at home. Here I manually added the IP address of my home router as a DNS entry.
The second connection I did the same by adding a new DNS entry, except here I used the DNS server of my cellular data connection, in this case T-Mobile UK.
When connecting to my office network I just use either of the above connections depending on whether I am connecting wirelessly at home or via my mobile phone.
It seems a bit long winded I grant you, but after literally months of trying to resolve this annoying problem, this appears to be the only fix that works.
The downfall of this would be that DNS resolution to any servers on your office network might not work, but that isn't a problem for me since I manually add any servers I use at work to my local hosts file. This negates any need for DNS lookups and actually speeds up access to my work servers.
In amongst this I did several reboots, so you give your machine a reboot once you've completed the above steps, just in case.
The 3G connection won't work for you if your provider changes the DNS server every time you connect, but this is unlikely.
If anyone's got any comments, I'd love to hear them.
Cheers
Phil

Similar Messages

  • Mapped drives do not open after connecting via Cisco VPN Client

    I have an issue when I initially connect to my remote network, I cannot get to any mapped drive unless I wait a few minutes for the VPN connect to mature. To explain further, I have to wait 2-4 minutes after connecting to the VPN for me to actually connect to those drives.
    The error that pops up is:
    "An error occurred while reconnecting to DriveLetter: to \\Server\sharedDrive\    Microsoft WIndows Network: The network path was not found. This connection has not been restored.
    Now, immediately after  I connect, I am able to successfully ping the server that hosts those folder locations but for some reason I cannot get to the server via UNC/shared drives until I wait a few minutes after connecting. 
    Below is the list of error logs I get when attempting to connect to the mapped drives during those first few minutes of connectivity:
    1      15:26:39.804  10/06/14  Sev=Warning/3 IKE/0xA300005F
    Firewall, Sygate Security Agent, is not running, the client will not send firewall information to concentrator.
    2      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    3      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    4      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    5      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    6      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    7      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    8      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    9      15:28:10.614  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    10     15:28:17.188  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    11     15:28:17.188  10/06/14  Sev=Warning/2 IPSEC/0xE3700003
    Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)
    12     15:33:50.642  10/06/14  Sev=Warning/2 CVPND/0xA3400015
    Error with call to IpHlpApi.DLL: CheckUpVASettings: Found IPADDR entry addr=192.168.11.120, error 0
    13     15:33:51.656  10/06/14  Sev=Warning/2 CVPND/0xA3400015
    Error with call to IpHlpApi.DLL: CleanUpVASettings: Was able to delete all VA settings after all, error 0
    14     15:35:16.855  10/06/14  Sev=Warning/3 IKE/0xA300005F
    Firewall, Sygate Security Agent, is not running, the client will not send firewall information to concentrator.
    Any ideas on what it could be?

    I have a client that is showing a similar issue.. Windows 7 computer using Cisco IPSec client terminating on a Cisco 881 Router.  I can ping the server by IP, Name and even access the drive from the start menu option, but not the mapped drive.  Currently I am looking into this from a offline file issue in windows, but ran across this post and was wondering if you had figured this out?  I am going to try the following and will post back if that resolves it.
    Doing some research I found that Windows 7 and Vista both have what’s called “slow link mode”.  The behavior is that if the latency of the network connection exceeds 80 milliseconds (ms), the system will transition the files to “offline mode”.  The 80 ms value is configurable using a local group policy edit.
    Open Group policy (start -> run -> gpedit.msc)
    Expand “Computer Configuration”
    Expand “Administrative Templates”
    Expand “Network”
    Click on “Offline Files”
    Locate “Configure slow-link mode”
    This policy can either be disabled or set to a higher value for slower connections.
    https://www.conetrix.com/Blog/post/Fixing-Problem-With-Windows-7-Shared-Files-and-Mapped-Drives-Unavailable-Over-VPN.aspx

  • Blank page after connecting via SAP HTML GUI through web vpn

    Hello,
    SAP HTML GUI connection works fine while internally.  Trying to connect via web vpn provides logon screen fine.  After entering credentials, an SAP stlogo appears and immediately changes to blank page.
    Any help is appreciated.

    In the default php.ini is set open_basedir which limits work with php only to few directories (and directories bellow them). There is set /srv/http, /home,/tmp and /usr/share/pear by default.
    To allow your vhost you should add /data/www or set empty value.

  • For anyone who is experiencing slow DNS lookups...

    I finally worked out what was wrong with my network config last night and thought I'd share it with everyone in a simgle post in the hope it'll help someone else.
    I tried the BIND work around, but it wasn't all that much faster.
    I tried disabling IPv6, but that didn't do much...
    The solution?
    In 'System Preferences' -> 'Network'
    Go to configure the adaptor (Airport / Ethernet / etc)
    In 'DNS Servers' where you'd normally specify the DNS servers given to you by your ISP... don't do this! As crazy as it sounds don't
    Of course, if you're using newer routers you'd not be having this slow DNS lookup problem and specifying the ISPs DNS Servers would be appropriate... still
    What you want to specify here is your ROUTER's IP:
    eg. 192.168.0.1
    With this simple modifcation you'll be fine. Why? You ask?
    In Linux / OSX (I imagine in Unix as well) the way the lookups are carried out are different from Windows. I have other Windows computers on our network and they never had DNS lookup problems and they've been given the ISPs DNS IPs... anyway I think I'm talking out of my depth now heh.
    This works!
    Remember: Specify your router as the DNS Server!

    I've had this problem on a G4 PowerMac running Panther, and it still had it after a Tiger upgrade. I just replaced it with a Core Duo MacMini, 10.4.7, same problem of slow DNS lookups (i.e., slow initial start to loading a web page, then it goes quickly). Windows machines on the same subnet have no such problem. I've tried the various suggestions on various forums, none of which worked. I tried:
    - turn off IPv6 (no help)
    - directly enter my ISPs DNS servers (no help)
    - manually configure both IP and DNS (no help, went back to DHCP)
    - swear at the computer (a little help, mentally)
    After some more reading, I tried resolving some addresses using the host command from the Terminal:
    host -v www.apple.com 24.34.240.9
    where the IP address is one of the DNS servers for my ISP (Comcast). I got a no server found message! I then tried the second DNS server in the Comcast list (found from my router), also no server found. Tried the third one in Comcast's list of DNS servers, and it worked. Entered it in System Preferences -> Network as a DNS server, and now web browsing is zippy! I verified that the two DNS servers that MacOS couldn't see are also down as far as Windows was concerned (using the nslookup command in windows).
    What this tells me is that the OS X algorithm for handling unreachable or slow DNS servers is different from that in Windows. Maybe Windows remembers a bad experience with a DNS server and uses ones that it has success with, while OS X just keeps trying them in order, slowing timing them out until it finds one that works?
    This could also explain many of the puzzling symptoms people have been seeing (things work some times, other times not; some people have luck specifying the DNS server manually, others don't). It all depends on what DNS servers got distributed to the Mac via DHCP, and how far down the list you have to go to find one that is responsive.
    Anyone reading this forum with technical knowledge of both UNIX and Windows DNS lookup implementations? Is there some way to tweak in MacOS to make it perform more like Windows in this situation (like, maybe shortening the DNS server failure timeout)?

  • Iphone 4s not getting detected in macbook after connecting via usb cable, also photos taken in iPhone not showing in macbook pro

    iphone 4s not getting detected in macbook after connecting via usb cable, also photos taken in iPhone not showing in macbook pro    

    Thanks. I realises that i will hv to go to iphoto to see the photo. Its now working !!!!!

  • No sound in hdtv after connecting via thunderbolt to hdmi cable from macbook pro

    no sound in hdtv after connecting via thunderbolt to hdmi cable from macbook pro

    What model MacBook Pro?
    The mini display port on earlier Apple computers only support video. See:
    About Mini DisplayPort to HDMI adapters
    Also, if you go to System Preferences>Sounds>Output do y see HDMI or Min displayport as an Audio out option?

  • Why is atv slow to buffer after connecting with cat5 cable

    Why is atv slow to buffer after connecting with cat5 cable

    Update on some things I have tried
    As I am not sure the cause, I have been reading and trying different things, last thing was to set the interfaces to Duplex Full
    I did this on both the Ethernet ports on the routers, and both of the Fast Ethernet ports being used on the switch, but has not changed the speed that PC1 is getting.
    Also turned on CEF on both routers

  • [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)

  • 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:

  • 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.

  • Very slow printing from Konica connected via Airport Express

    Hello folks,
    I have a very strange problem with erratic printing to a network printer, connected to an Airport Express via ethernet.
    The Network:
    - Draytek modem/router hosting DHCP
    - Time Capsule connected to Draytek. It's in bridge mode, and runs the WiFi network
    - Airport Express 1 in "Join a Network" mode, ethernet clients allowed
    - Konica Minolta Magicolor laserjet printer connected via ethernet to AX1
    - Airport Express 2 in "Extend a Network" mode elsewhere in the office
    All client devices on the network are getting IP addresses in the correct range etc. I have fixed the IP of most devices at the router level, so they don't change.
    Client Macs print directly to the printer using IPP (or might be LPD, I can check if relevant) using apparently a correct driver and IP address.
    WiFi network is very strong throughout, and the distance between Time Capsule and AX1 is just a few feet.
    Here's the problem:
    At the start of the day, the printer works just fine. Fast.
    Then, inexplicably, you send a document to it and the print queue reports "Spooling....xx%" which increases painfully slowly compared to when it's working normally.
    This happens randomly with both small and large files. A modest photo can take over an hour to fully spool and print when it's doing this.
    Turning the printer off and on again tends to make it work properly, until the above happens again.
    This is driving me mad. Is there a problem with:
    (a) The WiFi network or airport hardware
    (b) The printer
    (c) The drivers
    (d) The printing protocol
    (e) Me
    (f) All of the above
    Any insight would be most welcome. The Konica tech reckons it's working, but I think he didn't spend long enough sending print jobs to it for the problem to manifest.
    P.S.
    One of my main questions is, when the print queue says "spooling", is this the process of progressively sending the file over the network? Or does spooling occur when the data is either already fully arrived at the printer, or hasn't left the Mac yet?
    Could the printer's unwillingness to accept data cause the slow spooling? Why might this happen?

    It should work. Enable Printer Sharing via System Preferences -> Sharing. The Mac does need to be turned on.
    P.S. Try to just post one thread on your question instead of crossposting over several forums.

  • 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]

  • Slow DNS lookup

    For the past two days, my internet has really slowed down.  The problem appears to be a "pokey" DNS server.  In many cases, it would take longer for the DNS server to work, than to download the web pages.  This morning, the problem seems fixed -- DNS lookup is pretty much "instantaneous" again.  I still have my DNS settings to let Comcast determine the server.  Is it OK if I change the settings to a specific DNS Server?  If so, does anyone have any recommendations about which one to use?  TIA ---

    Try using the Google or the OpenDNS offerings. Search google for info.

  • Lost the monitor after connecting via DVI

    I've had an X2Gen 22" monitor connected to our G5 via DVI/VGA adapter to the VGA input on the monitor for a couple of years. Another monitor I just bought came with a DVI cord and a VGA cord. I decided to try the X2Gen/G5 connection via DVI since I now have a cable. The computer can't/won't recognize the monitor now that they're DVI connected. And screen images are ugly! I can't even calibrate it because the computer tells me it cannot identify the monitor. Any ideas anyone? (Other than going back to the VGA cable?)
    Thanks,
    Jon

    Just a thought, but try zapping the PRAM. Good luck.

  • Apple USB Modem rarely connects via PPP

    Greetings from Antarctica. My employer offers me dialup internet from my dorm room here in Antarctica. Using my Apple USB external modem, V.92 (error correction and compression in modem enabled) and all the correct username/password items, I am able to connect to the local dialup network maybe one time in ten.
    The modem gets a dial tone, dials, goes through the concert of tones, the tones disappear just like when a connection is made, but only about once in every ten tries will it actually establish a connection. The other times it will sit there saying "Connecting" until eventually it times out and disconnects the phone line. I have tried using v.90 and v.92, with and without error correction and compression in modem. No difference.
    The PPP configuration is to send PPP echo packets, verbose logging is off, Terminal script is none, the box is checked to use TCP header compression.
    I am using a Santa Rosa MacBook with 10.5.5, 2 GB RAM. If there is a log file somewhere that would help someone troubleshoot this with me, please give me specifics on where I might find it. If you want me to try and connect with the Terminal window instead, then I will need very specific instructions.
    Thanks from McMurdo Station, Antarctica.

    I'm not positive here as it could be a hardware failure of my usb modem, but leopard seems to have broken this device for my G5 iMac. Even in Tiger this modem was never as good as the built in ones on the G4 models and would be buggy sometimes and not as fast as the internal G4s. I had wondered if it would work on intel versions with Leopard better, but your experience isn't a good sign.
    My solution was to use a G4 mini using it's internal modem and internet sharing via airport which worked well and gave me more freedom on my other laptops as well, though it be at the slow speed of dialup. I would imagine a G5 PowerMac would also work with this modem especially if running Tiger. If this was an early Macbook, it might also have shipped with Tiger, but no idea how this would play out with the Intels vs PPC.
    Not sure how you get phone service in Antarctica but I'm guessing there is some sort of satellite device involved. Is anyone else having trouble connecting with modems through the setup? I know PPP is not well supported in certain compression modes such as Voip, but I would imagine if you had voip broadband would be available.
    Bottom line seems to be the G4s are gold if you need dialup service. Best of luck!

Maybe you are looking for

  • TS1881 My Iphone4 will not sync with my Itunes

    I have not been able to update or sync my Iphone for several month now due to error messages on my Itunes account when trying to update.  I get an error that says itunes64.msi not found.  And now its saying that sevice for this device is not started.

  • "Convert selection to iPod/iPhone" failing to convert

    When I attempt to sync an .mp4 video I downloaded from the net, it tells me I can't because my iPod touch can't play it. Okay, whatever, so I go to the Movies section of my iTunes library, right click said video, and select "Convert selection to iPod

  • E51 WLAN

    my phone connects at most hotspots but not on my home network. the router is mixed (b/g), 2.437GHz, SSID broadcast enabled. if WEP is enabled i can't connect to the network although i have the pass key entered in the phone. if i disable WEP it connec

  • Missing Camera Roll - iCloud "Some items could not be restored"

    After having some problems with my previous ipad 3, I had it replaced and tried restoring everything from iCloud. Everything went seemingly well until a pop-up appeared saying "Some items could not be restored." Everything seems to be accounted for e

  • 4.6.21: Logging region overflow with DB_RDONLY

    At Debian, we've shipped Berkeley DB 4.6.21 as part of our last release. Unfortunately, we missed what appears to be a rather annoying bug related to the use of DB_RDONLY: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510270 This appears to have b