Launcher Still broken 4.3.2.15211

Mac Technical Support
I am getting frustrated in the lack of support I'm getting on this issue.

I use Bootcamp to dual boot my iMac. The launcher never connects to the news server running under MacOS but when I reboot the system using Windows 7 it almost always connects. This is the same hardware at the same NAT address through the same hardware firewall. This is a BUG in the MacOS WoW launcher.

Technical Details:

Firewall/Router:
Firewall WNDR3400 latest firmware
Ports open and linked to system as per firewall configuration recommendations
http://us.battle.net/support/en/article/firewall-configuration-for-blizzard-games#q-1

System set to a reserved NAT DHCP address via MAC, 192.168.202.101 in this case.

System:

Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.20f4

MacOS 10.7.2
More then likely this is something you have on mac os x that window doesnt, such as little snitch or peerguardian with battle.net blocked. Or a bad realmlist.wtf file with a bad patch url.

Have you removed any blocking software, you may not even realize it's installed.
I am getting frustrated in the lack of support I'm getting on this issue.

I use Bootcamp to dual boot my iMac. The launcher never connects to the news server running under MacOS but when I reboot the system using Windows 7 it connects almost always. This is the same hardware at the same NAT address through the same hardware firewall. This is a BUG in the MacOS WoW launcher.

Technical Details:

Firewall/Router:
Firewall WNDR3400 latest firmware
Ports open and linked to system as per firewall configuration recommendations
http://us.battle.net/support/en/article/firewall-configuration-for-blizzard-games#q-1

System set to a reserved NAT DHCP address via MAC, 192.168.202.101 in this case.

System:

Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.20f4



Also getting frustrated with the support, i have called, written, etc..

My launcher still doesnt connect to the news server
Yeah, I can never get past that awful Blizzard Launcher... Hey Blizzard, no one likes your launcher. As usual I gotta go to a fifth hand iffy site to download the patch. Remember the good ole days not long ago, when you just manually downloaded updates, and it took like 3mins... hint hint.
More then likely this is something you have on mac os x that window doesnt, such as little snitch or peerguardian with battle.net blocked. Or a bad realmlist.wtf file with a bad patch url.

Have you removed any blocking software, you may not even realize it's installed.


I do have little snitch installed but is completely off. Installing it was suggested by the Blizzard support team when I first complained about this, as a debugging tool. I had this problem before that. I have no other software installed that has the capability to do this kind of blocking. I will remove it and try anyway but I expect no change.

Update: No Little Snitch, still "Cannot connect to the News Server. Please check the network and try again later."
I have the same problem, ticket open: no answer.
I found an interesting file /Applications/World of Warcraft/Logs/Launcher.log which has an error in it. See bottom of this post. I can browse to the URL that fails.

I'm speculating but I think another system on my network is confusing it. It may even be my router. I got a message when I mapped 6881-6999 that I had to restart because the router was using ports in the range. After analyzing the log output better I'm betting it is the UPnP negotiation that is going bad.

Or it could be my bridge which is a Linksys dd-wrt. nmap reports it listening on 6881.
Testing with it powered down proved it isn't

Other folks with this problem who is the manufacturer of your firewall or router? And are you running alternate firmware?

