ChrisVienna

I am using the 'Getting Started' Sample from the WCF Documentary. When I use 'localhost' as address everything works fine. When I change that to the name of my computer, I get a timeout exception:

System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   bei System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   bei System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)
   bei System.ServiceModel.Security.SspiNegotiationTokenProvider.OnOpen(TimeSpan timeout)
   bei System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   bei System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   bei System.ServiceModel.Security.CommunicationObjectSecurityTokenProvider.Open(TimeSpan timeout)
   bei System.ServiceModel.Security.SecurityUtils.OpenCommunicationObject(ICommunicationObject obj, TimeSpan timeout)
   bei System.ServiceModel.Security.SecurityUtils.OpenTokenProviderIfRequired(SecurityTokenProvider tokenProvider, TimeSpan timeout)
   bei System.ServiceModel.Security.SymmetricSecurityProtocol.OnOpen(TimeSpan timeout)
   bei System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   bei System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   bei System.ServiceModel.Security.SecurityProtocol.Open(TimeSpan timeout)
   bei System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpen(TimeSpan timeout)
   bei System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   bei System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)
   bei System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)
   bei System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)
   bei System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)
   bei System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   bei System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   bei System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
   bei System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   bei System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
   bei System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   bei Microsoft.ServiceModel.Samples.ICalculator.Add(Double n1, Double n2)
   bei Microsoft.ServiceModel.Samples.Client.Main()

A ping using the name of my computer works fine. In the firewall the port is enabled. This doesn't seem to be a particular WCF problem since I observed a similar problem with .NET 2.0, too.

What is the reason for this strange behavior



Re: Windows Communication Foundation (Indigo) System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Nathan Anderson - MSFT

Moving thread to WCF forum.

Thanks.





Re: Windows Communication Foundation (Indigo) System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Brian McNamara - MSFT

Have you re-run svcutil after changing the service config and restarting the service (I think the client's config may need to be correspondingly updated. Depending on the security mode, the problem you see may be a result of verifying the remote machine identity.)

You may also want to check out

http://msdn2.microsoft.com/en-us/library/ms752240.aspx

the section on running the samples across machines. (Even if it's on the same machine, you may want to follow these instructions if you are changing the address to something other than 'localhost'.)






Re: Windows Communication Foundation (Indigo) System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Ronald Ricardo Ramirez Moran

Review about this problem at :

WCF Troubleshooting Quickstart

Regards,






Re: Windows Communication Foundation (Indigo) System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

ChrisVienna

When I use the IP-Adress or the name of my computer in the config file everything works ok. But as soon as I add the domain name I get a server busy message. So it looks to me like some kind of DNS problem. On the other side 'ping' and 'nslookup' work as expected.