× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WDSCI-L
  3. February 2010

RSE communications daemon could not be started on port 4300

I keep getting this error message when running "stuff" in RDi, like the
Application Diagrams or the Outline.



NETSTAT does not specifically identify the port being busy.



Anyone have an idea what to fix?





The RSE communications daemon could not be started on port 4300. Check
that the port is free and restart the daemon or change the port used by
the daemon using the Remote Systems -> Communications Workbench
preference page.

<



Thanks, Matt




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.