On Friday 16 September 2016 16:51:58 Lisi Reisz wrote:
> On Friday 16 September 2016 15:53:03 Uwe Brauer wrote:
> > >>> "Lisi" == Lisi Reisz <lisi.reisz@...> writes:
> >    > On Friday 16 September 2016 11:23:24 Pisini, John wrote:
> >    >> Uwe is saying to use �8.8.8.8 and 8.8.4.4 as your DNS servers just
> >    >> to check. The system may not be able to reach the old ones
> >    >> regularly. The above ones are Google's and they do allow or at
> >    >> least don't stop people from using them.
> >    >
> >    > No, Uwe has the problem.  I suggested Google's for exactly that
> >    > reason, but Uwe did not report back.
> >
> > Ok I tried it out. I first disabled my wired net via systemsetting and
> > then called tdenetworkmanager.
>
> It sounds as though the two were being asked to give conflicting orders.  I
> should remove it from one before testing the other.  It may simply not have
> been working because system setting told it not to.
>
> > I attach the screenshot2 of the setting and the symbol of the icon,
> > which indicates IMHO that it does not connect to the wired net.
> > Please tell me whether the screenshots arrive.
>
> The screenshots arrived, but I am afraid that I am not used to sorting
> networks out by looking at icons and I'm not really sure what I am looking
> at.
>
> Did you run
> $ ip addr
> while the wireless was working?
>
> If it is working, then do:
> $ ping 8.8.8.8
>
> followed by
>
> $ ping www.google.com
>
> and send us the results.  You may have to use ^C to stop the ping command,
> depending on how your system is set up.
>
> DNS shouldn't affect connection, only finding sites.
>
> I still have no picture of your network at all.
>
> How (apart from the icon) do you know whether it is working or not?

Uwe - sorry, I should have asked.  Do you know how to use a terminal?  
(Otherwise said, do you know how to work at the CLI?)

Lisi