Wifi and wired not talking

Being able to ping both ways rather rules that out.

Woah, VNC works where ssh, telnet and rlogin won't ? Is VNC using TCP or UDP ?

-- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. |

Sorry I didn't mention that earlier. I don't know how to distinguish between TCP and UDP.

My adventures with VNC were the subject of a number of posts before Christmas. I finally got VNC working with help from some other forum but unfortunately I can't remember which one, or the magic words that made it work. (old age is a terrible thing :-))

The RPi3 was probably wired when I set up VNC but it continues to work now that it's wireless.

Jack

By default, it uses TCP port 5900 (+ screen number).

----

Does SSH work using the wired network connection? (Just thinking that there is something fishy in SSH setup).

Well of course you can

That is normally the default.

But the only explanation of all te facts as we drag them out of the troll is that he has a firewall set up and a split network, so pings get through but e.g. ssh does not.

Since no router defaults to that, I smell troll.

I am disappointed that you think I am a troll, or that you have to drag information out of me.

The problem is that I am new to this aspect of computers and don't know what is important and what is not. If firewalls etc exist in my network they are there by default and not by any intention on my part.

In the past I have received valuable information from news groups and have provided useful information where I could in my field of expertise; mathematics.

My name is my real name and you can google me. There is a short bio at

Best Regards, Jack Fearnley

Jack if you can ping, but not connect something has specifically been done to prevent ot rather than it hasnt been configured to work.

If its not deliberately firewalled out it is just possible that the daemons are not binding to the correct interface

Netstsat is your friend and will show you what is listening on what ports.

netstat -an | grep LISTEN | grep 'tcp '

iptables will whow you what firewall rules are in place.

sudo iptables -L

check in /etc/sudoers if your setting is ok local and remote hosts must be know in that fiile For rlogin: check /etc/pam.d/rsh if it contains entry for your remote host

Irrelevant if the fault reported is 'connection refused'

Shhesh

Indeed.

Or, for even more insight:

sudo netstat -lntup

Leave out the u option if UTP is not of interest.

"connection refused" may indicat that tere is no service listening! from your ubnutu do nmap that will show open port on your remote server

nmap has many options and some are only valid for 'root'. stil check your /etc/sudoer ## Host Aliases ## Groups of machines. You may prefer to use hostnames (perhaps using ## wildcards for entire domains) or IP addresses instead. # Host_Alias FILESERVERS = fs1, fs2 # Host_Alias MAILSERVERS = smtp, smtp2 Host_Alias HOME=homepc

The IP addresss are DIFFERENT on the wired side and the wifi side so make sure both addresses are declared!!

for telent make sure you have "telnetd" installed on your raspi, "apt-get install telnetd"

Also, as ip addresses are different from the wired and wifi side, make sure the /etc/ssh/sshd_config (may be at a different locaion on your raspi" contains something like:

#AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress ::

if it contains a Listenaddress: not commentedout make sure it contain a valid address!

Thank you all for your contributions to this thread. I learned a lot.

My son found the following blog item which seems to have solved the problem.

I added the indicated changes and all ssh connections now work independent of who is wired or wifi.

It seems the problem lay with the raspberries rather than the wiring.

To be more precise, the interaction between the RPi and my ten year old router.

My apologies for setting this false wifi/wired trail in the first place.

Jack

Not at all, thank you for getting to the bottom of it and letting us know. I would never have suspected QoS settings.

-- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. |

Qos bit me when my new house ADSL reported uplink connections at 1150k but I was only gettting 448k upload

Turns out the router had that set as maximum rabbit* in its QOS settings

Rate limiting would make me suspect QoS but not working, boggle!