On 11/19/06, Craig White <craigwhite@xxxxxxxxxxx> wrote:
> > > > do you have something listening on port 9734 already? if so, then > > > > there's nothing to do, except issue the telnet command (there's no > > > > colon between ipnunmber and port in telnet). > > > > > > > > i.e., unless you didn't install the telnet client for some reason, > > > > there's nothing to do to enable use the that client. > > > > > > > > now, if you don't have something already listening on 9734 and are > > > > trying to get the telnet daemon to listen there, that's a different > > > > issue. > > > > > > > > [if you have iptables running you could be blocking inbound connection > > > > attempts to random ports and you'd need to adjust that.] > > > > > > Thanks, Rick. Apparently, I do not have anything listening on 9734. I > > > get the following: > > > > > > $ telnet 127.0.0.1 > > > Trying 127.0.0.1... > > > telnet: connect to address 127.0.0.1: Connection refused > > > telnet: Unable to connect to remote host: Connection refused > > > $ > > > > > > Any further ideas? > > ---- > > psychic powers do not allow telnet to connect to other than port 23 > > unless it is specifically told to do so. > > > > telnet 127.0.0.1 9734 > > > > telnet --help > > or > > man telnet > > > > will show you the proper terminology > > > > Obviously this assumes that there is a 'listener' for a connection on > > port 9734. You can probably verify that something is listening to port > > 9734 with a command like > > > > netstat -an|grep 9734 > > Thanks, Craig. The result is: > > $ telnet 127.0.0.1 9734 > Trying 127.0.0.1... > telnet: connect to address 127.0.0.1: Connection refused > telnet: Unable to connect to remote host: Connection refused > $ > $ netstat -an|grep 9734 > $ > > i.e., ' netstat -an|grep 9734' returns nothing. ---- why don't you tell us what you are trying to accomplish on port 9734
Thanks, Craig. What I am trying to accomplish is the following: http://marc.10east.com/?l=r-help&m=116389849302592&w=2 Paul