At the end of the file is:
19:42:38.2652 Portmap: successfully mapped port using UPnP. external port: 6881
19:42:38.4340 Finished checking files.
19:42:38.4758 Play-on-demand initial values:
Total Bytes: 16010706944
Base Bytes: 14695530496
19:42:38.4758 Stage 0: 174850048 of 174850048 bytes
19:42:38.4758 Stage 1: 8933081088 of 8933081088 bytes
19:42:38.4758 Stage 2: 6902775808 of 6902775808 bytes
19:42:38.4837 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
19:42:38.4838 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
19:42:38.4839 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
19:42:38.4840 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
19:42:52.6101 Cannot load the page 'http://launcher.worldofwarcraft.com/2.0/CT/index.xml?version=4.3.2.15211&locale=en-US&type=CT' (The operation couldn’t be completed. (NSURLErrorDomain error -999.)) (2)
yea, I have not had much luck with the launcher either. I launch the game using the wow.exe file in the main directory, it bypasses the launcher. It does launch the launcher when a patch is ready though, but it doesn't lock up when it does. Not sure why that is, bit it doesn't matter as long as I can launch the game. use the wow.exe file to launch the game and see if that solves your launcher lock up problem.
yea, I have not had much luck with the launcher either. I launch the game using the wow.exe file in the main directory, it bypasses the launcher. It does launch the launcher when a patch is ready though, but it doesn't lock up when it does. Not sure why that is, bit it doesn't matter as long as I can launch the game. use the wow.exe file to launch the game and see if that solves your launcher lock up problem.
Having LittleSnitch off isn't the same as it removed. It still may be running some sort in the background. Try going into safe mode to see if this helps connect to the news server. Your WoW will crash once you hit play, but that cause of no drivers loaded in safe mode. This is just to test 3rd party items from interfering with the launcher.

Starting up into Safe Mode (to Safe Boot)
    1. Be sure your Mac is shut down.
    2. Press the power button.
    3. Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    4. Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).

You can restart you Mac after you've done this test and posted the results.
________________________________________________
Mac Tech Support for Baaaaahlizzard Entertainment
Not finding what you need here? Contact a rep direct! http://us.battle.net/support/en/article/contact

Pfft! Secret doors, who needs 'em? What do I care about secret doors?... and the unparalleled delights they keep hidden from the world!
Also that error log is still showing launcher using bittorrent. If you cannot connect to torrents DISABLE the p2p option in launchers "download" options. Some ISPS or networks just can't torrent and disabling it solves your problem. I get a stable 150kbps (my ISPSs max speed in my small town) with option off, with it on i'm lucky to get 20-30kbps, because it saturates my really tiny upload pipe to a point where my download bandwidth also tanks. If you don't have a very strong upload pipe, or a lot of bandwidth in general, DO NOT use the P2P option in downloader. This should help a lot with bad speeds or connection timeouts/problems.

Now if you cannot connect to blizzards http server still after the fact, then it probably is still a blocked port or server by some kind of software.
I removed it. The folder containing Little Snitch isn't even in the trash.

I have 30 years as a Unix System Admin. I "rm -rf " the directory and the process is no longer in the process table.

Please have someone with a some knowledge in this area read the Launcher.log segment I have included.
Just to be very clear I can use a browser to reach the URL that fails at the end of this log. This is the complete log of one attempt:



#-----------------------------------------------------------
# System started at 2012-02-03 01:48:20.5958
# system: lilmac
#-----------------------------------------------------------
01:48:20.5969 Launcher version 4.2.1.2683
01:48:20.6144 World of Warcraft version 4.3.2.15211
01:48:22.2442 Starting PatchOnDemand system...
01:48:22.2442 Retrieving torrent information from the server.
01:48:22.3139 Download Tags: EXP3,EXP2,EXP1,OSX,enUS
01:48:22.4077 Storage subsystem initialized to /Applications/World of Warcraft/.
01:48:22.4597 Portmap log: UPnP: broadcasting search for rootdevice
01:48:22.4598 Portmap log: UPnP: adding port map: [ protocol: tcp ext_port: 6881 local_port: 6881 ]
01:48:22.4598 Portmap log: UPnP: adding port map: [ protocol: udp ext_port: 6881 local_port: 6881 ]
01:48:22.4598 Portmap log: NAT-PMP: found router at: 192.168.202.254
01:48:22.4598 Portmap log: NAT-PMP: ==> get public IP address
01:48:22.4598 Portmap log: UPnP: found rootdevice: http://192.168.202.254:5000/Public_UPNP_gatedesc.xml (0)
01:48:22.4598 Portmap log: UPnP: connecting to: http://192.168.202.254:5000/Public_UPNP_gatedesc.xml
01:48:22.4598 Portmap log: UPnP: found rootdevice: http://192.168.202.254:1780/WFADevice.xml (1)
01:48:22.4598 Portmap log: UPnP: connecting to: http://192.168.202.254:1780/WFADevice.xml
01:48:22.4598 Portmap log: UPnP: could not find a port mapping interface in response from: http://192.168.202.254:1780/WFADevice.xml
01:48:22.5087 Torrent Resumed.
01:48:22.7151 Portmap log: UPnP: upnp model name: WNDR3400
01:48:22.7151 Portmap log: UPnP: found control URL: http://192.168.202.254:5000/Public_UPNP_C3 namespace urn:schemas-upnp-org:service:WANIPConnection:1 urlbase: http://192.168.202.254:5000 in response from http://192.168.202.254:500
01:48:22.7152 Portmap log: UPnP: sending: POST /Public_UPNP_C3 HTTP/1.0
Host: 192.168.202.254:5000
Content-Type: text/xml; charset="utf-8"
Content-Length: 282
Soapaction: "urn:schemas-upnp-org:service:WANIPConnection:1#GetExternalIPAddress"

