Question about Computers & Internet

Open Question

Error when trying to open a middleware server. Reason:connecting stream socket [WSAETIMEDOUT]

Posted by on

1 Suggested Answer

  • 40 Answers

SOURCE: The connection to the server has failed. Account:

You can also receive this error message when you have antivirus e-mail protection or personal firewall software enabled on your computer.
Try disabling the antivirus program through msconfig or close the antivirus program and see if you get the same error again, if not then disable email scanning and this will help you.

Posted on Oct 04, 2009

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

MCU Firmware Error: Error 006-370: Code 00000001h on 2155cn dell printer


  • Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  • Open an IP socket connection to that IP address.
  • Write an HTTP data stream through that socket.
  • Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
  • for more help visit CBR Tech Solutions

Feb 17, 2014 | Dell 2150cn / 2150cdn / 2155cn / 2155cdn...

1 Answer

Am using small business server 2011and and it says http error service unavailable


Hi sebenzile,

The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.
Any client (e.g. your Web browse) goes through the following cycle when it communicates with the Web server:
  • Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  • Open an IP socket connection to that IP address.
  • Write an HTTP data stream through that socket.
  • Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognizes as '503'.

Basically, the Web server is effectively 'closed for repair'. It is still functioning minimally because it can at least respond with a 503 status code, but full service is impossible i.e. the Web site is simply unavailable. There are a myriad possible reasons for this, but generally it is because of some human intervention by the operators of the Web server machine. You can usually expect that someone is working on the problem, and normal service will resume as soon as possible.

You can also contact the system operators of the Web site (e.g. your ISP) to determine why the service is down. They will be in a much better position to help you than I am for this type of error.

Sorry so long winded:)
Hope this helps!
And please rate

Thanks,
Gary

Aug 27, 2013 | Computers & Internet

1 Answer

Website not displayed error http 500


The Web server (running the Web Site) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.
This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs.

500 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:
  • Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  • Open an IP socket connection to that IP address.
  • Write an HTTP data stream through that socket.
  • Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'. (Last updated: March 2012).

Fixing 500 errors - general

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.

Fixing 500 errors - CheckUpDown

Please contact us (email preferred) whenever you encounter 500 errors on your CheckUpDown account. We then have to liaise with your ISP and the vendor of the Web server software so they can trace the exact reason for the error. Correcting the error may require recoding program logic for the Web server software, which could take some time.

Jan 28, 2013 | Facebook Social Network

1 Answer

Keek -forbidden(error 408) solution


HTTP Error 408 Request timeout
Introduction

The Web server (running the Web site) thinks that there has been too long an interval of time between 1) the establishment of an IP connection (socket) between the client (e.g. your Web browser or our CheckUpDown robot) and the server and 2) the receipt of any data on that socket, so the server has dropped the connection. The socket connection has actually been lost - the Web server has 'timed out' on that particular socket connection. The request from the client must be repeated - in a timely manner.
408 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:
  • Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  • Open an IP socket connection to that IP address.
  • Write an HTTP data stream through that socket.
  • Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '408'. (Last updated: March 2012).
Fixing 408 errors - general
408 errors are often difficult to resolve. They typically involve one-off variations in system workload or operations.
If you see persistent 408 errors, the first thing to consider is the workload on the Web server - particularly around the time the 408 errors were generated. If this is light, then you also need to consider workload on the client system. If the computer systems on both ends of the socket connection seem to be running normally, then temporary Internet surges may be to blame.
Fixing 408 errors - CheckUpDown
This error is highly unlikely to occur on your CheckUpDown account, because there is usually only a tiny interval of time (milliseconds) between our 1) opening of the socket and 2) writing the HTTP data stream through that socket. In exceptional circumstances, this interval may increase because of some operations on our computer systems e.g. we temporarily suspend an executing process and this happens immediately after the socket was created. Or the two steps may follow quickly on our systems, but the second step encounters an unreasonable delay on the Internet. The acceptable interval between the two steps could also be set very low on the Web server e.g. the Web server is very busy, and has become a bit 'impatient' with attempted connections it views as a bit slow.
Any of these conditions may generate an 408 error. But they are all fairly unlikely to occur. In normal IP communications, the time interval between the two steps should be much less than 10 seconds, which should be completely acceptable to the Web server.
I hope this helps.

