Using WCF HttpBindings on a LAN
Posted
by dcw
on Stack Overflow
See other posts from Stack Overflow
or by dcw
Published on 2010-04-20T03:39:52Z
Indexed on
2010/04/20
3:43 UTC
Read the original article
Hit count: 271
We have a WCF-based client server that operates over a LAN. We've been getting along ok by using the NetTcpBinding, chosen because we couldn't get either HttpBinding to work between hosts. (Within a single host works fine, but is not useful for the production environment.)
We're now back at the point where we want to explore using either BasicHttpBinding or WsHttpBinding, but we simply can't see the server from the client: even putting in the path to the endpoint into IE fails to see the server.
Is there something simple we've overlooked? We're not specifying any security settings (or anything else, for that matter). Should we be doing so (e.g. explicitly setting security settings to None)?
© Stack Overflow or respective owner