Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problems with wsHttpBinding
Message
From
07/04/2012 10:12:18
 
General information
Forum:
ASP.NET
Category:
Windows Communication Foundation (WCF)
Environment versions
Environment:
C# 4.0
Miscellaneous
Thread ID:
01540381
Message ID:
01540580
Views:
40
>Fiddler is an HTTP proxy and it probably fixed up your machine name to an IP address that worked with the service. Machine names won't always work in HTTP unless you're on the same Windows workgroup/domain. IP addresses should always work as long as they visible to each other on the network.
>
>+++ Rick ---


Thanks Rick, but as Viv mentioned in a previous reply to you, both client and service are on the same machine, so I think Fiddler must be doing something else. Or there's something weird with my laptop (it's running XP, SP3).

Did you see my other reply to Viv in Message #1540454 where IE wouldn't work at all after using the browser as a client to try and test this? Not for any website and this was after a reboot. And the use of Fiddler fixed that too. Very strange!

~~Bonnie


>
>>Thanks Viv ... you got my brain going in a different direction and I've fixed the problem (after staring at this for days)!!
>>
>>When I tried to use Fiddler, it worked fine!! As soon as I stopped Fiddler, it crashed and burned again. I tried using the IP instead of the computer name and then it worked. Fiddler must have done something when I used the computer name and maybe that's why it worked then.
>>
>>Anyway problem solved ... use IP instead of computer name!!
>>
>>Thanks!!
>>
>>~~Bonnie
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform