Nigel Andrews said:
I have now set in the Registry entry (I had to create the subkeys under
Main)
But the site I am trying still gives "The page cannot be displayed" and I am
pretty sure it is available.
What does it say in the title bar now?
FWIW I don't have the registry switch applied
and I get "Invalid syntax error" from your example
so I would expect at least you should have a different title
to indicate that the switch has been noticed.
Hmm... I just tried your example and found two problems.
Even before the patch the RFC would not have allowed that
colon
) in the "password" parameter. You would have to encode
it as the equivalent escaped ASCII hex value (%3A).
Secondly and serendipitously, I have discovered that if you are using
a proxy on the client that you would have to add a registry value for
its program name too. Makes sense but it's a bit obscure IMO.
Some users might be aware that they had a proxy program running
because of the checkmark in the Connections dialog but that only
informs them of the port which is to be used.
Here is how an XP user might check if this applies.
1. Find the proxy port number from the Connections dialog
For purpose of example below say that that was 8080.
2. In a command window enter:
netstat -a -o | find "8080" | find /i "LISTENING"
(I.e. enter the actual port number from #1 in place of 8080.)
The -o switch (unique to XP) gives the PID of the listening task
and the PID appears at the end of each line when requested.
For purpose of example below say that that was 555.
3. Plug the listening task PID into the following pipeline in place of 555
for /f "tokens=1,2" %l in ('tasklist') do @if %m==555 echo %l %m
4. The program name of the proxy is the first parameter echoed
after the command line in #3. Add an entry for that program
in the way that 834489 describes.
BTW I used RegMon to notice this. Filter was FeatureControl
So if you have RegMon using that filter during your testing might
be easier than the above procedure. RegMon also makes evident
that for the registry changes to take effect you may need to restart
the program. (It seems to be checked once when the program is
opened.)
Could there be something else to do?
Hopefully the above description will be enough information
for you to solve the problem; otherwise here are some diagnostics
I might try.
Does netstat give you any clues?
netstat -a -n -o
Even better would be to trace the packet flow
using netcap or Ethereal.
Good luck
Robert
---
