Unable to get fiddler working on phone

[Mukund]

Hi,
I have installed fiddler on my work desktop PC that is connected to a domain.

Now,
From my desktop
 I am able to see the fiddler echo service page
 I can all the traffic on fiddler

From my work laptop which is also connected to the domain to use the fiddler on desktop as a proxy
 I am able to see the fiddler echo service page
 I can see all the traffic from my laptop on the fiddler running on my desktop
 
But when I try to connect my phone (which is in the same wifi as the laptop but is not connected to the domain) to use the proxy on my desktop
 I DONT see the fiddler echo service page
 I DONT see any traffic on fiddler
 The phone is not able to access internet
 I used the "Ping" app on iOS and it is able to ping my desktop
 I have tried to use both iOS and windows phone and I get the same results.

I have tried:
1. Allowing remote connections
2. prefs set fiddler.network.proxy.registrationhostname <desktop PC ipaddress>
3. Restarted fiddler

Am I doing anything wrong? What else do I need to do?
Any help is appreciated.

[Eric Lawrence]

Hi, Mukund--

copying from https://groups.google.com/forum/#!topic/httpfiddler/nmgr5kZ6RkU
​

 

You don't need to set registrationhostname when using a remote device (and you should undo that using about:config or Fiddler will break the next time your PC gets a new IP).

 

 

 

You have correctly set "Allow Remote Connections" and your firewall is properly configured; we know this because you're able to see traffic from your laptop.

 

 

 

Would I be correct in guessing that you're a Microsoft employee who is connected to CorpNet?

 

 

 

The problem you're having is almost certainly caused by use of IPsec, which prevents TCP/IP connections from non-domain devices to domain-joined PCs. You need to go to ITWeb and search for "IPsec boundary exemption" which will lead to a form which you can use to set your desktop PC as exempt from IPsec rules. Or you can use one of the various "Fiddler as a service" servers that some teams around the company have configured (which are already boundary-exempt). 

Regards,
Eric Lawrence
Telerik