We have a C# application (deployed to a beta testing site) running on WinXP
that calls a third party web service.
Everytime theytry calling the service they get a "The operation has timed
out" message after about 90 seconds.
The only way we have been able to get around this is to delete (or rename)
the following registry key:
[HKEY_CURRENT_US ER\Software\Mic rosoft\Windows\ CurrentVersion\ Internet
Settings\Connec tions]\DefaultConnect ionSettings
We've tried adding the service address to the exceptions list in the proxy
settings dialog but it doesn't help.
Any ideas on why deleting(renami ng) the registry key works but adding the
address to the xceptions list doesn't?
Thanks,
Jon
that calls a third party web service.
Everytime theytry calling the service they get a "The operation has timed
out" message after about 90 seconds.
The only way we have been able to get around this is to delete (or rename)
the following registry key:
[HKEY_CURRENT_US ER\Software\Mic rosoft\Windows\ CurrentVersion\ Internet
Settings\Connec tions]\DefaultConnect ionSettings
We've tried adding the service address to the exceptions list in the proxy
settings dialog but it doesn't help.
Any ideas on why deleting(renami ng) the registry key works but adding the
address to the xceptions list doesn't?
Thanks,
Jon