Error 19

Jim Terral (jterral@netidea.com)
Fri, 05 Sep 1997 07:19:28 -0700

This is a multi-part message in MIME format.
--------------C80DA7D5D58D80F81F850EDC
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

--
Jim Terral
South Slocan, BC


Have a look at the aka Boris project proposal--
http://www.netidea.com/~cyberhut/akaboris/proposal.htm




--------------C80DA7D5D58D80F81F850EDC
Content-Type: text/html; charset=us-ascii; name="error19.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="error19.html"
Content-Base: "file:///C|/Data/Txts/error19.html"






Errors Messages








Error #19 An error occurred while trying to connect

to the RealAudio Server.


Error 19 indicates that the Player and the RealServer were unable to communicate properly. This may occur for any number of reasons. 




If you can successfully use the RealAudio Player or RealPlayer at most web sites, but on a few sites receive Error 19, the cause could be that the server is not currently available because it is too busy or is not functioning properly.  It could also be that the server is offline for maintenance.  




One can verify whether or not the RealServer is down by testing several of the clips located at The RealAudio Showcase.




If these clips can be played successfully, then the problem is temporary. Please try the nonfunctioning site again at a later time. 




If you cannot play clips at the site above, please refer to the list below for less common causes of this error:





    


  1. Using Windows 95 (32-bit) Player with Windows 3.1 (16-bit) Internet software.


  2. Your computer is behind a firewall.


  3. When using the 16-bit 3.0 RealAudio Player or Player Plus with a 16-bit winsock, you may encounter Error 29: Server Disconnected, followed by Error 19.


  4. Using an older version of Novell's 16-bit winsock with RealAudio 3.0 Player.


  5. Your Internet Service Provider (ISP) is using a version of Squid Cache or Harvest Cache prior to 2.0.


  6. The site you are connecting to is using an early beta version of the 3.0 Server.





Windows 95 and Windows NT


Many Internet providers provide customers with Windows 3.1 (16-bit) Internet software, even if you use Windows 95 or Windows NT which are 32-bit operating systems. If you receive Error 19 everytime you try to play a file, it is likely that you are using a 16-bit winsock and a 32-bit version of the Player. You have two choices for solving this problem, either upgrade your winsock and browser to a 32-bit version or revert to the 16-bit Windows 3.1x version of the RealAudio Player. 




To download the 16-bit player, choose Windows 3.1x as your operating system when you download the Player. 




Note: There is no 16-bit RealPlayer 4.0 beta. So if you want to use the RealPlayer 4.0 beta, you need to have a 32-bit winsock and browser.





You are behind a Firewall


The default behavior for the Player is to receive data packets via UDP. Some systems behind packet-filtering firewalls cannot receive UDP packets. In some cases, switching the default to TCP can solve this problem. Refer to Setting Your Player to Receive Data through TCP only.




Once you have set your Player to receive data through TCP only, play a file from the internet. If this does not resolve the problem, you will need to contact your System Administrator or ISP to create a Proxy. 


 

For more complete information on firewalls and proxies and they work with the Player, search the Knowledge Base with the keywords "configure firewall".





When using the 16-bit 3.0 RealAudio Player with a 16-bit winsock, you may encounter Error 29: Server Disconnected, followed by Error 19.


This occurs when 16-bit RealAudio Player does not autoswitch from UDP to TCP when the Player has trouble receiving UDP packets. To resolve this, configure the Player so it uses TCP instead of UDP for transport. Refer to Setting Your Player to Receive Data through TCP only.


 


Using an older version of Novell's 16-bit winsock with RealAudio 3.0 Player.


This error may result if an outdated 16-bit Novell winsock is being used in conjunction with the RealAudio 3.0 Player. Progressive Networks suggests that you update this winsock by getting the latest version from Novell.




Visit Novell for the latest fixes for Novell's 16-bit Client TCP/IP protocol stack.





Your Internet Service Provider (ISP) is using a version of Squid Cache or Harvest Cache prior to 2.0.


If your ISP is using outdated versions of Squid Cache or Harvest Cache, they may interfere with UDP transmission. This problem is not common. 




Squid Cache is derived from software developed on the ARPA-funded Harvest Project which developed the Harvest Cache. Both use Internet Cache Protocol Specification v1.4 (ICP) which describes the protocol to be used for exchanging information among caches, and for application programs that need guaranteed reliable transmission of binary objects.




You can receive RealAudio sound (.ram and .rpm files) through HTTP. Within ICP, they are cached. The RealAudio signal itself is coming over UDP (default configuration) and, under ICP, is not HTTP cachable.  




The default behavior for the Player is to receive RealAudio data packets via UDP.  Squid/Harvest system's earlier beta versions prior to 2.0 perform packet-filtering and, therefore, cannot receive UDP packets. If your system cannot receive UDP packets, 

set this preference to TCP only. Refer to Setting Your Player to Receive Data through TCP only.




If the problem remains, contact your system administrator.  They may need to 

upgrade to a more current version of this Web-caching software.





The site you are connecting to is using a earlier beta version of the 3.0 server.


If, when you play an .RA file with the RealAudio Player, you receive the error message, Error 19: An error occurred while trying to connect to the 

RealAudio Server, you may have run into a known bug in earlier versions of the RealAudio 3.0 Server.




If you get this error on some RealAudio Web sites, but not others, this is the likely problem. This error can occur on builds below 180 of the beta RealAudio Server. In this case Progressive Networks would appreciate it if you notified both us and the Web site of the problem so action can be taken quickly. Please take careful note of the URL for ease of finding the outdated Server. Please contact us through our Technical Support page with the URL of the problem site. 





Setting Your Player to Receive Data through TCP only:


RealAudio Player 2.0:


    


  1. Select Preferences from the View menu.


  2. Click the Network tab in the Preferences windows.


  3. Click TCP in the Receive Audio Via box.


  4. Click the OK button.




RealAudio Player 3.0 and RealPlayer:




Note: These version of the Player should automatically detect if you cannot receive data through UDP and will switch to TCP. In some cases, you may need to force the Player to default to TCP.





    


  1. Select Preferences from the View menu. 


  2. Click the Transport tab in the Preferences windows.


  3. Click the Use Specified Transports box. 


  4. Click the Specify Transports button.


  5. Check the Use TCP for all content option and make sure that the other options are unselected. 


  6. Click the OK button in the Specify Transports window.  


  7. Click the OK button in the Preferences window.









Table of Contents



Main Help Page     

 Support Request     

 Home Page











































Legal Notice/Terms of Use















--------------C80DA7D5D58D80F81F850EDC--