× 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.



No, the RSE daemon in your computer will tell the RSE server on which port
it likes to communicate, and then it is going to listen on that port for
answers of the RSE server. So nobody else is affected by changing the port
number in your workspace.
However, most likely is that the firewall on your computer is just blocking
incoming traffic on that port 4300 so probably an allow rule in the
firewall will help.

Regards,
-Arco

Op donderdag 24 mei 2018 heeft Dan <dan27649@xxxxxxxxx> het volgende
geschreven:

Well, this stuff is kinda Greek to me, but if I change the rse deamon port
setting on my laptop, don't I have to specify the same port via STRRSESVR?
And, if I do that, will other RDi users need to make the same change?

- Dan

On Thu, May 24, 2018 at 1:23 PM, Arco Simonse <arco400@xxxxxxxxx> wrote:

Very likely this is your computers firewall blocking port 4300, or
another
application on your computer that is already listening to port 4300.
If the latter, it might help if you change the rse deamon port setting in
the preferences of your RDI workspace. This has no impact for other
users,
the port is specifically on your computer.

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.