Message: previous - next
Month: September 2016

Re: [trinity-users] Re: tdenetworkmanager cannot connect to wired

From: Lisi Reisz <lisi.reisz@...>
Date: Fri, 16 Sep 2016 16:51:58 +0100
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 � and 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 

Did you run 
$ ip addr
while the wireless was working?

If it is working, then do:
$ ping

followed by

$ ping

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?