Oct 23, 2012 | Computers & Internet

1 Answer

1. My 2008 MacBook Pro rejects most cd's and dvd's, has a Intel 2.5 GHz Intel core 2 processor. 2. When I downloading or streaming movies they keep re-buffering


Solving Problems with Streaming Services

If the Server Does Not Start Up or Quits Unexpectedly:

  • Check the error log.
  • Make sure the QuickTimeStreamingServer file is in the /usr/sbin/ folder.

    You must be logged in to the server computer as Administrator (root) to see the QuickTimeStreamingServer file in the Workspace Manager.
  • Use the Mac OS X Server Setup Assistant to reconfigure the Ethernet ports.
If Media Files Do Not Stream Properly:
  • Check the error log.
  • Make sure the movie file is supported by the QuickTime Streaming Server. Check the list of compatible file formats.
  • Try streaming a sample movie to see if the server can stream it. You can download a sample prehinted movie from the Apple Software Updates Web site: http://www.apple.com/swupdates

    If the server streams the sample movie, the problem you're having may be with the way your movie file is prepared. Recreate the movie.

    If the sample movie doesn't stream, the problem you're having may be with the server computer or the network.
  • Try hinting the movie again with the Optimize Hints For Server option selected.
  • Check streaming server activity and if necessary, reduce the number of connections or throughput.
  • If the problem occurs on a Mac OS client computer, open the TCP/IP control panel on the client computer and make sure MacIP is not selected.
  • If the problem occurs on a client computer, make sure the user has the appropriate settings in the Streaming Proxy and Streaming Transport panels of the QuickTime Settings control panel. The administrator for the client computer's network should be able to provide the correct settings.
  • If the problem occurs for media streamed using PlaylistBroadcaster, try hinting the movies again with the RTP Payload Encoding set to QuickTime and Smooth Data Rate enabled.
  • If you are reflecting more than one live stream, make sure each stream uses a separate UDP port. Otherwise client computers will show a message with error 500. You set up ports in the relay configuration file.

If Streaming Service is Slow:
  • If you are streaming QuickTime movies, make the movies self-contained using your authoring application, and make sure hinting is optimized for streaming services.
  • Reduce the maximum number of connections or the throughput.
  • Turn off other services.
  • Place media files on other hard disks to improve server performance.

    Because QuickTime Streaming Server can use only one media folder, you need to create links from the folder you have selected in QuickTime Streaming Admin to the media files on other hard disks. To do so:

    In the Workspace Manager, press the Control key and drag the folders that contain the media from the other disks to the folder you have selected as the media folder.

Aug 04, 2011 | Computers & Internet

1 Answer

What is the meaning of HTTP 411


http://www.checkupdown.com/status/E411.html


HTTP Error 411 Length required
Introduction
The Web server (running the Web site) thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) should include a 'Content-Length' specification. This is typically used only for HTTP methods that result in the placement of data on the Web server, not the retrieval of data from it.
411 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:

  • Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  • Open an IP socket connection to that IP address.
  • Write an HTTP data stream through that socket.
  • Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '411'. Frank Vipond. September 2010.
Fixing 411 errors - general
This error seldom occurs in most Web traffic, particularly when the client system is a Web browser. The problem can only be resolved by examining what your client system is trying to do then discussing with your ISP why the Web server expects a 'Content-Length' specification.
Fixing 411 errors - CheckUpDown
This error should simply never occur on your CheckUpDown account. If it does, it typically indicates defective programming of our systems or of the Web server which manages the site. The 'Content-Length' specification is irrelevant to the type of access we use when we check your URL.
Please contact us (email preferred) whenever you encounter 411 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of the Web server software to agree the exact reason for the error.

