WWW call on MacBook pro times out

So i've been trying to work this one out, and i'm totally lost. We're working on a project with a few people, and one particular person is having this problem. What happens is that the WWW call in the following code times out. The call takes ages to resolve and then fails with Connection Timed out. The server in question is on our local network. Only on that MacBook. We can ping the given URL, we can go to it in the browser, but on the same machine, in the Unity editor and only the editor, we can't access the URL. I don't doubt that this is an issue specific to that particular Macbook, but was hoping someone had experienced this or had an idea about what might be causing this.

using UnityEngine;
using System.Collections;

public class ServerTest : MonoBehaviour {

    // Use this for initialization
    void Start () 


    bool check = false;

    // Update is called once per frame
    void Update () 
        if( !check )
            check = true;


    IEnumerator getWebCall()
        Debug.Log("About to start");

        yield return www;

        if( www.error != null )
            Debug.Log("WWW fail: " + www.error);

        Debug.Log("Returned: " + www.text.ToString());

EDIT: With some further investigation, even switching the player prefs to Mac/Standalone still gives the error. Oddly enough it gives this error for ANY url ( even Google.com and Microsoft.com ). We decided to attempt to hack around the issue just for this Mac, by adding our URL to the hosts file on the system, but all that did was get a response from that URL and no response from the other urls we need. Our developers and system admin are all stumped. It just looks like something on that mac is blocking only the Unity Editor ( since the webplayer works fine on his mac, but is not a workable solution since he needs to create and test assets for the game ).

Are you building as a webplayer or a standalone, with the webplayer selected as build type you can run into security sandbox issues with www requests due to the same domain restriction on them. Check that out as that was giving me a problem as well.