<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetExternalIPAddress xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"></u:GetExternalIPAddress></s:Body></s:Envelope>
01:48:22.7152 Portmap log: UPnP: get external IP address response: <?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:GetExternalIPAddressResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1">
<NewExternalIPAddress>70.92.189.19</NewExternalIPAddress>
</u:GetExternalIPAddressResponse>
</s:Body>
</s:Envelope>

01:48:22.7152 Portmap log: UPnP: got router external IP address 70.92.189.19
01:48:22.7152 Portmap log: UPnP: connecting to 192.168.202.254
01:48:22.7152 Portmap log: UPnP: sending: POST /Public_UPNP_C3 HTTP/1.0
Host: 192.168.202.254:5000
Content-Type: text/xml; charset="utf-8"
Content-Length: 633
Soapaction: "urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping"

<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:AddPortMapping xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"><NewRemoteHost></NewRemoteHost><NewExternalPort>6881</NewExternalPort><NewProtocol>TCP</NewProtocol><NewInternalPort>6881</NewInternalPort><NewInternalClie
01:48:22.7153 Portmap log: UPnP: found rootdevice: http://192.168.202.106:8089/ (2)
01:48:22.7153 Portmap log: UPnP: connecting to: http://192.168.202.106:8089/
01:48:22.7153 Portmap log: UPnP: map response: <?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"/>
</s:Body>
</s:Envelope>

01:48:22.7153 Portmap: successfully mapped port using UPnP. external port: 6881
01:48:22.7153 Portmap log: UPnP: connecting to 192.168.202.254
01:48:22.7154 Portmap log: UPnP: sending: POST /Public_UPNP_C3 HTTP/1.0
Host: 192.168.202.254:5000
Content-Type: text/xml; charset="utf-8"
Content-Length: 633
Soapaction: "urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping"

<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:AddPortMapping xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"><NewRemoteHost></NewRemoteHost><NewExternalPort>6881</NewExternalPort><NewProtocol>UDP</NewProtocol><NewInternalPort>6881</NewInternalPort><NewInternalClie
01:48:22.7154 Portmap log: UPnP: map response: <?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"/>
</s:Body>
</s:Envelope>

01:48:22.7154 Portmap: successfully mapped port using UPnP. external port: 6881
01:48:22.7154 Portmap log: UPnP: could not find a port mapping interface in response from: http://192.168.202.106:8089/
01:48:23.9458 Finished checking files.
01:48:23.9656 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
01:48:23.9658 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
01:48:23.9659 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
01:48:23.9660 Found peer on local subnet: cce9238c7d3e2043089456c17724c9622f90eadf peer (192.168.202.101, Unknown): received peer from local service discovery
01:48:24.2286 Play-on-demand initial values:
Total Bytes: 16010706944
Base Bytes: 14695530496
01:48:24.2286 Stage 0: 174850048 of 174850048 bytes
01:48:24.2286 Stage 1: 8933081088 of 8933081088 bytes
01:48:24.2286 Stage 2: 6902775808 of 6902775808 bytes
01:48:37.2928 Cannot load the page 'http://launcher.worldofwarcraft.com/2.0/CT/index.xml?version=4.3.2.15211&locale=en-US&type=CT' (The operation couldn’t be completed. (NSURLErrorDomain error -999.)) (2)
Also that error log is still showing launcher using bittorrent. If you cannot connect to torrents DISABLE the p2p option in launchers "download" options. Some ISPS or networks just can't torrent and disabling it solves your problem.

