Verner wrote
fire up Konqueror and in the url line type: fish://IP-of-that-other-machine-on-your-local-net.
Both machines have the same IP 127.0.0.2 according to /etc/hosts The HOSTNAMEs are different, rwb.site and fam.site fish://127.0.0.2 gives my own machine rwb.site fish://fam.site gives error, cannot connect
Check that the firewall on that other machine is open for traffic on port 22 (YaST).
I cannot find any port in YaST2 / Security and Users / Firewall Robert -- http://rwbest.no.sapo.pt/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Robert On Saturday 16 June 2007 10:36:14 Robert Best wrote:
Verner wrote
fire up Konqueror and in the url line type: fish://IP-of-that-other-machine-on-your-local-net.
Both machines have the same IP 127.0.0.2 according to /etc/hosts The HOSTNAMEs are different, rwb.site and fam.site fish://127.0.0.2 gives my own machine rwb.site fish://fam.site gives error, cannot connect
On the fam.site machine, can you run the following command in a console: netstat -tulp | grep ssh You should see something like this: tcp 0 0 *:ssh *:* LISTEN 3696/sshd If you don't it's because the ssh daemon isn't running so there is not port for the SSH client to connect to. It's normally port 22, but that can be changed. If nothing show up in the output, the ssh daemon isn't running, so it should be started with rcsshd start
Check that the firewall on that other machine is open for traffic on port 22 (YaST).
A temporary, troubleshooting check would be to run: SuSEfirewall2 stop with that exact command (it is case sensitive) to unload the firewalls rules while we tfind the problem. If Konq can then connect using the fish:// protocol, we can configure the firewall rules to allow access. Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Robert Best wrote:
Verner wrote
fire up Konqueror and in the url line type: fish://IP-of-that-other-machine-on-your-local-net.
Both machines have the same IP 127.0.0.2 according to /etc/hosts The HOSTNAMEs are different, rwb.site and fam.site fish://127.0.0.2 gives my own machine rwb.site fish://fam.site gives error, cannot connect
Any 127.x.x.x is your local computer. It is not another computer across the network. There has to be some other address. A lot of people running behind firewalls use 192.168.x.x or 10.x.x.x. If you're connected to the internet, there has to be some other address used, beyond 127.0.0.2. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2007-06-16 at 08:06 -0400, James Knott wrote:
Robert Best wrote:
Verner wrote
fire up Konqueror and in the url line type: fish://IP-of-that-other-machine-on-your-local-net.
Both machines have the same IP 127.0.0.2 according to /etc/hosts The HOSTNAMEs are different, rwb.site and fam.site fish://127.0.0.2 gives my own machine rwb.site fish://fam.site gives error, cannot connect
Any 127.x.x.x is your local computer. It is not another computer across the network. There has to be some other address. A lot of people running behind firewalls use 192.168.x.x or 10.x.x.x. If you're connected to the internet, there has to be some other address used, beyond 127.0.0.2.
Use ip -a to see what address your eth interface is using. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2007-06-16 at 08:12 -0400, Kenneth Schneider wrote:
On Sat, 2007-06-16 at 08:06 -0400, James Knott wrote:
Robert Best wrote:
Verner wrote
fire up Konqueror and in the url line type: fish://IP-of-that-other-machine-on-your-local-net.
Both machines have the same IP 127.0.0.2 according to /etc/hosts The HOSTNAMEs are different, rwb.site and fam.site fish://127.0.0.2 gives my own machine rwb.site fish://fam.site gives error, cannot connect
Any 127.x.x.x is your local computer. It is not another computer across the network. There has to be some other address. A lot of people running behind firewalls use 192.168.x.x or 10.x.x.x. If you're connected to the internet, there has to be some other address used, beyond 127.0.0.2.
Use ip -a to see what address your eth interface is using.
Sorry, it is ip a (no -). -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
James Knott
-
Kenneth Schneider
-
Pete Connolly
-
Robert Best