Re: I am at a lost.... WCF

Grabbed this from another thread, with Microsofts orfiginal reply to a similar problem. Maybe it helps:

Hello,

I follow the following documents and have quick tests in my side. I can consume the WCF service that hosted in a remote Windows Service.
(http) http://msdn.microsoft.com/en-us/library/ms733069.aspx
(tcp) http://msdn.microsoft.com/en-us/library/cc949080.aspx

I think we need to check the following three points,
1. Make sure our Windows Service is started
2. Make sure we have changed the client configuration to align the server address.
3. Make sure we specify the client credential like the following codes,
-----------Client Configurations-----
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.serviceModel>
<bindings>
<netTcpBinding>
<binding name="NetTcpBinding_IService1" closeTimeout="00:01:00"
openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
transactionFlow="false" transferMode="Buffered" transactionProtocol="OleTransactions"
hostNameComparisonMode="StrongWildcard" listenBacklog="10"
maxBufferPoolSize="524288" maxBufferSize="65536" maxConnections="10"
maxReceivedMessageSize="65536">
<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
maxBytesPerRead="4096" maxNameTableCharCount="16384" />
<reliableSession ordered="true" inactivityTimeout="00:10:00"
enabled="false" />
<security mode="Transport">
<transport clientCredentialType="Windows" protectionLevel="EncryptAndSign" />
<message clientCredentialType="Windows" />
</security>
</binding>
</netTcpBinding>
</bindings>
<client>
<endpoint address="net.tcp://YOURSERVERNAME:8523/Service1" binding="netTcpBinding"
bindingConfiguration="NetTcpBinding_IService1" contract="ServiceReference1.IService1"
name="NetTcpBinding_IService1">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
</client>
</system.serviceModel>
</configuration>

-----------Client Codes----------------
ServiceReference1.Service1Client client = new ConsoleApplication1.ServiceReference1.Service1Client();
client.ClientCredentials.Windows.ClientCredential.UserName = "abc";
client.ClientCredentials.Windows.ClientCredential.Password = "abc";
Console.WriteLine(client.GetData(23));

Best regards,
Colbert Zhou (colbertz@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx


Hello Mr. Arnold" MR.,

"wajeeh" <wajeeh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F3FF6D6-7951-410E-B90D-421246B7AB52@xxxxxxxxxxxxxxxx

Arnold,

if you don't know the solutions why you replying message.

<http://blog.scorpiotek.com/2009/01/02/how-to-increase-the-maxarrayle
n gth-in-a-wcf-component/>

I removed everything from the other post.
Can you figure it out about the time-out?
Arnold,

I'm sorry, I've been following this thread, but have no clear solution
at hand. My first guess would be that there is a firewall in the way
(probably Windows Firewall), but that would be my guess.

I did follow your conversation with the original poster and today I
followed the link provided, but don't see information about a Timeout,
I do see information about MaxArray sizes, but that does not match the
OP's description. Calling people dense, or anything in that direction
isn't proper for this forum. Please, if you think he doesn't get it,
just say so and ask what he did try and why he thinks it isn't
helpful.

At the Original Poster, if people respond to your questions, it's
usually because they believe they can help. Your response to the
original answer of Mr. Arnold is, as far as I can tell, because you
had problems understanding his answer. From your replies I'd say that
you are not a native English speaker. The responses after that are
rude and inappropriate. We're only trying to help here.

Again back to the problem...

net.tcp is working, http won't budge. As I said before, my guess would
be that a firewall is in the way. But there are a lot of reasons why
this isn't working. Could you provide the code (not the configuration)
you have to set up these end points? Maybe there's something in there
that might help. You could also use Fiddler to try and find out what
is and what isn't being sent over the wire. Fiddler is a very helpful
tool when trying to debug web(service) problems.

--
Jesse Houwing
jesse.houwing at sogeti.nl
--
Jesse Houwing
jesse.houwing at sogeti.nl


.

Relevant Pages
Loading