May 24, 2011 | General Computers & Internet

1 Answer

Please describe solution of error 413 problem:


HTTP Error 413 Request entity too large
Introduction
The Web server (running the Web site) thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) was simply too large i.e. too many bytes. What constitutes 'too many bytes' depends partly upon the operation being attempted. For example a request to upload a very large file (via the HTTP PUT method) may encounter a ceiling on upload file size set by the Web server.
413 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:

  • Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  • Open an IP socket connection to that IP address.
  • Write an HTTP data stream through that socket.
  • Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receive an HTTP status code that it recognises as '413'. Frank Vipond. September 2010.
Fixing 413 errors - general
This error seldom occurs in most Web traffic, particularly when the client system is a Web browser. The problem can only be resolved by examining what your client system is trying to do then discussing with your ISP why the Web server rejects the number of bytes sent by the client system.
Fixing 413 errors - CheckUpDown
This error should simply never occur on your CheckUpDown account. If it does, it typically indicates defective programming of our systems or of the Web server which manages the site. The length of the HTTP data stream we normally send is relatively small and well within the limits of what most Web servers should accept.
Please contact us (email preferred) whenever you encounter 413 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of the Web server software to agree the exact reason for the error.
hope this helps

Mar 01, 2011 | Computers & Internet

2 Answers

Get a 403 error message


Hi,I am hosting with this http://www.tucktail.com/ site,still now there is no problem for me,you too also try this one,All the best.

Jun 17, 2009 | Twitter Tweets

1 Answer

Every time i try to get on youtube it comes up.But when i click on my account it says 400 bad request. when i tryed to click on my friends video of gymnastics it says 400 bad request. Please Help Quick


Introduction
The Web server (running the Web site) thinks that the data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) was 'malformed' i.e. did not respect the HTTP protocol completely. So the Web server was unable to understand the request and process it.

It almost always means bad programming of the client system and/or the Web server. 

400 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:
Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs). 
Open an IP socket connection to that IP address. 
Write an HTTP data stream through that socket. 
Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information. 

This error occurs in the final step above when the client receives an HTTP status code it recognises as '400'.

Fixing 400 errors - general

There is a low-level program bug in the client or the Web server or both. If you do not have access to the source code for these systems, the only thing you can do is refer the problem to technical support people at the companies that developed the systems.

Fixing 400 errors - CheckUpDown

You should never see this error at all when you use our CheckUpDown service. It indicates that the two systems (our robot and the Web server) fundamentally disagree on the syntax of HTTP data streams.

Please contact us directly (email preferred) whenever you encounter 400 errors. Only we can resolve them for you. Unfortunately this may take some time, because we have to analyse the underlying HTTP data streams and may have to liaise with your ISP and the vendor of the Web server software to agree the exact source of the error.

Jun 14, 2009 | YouTube Videos

1 Answer

When trying to refresh a Business Objects error... DMA0007


If changes have been made to the universe it may well be that in Deski you're using a local copy of it,
I would first advise exporting the universe to the repository (cms ) and having another go in Infoview just to ensure that the same copy of the universe is being used.

If it still fails, you will need access to the Business Objects server as it could well be that the connection on the server is either missing, incorrect or using a different version of middleware.

The fastest way to check on the server, is to launch Deski directly on the server and import the report > refresh it and see if you get the error.
If so then we know that it's a connectivity issue.

Sep 11, 2007 | Business Objects BusinessObjects...

Not finding what you are looking for?
Computers & Internet Logo

Related Topics:

65 people viewed this question

Ask a Question

Usually answered in minutes!

Top Computers & Internet Experts

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers

kakima

Level 3 Expert

101607 Answers

David Payne
David Payne

Level 3 Expert

14160 Answers

Are you a Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...