On 22/01/18 20:37, Jack Fearnley wrote:
> On Mon, 22 Jan 2018 18:26:15 +0000, The Natural Philosopher wrote:
>
>> On 22/01/18 12:52, Ahem A Rivet's Shot wrote:
>>> On Sun, 21 Jan 2018 11:43:40 +0000 (GMT)
>>> "Dave Liquorice"  wrote:
>>>
>>>> On Sun, 21 Jan 2018 09:05:53 +0000, Ahem A Rivet's Shot wrote:
>>>>
>>>>>>> I'm thinking this is some kind of problem between the wired and
>>>>>>> wireless networks - are they routed or bridged together ?
>>>>
>>>> A different description of the WiFi being a "guest" subnet with access
>>>> only to other WiFi clients and the 'net.
>>>
>>>  That is only possible with them routed, but you can have a routed
>>> WiFi with full access to local resources as well, I ran mine that way
>>> for a while.
>>>
>> 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
>
> http://ctr.concordia.ca/2000-01/June_7/14-Great_Grads3/index.shtml
>
> 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


--
In todays liberal progressive conflict-free education system, everyone
gets full Marx.

--- SoupGate-Win32 v1.05