Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / March 2005

Tip: Looking for answers? Try searching our database.

Failure Sending a Fault: System.Net.Sockets.SocketException

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kups - 22 Feb 2005 09:29 GMT
Hi!

I have a service and client that use WSE 2.0 and soap.tcp. Both are behind
firewalls.  Client connects to a public machine's tcp port which is
redirected to service.

If I send a request  to service, it is received, but  I can't get the
answer.  
Here is the message from event log:

Event Type:    Error
Event Source:    Microsoft WSE 2.0
Event Category:    None
Event ID:    0
Date:        2/22/2005
Time:        10:20:38 AM
User:        N/A
Computer:    kups
Description:
Failure Sending a Fault: System.Net.Sockets.SocketException: A connection
attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has
failed to respond
  at Microsoft.Web.Services2.Messaging.SoapTcpConnection.Connect()
  at Microsoft.Web.Services2.Messaging.SoapTcpConnection..ctor(Uri
remoteEndpoint, SoapTcpTransportOptions options, ISoapFormatter formatter)
  at Microsoft.Web.Services2.Messaging.SoapTcpTransport.GetConnection(Uri
destination)
  at
Microsoft.Web.Services2.Messaging.SoapTcpOutputChannel.Send(SoapEnvelope
message)
  at Microsoft.Web.Services2.Messaging.SoapReceiver.SendFault(SoapEnvelope
request, Exception ex)

What could be the problem?

Kristjan
Trevor Pinkney - 22 Feb 2005 14:55 GMT
It sounds like the port that you come in on is open, but you can't get back
out on that port.  

> Hi!
>
[quoted text clipped - 38 lines]
>
> Kristjan
Kups - 04 Mar 2005 11:01 GMT
The error occured due to client-side timeout which came earlier than server
time-out. So, the client did not accept the fault message.

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.