Archive for January, 2011

NetFlix Watch Instantly on IOS via GlimmerBlocker

I recently posted about the possibility of watching NetFlix on an iPad via Proxy…  I like using GlimmerBlocker because it’s really good at blocking Ads, including Mobile Ad networks, but whenever I was using it on my wife’s iPad, it wouldn’t play any NetFlix videos.  I found out that the NetFlix app goes to, which resolves to….  So, when GlimmerBlocker is trying to connect to it, it’s trying to connect to itself, and it’s not running the IOS service listening for such connections, so it fails.  The kind author of GlimmerBlocker was able to help!  He put together a quick beta (1.4.10b7) that is hard coded to look for requests to, and if it is found, it redirects the requests back to the IP address that requested them.

It works perfectly with multiple iDevices…

A workaround for any proxy for use with one IOS device would be to simply set a hosts file entry on your proxy server for to point to the static IP of your iPad.

January 20, 2011 at 8:47 pm Leave a comment

launchd winbindd spam in Mac OS Console

I’m posting this here because I recently noticed this in my console:

1/9/11 12:53:36 PM[1]    (org.samba.winbindd) Throttling respawn: Will start in 10 seconds
1/9/11 12:53:46 PM[1]    (org.samba.winbindd[16381]) Exited with exit code: 1
1/9/11 12:53:46 PM[1]    (org.samba.winbindd) Throttling respawn: Will start in 10 seconds
1/9/11 12:53:56 PM[1]    (org.samba.winbindd[16382]) Exited with exit code: 1
1/9/11 12:53:56 PM[1]    (org.samba.winbindd) Throttling respawn: Will start in 10 seconds
1/9/11 12:54:06 PM[1]    (org.samba.winbindd[16383]) Exited with exit code: 1
1/9/11 12:54:06 PM[1]    (org.samba.winbindd) Throttling respawn: Will start in 10 seconds
1/9/11 12:54:16 PM[1]    (org.samba.winbindd[16385]) Exited with exit code: 1

And it just keeps going.  So, I did a search for this on Google and ran across a few posts showing how to disable winbindd, but nothing stating what the cause of it was…

Well, a quick run of “man winbindd” showed that is has to do with resolving names on NT networks and managing the connection to domain controllers.

Aha!  I remembered previously playing with the idea of running a domain on my home network with a copy of Windows 2008 that I got for free from some student program Microsoft was running.  To test things out, I loaded it in a VM.  Ultimately, I couldn’t get roaming profiles to work, so I abandoned the idea.  But, I didn’t remember if I cleared my domain out on my Mac or not.  So, off to Accounts, Login Options, and there at the bottom of the screen I saw a “Network Account Server” was configured (with a red dot next to it, indicating no contact).  So, I removed it, and the winbindd spam stopped in my console.

Anyhow, since I had trouble finding a good answer on Google and the threads I found on Apple’s support forum were closed, I thought I’d post my resolution here in hopes of helping someone else.  Your welcome.  🙂

January 9, 2011 at 1:04 pm Leave a comment

NetFlix Watch Instantly on IOS devices via Proxy

It looks like NetFlix Watch Instantly on IOS devices uses a trick to try to avoid proxy servers.  More on that in a bit.

I found this out using a great Mac application called GlimmerBlocker.  It’s a proxy server that blocks ads, enhance web sites, and more.  Kind of like GreaseMonkey for Firefox, except this is in Proxy server form.  It allows you the opportunity to transform the content of everything going through it.  Various programmers create filters, and publish them for anyone else to use.  The site lists ones as specific as a “Facebook ‘Like’ Disabler” and the “Facebook 3rd party block”, to ones such as “SSL:ify Sites”, which forces all communications to Facebook, LinkedIn, Dropbox, and Google to their SSL versions.  If you have kids, you might want “SafeSearch”, which enforces safe-search on Google, Yahoo, and Bing.  You can even chain GlimmerBlocker to a Caching proxy to save bandwidth.

Unfortunately, my iPhones and iPad can’t use NetFlix’s Watch Instantly feature through GlimmerBlocker, or any other proxy for that matter.  Today, using the debug logging built into GB, I was able to figure out why.  Somewhere just before the video starts to play, the NetFlix IOS application tries to perform a CONNECT to the address on port 4343.  Oddly enough, this IP address resolves to, which fails since the proxy server is trying to talk to itself.  It appears the the IOS application is listening on port 4343 for this in some sort of strange attempt to keep you from running this through a proxy server.  I don’t know if they are sending this through to the client unencrypted and don’t want the video cached, or what they are trying to do here, but there is a way around it, though not very elegant…

On the proxy server itself, set a hosts file entry for to be the local IP address of the IOS device.  You might have to set a static IP on your iPad, or use a static DHCP reservation, but it works. The problem here is if you have more than one IOS device.

A far more elegant way to handle it would be via a GlimmerBlocker filter that looks for as the destination host, then changes the request to the IP address of the requesting client machine.  This way, you could have multiple IOS devices going through the proxy server simultaneously, and it would translate all the “” requests back to the original IOS device that made the request.  I’ve tried my hand at creating a GB filter to do this, but so far I’ve been unable to.  I’m not experienced at this, so perhaps it is possible without changes to GB, but it appears that there isn’t a variable containing the requesting client’s IP Address.

If you have any ideas on how to make this work with multiple IOS devices via proxy at the same time, feel free to chime in.

January 7, 2011 at 9:24 pm Leave a comment


January 2011

Posts by Month

Posts by Category