<<SNIP>>
.


Remember the same machine with the same ISP works fine when running Windows 7.
It is still broken. Still no useful reply. I have sent email to macsupport@blizzard.com with no response either. Which is what was suggested when I called the support line.
The macsupport@blizzard.com is no longer a valid email address. If you wish to have me to look at the files personally, you can do so by following the steps below. Please send me the information after you've tried to connect again. This will help show me useful information that may be present in your system.log.

Obtaining your System Information and system.log
Snow Leopard (10.6) and older versions of OS X
    1. Hold the Option Key and choose System Profiler from the Apple Menu
    2. When the System Profiler is finished gathering its data, click "File" then "Save As..."
    3. Add your name to the filename, and save it to your desktop for easy location. Make sure the file format is "System Profiler 4.0 (XML)"

Lion (10.7)
    1. Hold the Option Key and choose System Information from the Apple Menu
    2. When the System Information is finished gathering its data, click "File" then "Save As..."
    3. Add your name to the filename, and save it to your desktop for easy location.

Obtaining your system.log
    1. Using Finder, Navigate to /Applications/Utilities and open Console
    2. Click system.log on the left side bar.
    3. On the menu bar, click File, and select Save a Copy As. Make sure the file is saved to the desktop for easy location.

Submitting your system files
    1. Open a new email message, and attach the items as an attachment.
    2. Send the email to forumtech@blizzard.com with the subject as "Attn: TonyM". Make sure you include the Thread title and URL address. This way it gets routed to me so I can take a personal look.

Thanks!
________________________________________________
Mac Tech Support for Baaaaahlizzard Entertainment
Not finding what you need here? Contact a rep direct! http://us.battle.net/support/en/article/contact

Pfft! Secret doors, who needs 'em? What do I care about secret doors?... and the unparalleled delights they keep hidden from the world!
TonyM,
Expect the following in your mail:

I'm sending you the files you requested but my guess is that the launcher and my firewall router are having issues. I believe that from the trace in the Launcher.log. For some reason the Launcher thinks there is a peer on my internal network even when the only devices on the network are my iMac and my router. Everything else has either been powered down or in the case of my TiVo the USB wireless has been unplugged. The log is from a single session, with the usual network devices online, where I run the launcher, wait for the failure message, and the click the play button to start the game itself.


DarrylB
Thanks for the files.

So, from a little research, it may not be a bug in the OS (yet). You may be on to something, as from the research on the logs, the error may occur if an another request is made before the previous request is completed.

So something on the OS I think is acting as a nanny of sorts. Going back to my previous post, did you try booting into safe mode to ensure no 3rd party process are running when you launch the launcher? I believe this should even disable helper process for some software. I see a few bits of software that may causing it to be a nanny of sorts.

Safe mode should allow you to bring up the the WoW Launcher and test to see if it can connect itself to the page without something acting as a nanny of sorts. Now more than likely after pressing Play, the World of Warcraft.app will crash, but thats expected due to no real drivers running in Safe mode.
________________________________________________
Mac Tech Support for Baaaaahlizzard Entertainment
Not finding what you need here? Contact a rep direct! http://us.battle.net/support/en/article/contact

Pfft! Secret doors, who needs 'em? What do I care about secret doors?... and the unparalleled delights they keep hidden from the world!
I amazed how slow the machine is in safe mode but it didn't help. I forgot to post those results. I sent you the Launcher.log file from a run in safe mode but it looks the same. I still think it is my router that is making the Launcher think it has a peer on the network. As to why it thinks the IP of the peer is the Mac itself I'm clueless.
Out of curiousity but have you tried flat out disabling upnp in case it is failing because of that?

Join the Conversation

Return to Forum