|
Robin, Make sure that your IP address is infact 192.168.9.110 and that the daemon is running on port 4300. The easiest way to do this is go to a Command Prompt window on your PC and type: To get your ip address: ipconfig To check for listening ports: netstat -a | more You should see a line something like: TCP yantzi:4300 yantzi.torolab.ibm.com:0 LISTENING If your IP address is correct and the port is listening then something between WDSc and the iSeries might be blocking the connection like a firewall. Have you installed any firewall software on your PC lately like ZoneLabs or Symmantic Internet Security? If so then you will need to configure a rule to allow this connection in. Don Yantzi WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx Robin.Li@microage solutions.com Sent by: To wdsci-l-bounces@m wdsci-l@xxxxxxxxxxxx idrange.com cc Subject 01/14/2004 12:16 [WDSCI-L] STRRSESSVR PM Please respond to Websphere Development Studio Client for iSeries Hi, Peter Thanks for your email! I tried to use the IP address, but still no luck and got the same error message. Any other suggestions? Thanks! Robin ------------------------------ message: 7 date: Wed, 14 Jan 2004 15:13:37 +0100 from: Peter Merikan <peter.merikan@xxxxxxxxxxxxxx> subject: Re: [WDSCI-L] STRRSESVR error try to use the ip-number to your desktop STRRSESVR NAME(<your connection>) RMTLOCNAME('192.168.9.110') I think it's a dhcp problem /Peter Robin.Li@xxxxxxxxxxxxxxxxxxxxx wrote: > Hi, > > Before I try to start a interactive debug from WDS, I should do an > STRRESSVR on the green screen. It used to work all the time, however, I > run into the attached error today when I tried to run STRRSESVR > blackbox(blackbox is the connection name to the Iseries in WDS): > > Message ID . . . . . . : RSE2001 Severity . . . . . . . : 30 > Message type . . . . . : Diagnostic > Date sent . . . . . . : 01/13/04 Time sent . . . . . . : 15:55:29 > > > Message . . . . : ERROR CONNECTING TO REMOTE SYSTEMS EXPLORER > CAUSE . . . . . : THE STRRSESVR COMMAND COULD NOT CREATE A TCP/IP > CONNECTION > TO THE REMOTE SYSTEMS EXPLORER (RSE) AT REMOTE LOCATION 192.168.9.110 ON > > PORT 4300. POSSIBLE CAUSES: THE ISERIES RSE COMMUNICATIONS DAEMON HAS > NOT > BEEN STARTED ON THE CLIENT. THE REMOTE LOCATION NAME IS NOT A CORRECT > TCP/IP > HOSTNAME OR ADDRESS. THE ISERIES RSE COMMUNICATIONS DAEMON IS LISTENING > ON > A DIFFERENT PORT NUMBER. START THE ISERIES COMMUNICATION DAEMON AND > VERIFY > THAT THE REMOTE LOCATION NAME AND PORT ARE VALID. > > > I'm sure the the connection name is right, RSE communications DAEMON is > started and The port # 4300 looks like the default one. Since it worked > before without any problem, I'm really confused by this error. Any > suggestions? Thanks for the help! > > Robin > _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
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.