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



If you want to check to see if port 4300 is accessible to your pc from the
400, I ported a small portscan program to the 400.  Have a look here if
interested --> http://home.columbus.rr.com/jbmmdietz/iseries.html

Bryan

-----Original Message-----

Robin,

Let me first give a description of what goes on with STRRSESVR.  When you
run STRRSESVR the command tries to create a socket connection from the
iSeries to the PC.  Inside of WDSc there is an RSE Communications Daemon
(this used to be called the iSeries Communications Daemon but was renamed
from 5.0 to 5.1 because it is also used by other connection types) that
listens on port 4300 (by default) for this incoming socket connection.  If
the STRRSESVR command cannot connect to the daemon in WDSc then it displays
this RSE2001 error message.

The first thing to check is that the STRRSESVR is using the correct ip and
port number.  These are displayed in the 2nd level help for the RSE2001
message and should match the ip address of your PC and the port number
specified in WDSc under Window -> Preferences -> Remote Systems ->
Communications.  This page also has a checkbox to start the daemon on
workbench startup, or you can manually start the daemon using the "Start
Communications Daemon" and "Stop Communications Daemon" actions on the pull
down menu for the Remote Systems view (the pull down menu is the upside
down triangle.)

If these are all correct then make sure you can ping your PC from the
iSeries.  To do this run the following CL command:  ping ipAddress

What do you see from this command?

If that works then the last thing that goes wrong 95% of the time is a
firewall (typically installed on the PC) that blocks this connection.  The
firewall may be blocking incoming socket requests on certain ports and may
let others (like the ping request) through.  A lot of Internet security and
anti-virus software these days also act as firewalls so if you have any of
these installed make sure they allow port 4300 to accept incoming socket
requests.

Don 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.