Failed to register Fiddler as the system proxy.

[Lopotun]

A day ago I upgraded Fiddler to version 2.2.4.6.
Since then I get the following error message: "Failed to register
Fiddler as the system proxy." while Fiddler is starting. Then I see
the normal Fiddler window.

When I try to capture traffic (F12) I get the same error message. No
traffic is captured.

Fiddler does lesten to port 8888
C:\>netstat -an | find "8888"
TCP 127.0.0.1:8888 0.0.0.0:0 LISTENING

I configured Fiddler to listen to another port. It didn't help.

Tried to re-install Fiddler. It didn't help either.

Previous version of Fiddler worked fine.

Any ideas?..

[EricLaw]

What version did you use previously?

How are you connected to the Internet?

Inside Tools / Fiddler Options / Connections, is "Monitor all
connections" checked? How many connections are listed in the box
below the checkbox?

Are you on a network where an adminstrator controls your machine using
group policy?

-Eric

[Lopotun]

Hi!
Thank you for your prompt response.

I don't know exactly what version I used. I do know that it was pretty
recent: I update Fiddler on the regular base.

I'm connected to the Internet through a cable modem (via Ethernet
card).

"Monitor all connections" wasn't checked. One connection "Dafault LAN"
appears in the boxbelow the checkbox. When I checked "Monitor all
connections", the error message stopped to appear :-)

I use my own PC at home, so noone controls my machine using group
policy.

Now I have another problem: requests from IE, Chrome and Skype are not
captured by Fiddler. Requests from any other application I used
(Opera, Java-based applications) with 127.0.01:8888 proxy setting are
successfully captured by Fiddler.
Actually, as I can see, this is not Fiddler problem. For some reason
my IE ignores its proxy server settings. Even if I write garbage
there, IE is still able to retrieve a page...

[EricLaw]

"Cable modem via ethernet card"-- can you be more specific? Is the
cable modem connected to a router, or directly to your PC?

Inside Tools / Internet Options / Connections, what connections do you
see listed in the list box on that page?

The behavior you're describing suggests that IE believes that it's
connected via a dialup modem or a VPN connection. However, the fact
that you only see "DefaultLAN" in the box in Fiddler suggests that
Fiddler is not able to see any other connections.

If you recheck the Monitor all connections box, do you still see the
same error? If so, can you try the newest alpha
https://www.fiddler2.com/dl/fiddler2alphasetup.exe with DebugView
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
running? You should see some diagnostic info in debugview when
attaching fails.

thanks for your help!

> > > Any ideas?..- Hide quoted text -
>
> - Show quoted text -

[Lopotun]

After Windows reboot I removed old connection definitions I had from
my previous providers. Then things started to work properly: Fiddler
catches requests from my IE.
In "Tools/Internet Options/Connections" I have now two entries:
"DefaultLAN"(unchecked) and "Smile - Cable Dialer"(checked).
It seems, system reboot sovled the problem. A glitch?..
At work I've upgraded Fiddler to its latest version. Everything
worked fine.

Thank you for your prompt responses and for your wonderful and very
useful application!

On 2 сен, 01:10, EricLaw <bay...@gmail.com> wrote:
> "Cable modem via ethernet card"-- can you be more specific?  Is the
> cable modem connected to a router, or directly to your PC?
>
> Inside Tools / Internet Options / Connections, what connections do you
> see listed in the list box on that page?
>
> The behavior you're describing suggests that IE believes that it's
> connected via a dialup modem or a VPN connection. However, the fact
> that you only see "DefaultLAN" in the box in Fiddler suggests that
> Fiddler is not able to see any other connections.
>
> If you recheck the Monitor all connections box, do you still see the

> same error?  If so, can you try the newest alphahttps://www.fiddler2.com/dl/fiddler2alphasetup.exewith DebugViewhttp://technet.microsoft.com/en-us/sysinternals/bb896647.aspx