• lost wired internet connection Ubuntu 22.04

    From wAYNE@21:1/5 to All on Tue Oct 11 10:45:53 2022
    My laptop has been working fine since the fresh install of 22.04.
    Today, however, I noticed a question mark instead of the connection icon
    while trying to connect to my wired router. First step was to swap out
    the 50 foot cat5 cable, same thing. Then, swap out for another shorter
    one I use for situations like now when I need to get back on the
    desktop. Still have the question mark. As you can see, my connection
    is fine from the desktop and both are using the same router.

    Trying to troubleshoot, first thing I did was to turn off "connectivity checking" under privacy. That gives the solid connection icon now, but
    still no apparent connectivity.

    I've tried to restart network manager and get a message about failing to restart, but that was before rebooting. Once rebooted, no difference,
    still unable to connect.

    Any suggestions welcome. Everything had been working fine until this
    morning.

    Thanks in advance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From wAYNE@21:1/5 to Marco Moock on Tue Oct 11 11:14:55 2022
    On 10/11/22 10:47 AM, Marco Moock wrote:
    On 11 Oct 2022 10:45:53 -0400 wAYNE <none@nowhere.net> wrote:

    Any suggestions welcome. Everything had been working fine until this
    morning.

    Post the output of

    ip a
    resolvectl
    cat /etc/resolv.conf

    When the connection is established and the question mark is there.



    ip a

    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
    state UP group default qlen 1000
    link/ether 00:23:ae:31:df:70 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.224/24 brd 192.168.1.255 scope global dynamic
    noprefixroute enp9s0
    valid_lft 563sec preferred_lft 563sec
    inet6 fe80::db86:de8c:8266:76/64 scope link noprefixroute
    valid_lft forever preferred_lft forever
    3: wlp12s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
    default qlen 1000
    link/ether 0c:60:76:66:f6:c4 brd ff:ff:ff:ff:ff:ff





    resolvectl

    Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub

    Link 2 (enp9s0)
    Current Scopes: DNS
    Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    Current DNS Server: 192.168.1.1
    DNS Servers: 192.168.1.1
    DNS Domain: fios-router.home

    Link 3 (wlp12s0)
    Current Scopes: none
    Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS
    DNSSEC=no/unsupported




    cat /etc/resolv.conf


    # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
    # Do not edit.
    #
    # This file might be symlinked as /etc/resolv.conf. If you're looking at
    # /etc/resolv.conf and seeing this text, you have followed the symlink.
    #
    # This is a dynamic resolv.conf file for connecting local clients to the
    # internal DNS stub resolver of systemd-resolved. This file lists all
    # configured search domains.
    #
    # Run "resolvectl status" to see details about the uplink DNS servers
    # currently in use.
    #
    # Third party programs should typically not access this file directly,
    but only
    # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
    # different way, replace this symlink by a static file or a different
    symlink.
    #
    # See man:systemd-resolved.service(8) for details about the supported
    modes of
    # operation for /etc/resolv.conf.

    nameserver 127.0.0.53
    options edns0 trust-ad
    search fios-router.home

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to none@nowhere.net on Tue Oct 11 16:47:27 2022
    On 11 Oct 2022 10:45:53 -0400 wAYNE <none@nowhere.net> wrote:

    Any suggestions welcome. Everything had been working fine until this morning.

    Post the output of

    ip a
    resolvectl
    cat /etc/resolv.conf

    When the connection is established and the question mark is there.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From wAYNE@21:1/5 to All on Tue Oct 11 12:09:13 2022
    T24gMTAvMTEvMjIgMTE6MTQgQU0sIHdBWU5FIHdyb3RlOg0KPiBPbiAxMC8xMS8yMiAxMDo0 NyBBTSwgTWFyY28gTW9vY2sgd3JvdGU6DQo+PiBPbiAxMSBPY3QgMjAyMiAxMDo0NTo1MyAt MDQwMCB3QVlORSA8bm9uZUBub3doZXJlLm5ldD4gd3JvdGU6DQo+Pg0KPj4+IEFueSBzdWdn ZXN0aW9ucyB3ZWxjb21lLsKgIEV2ZXJ5dGhpbmcgaGFkIGJlZW4gd29ya2luZyBmaW5lIHVu dGlsIHRoaXMNCj4+PiBtb3JuaW5nLg0KPj4NCj4+IFBvc3QgdGhlIG91dHB1dCBvZg0KPj4N Cj4+IGlwIGENCj4+IHJlc29sdmVjdGwNCj4+IGNhdCAvZXRjL3Jlc29sdi5jb25mDQo+Pg0K Pj4gV2hlbiB0aGUgY29ubmVjdGlvbiBpcyBlc3RhYmxpc2hlZCBhbmQgdGhlIHF1ZXN0aW9u IG1hcmsgaXMgdGhlcmUuDQo+Pg0KPiANCj4gDQo+IGlwIGENCj4gDQo+IDE6IGxvOiA8TE9P UEJBQ0ssVVAsTE9XRVJfVVA+IG10dSA2NTUzNiBxZGlzYyBub3F1ZXVlIHN0YXRlIFVOS05P V04gDQo+IGdyb3VwIGRlZmF1bHQgcWxlbiAxMDAwDQo+ICDCoMKgwqAgbGluay9sb29wYmFj ayAwMDowMDowMDowMDowMDowMCBicmQgMDA6MDA6MDA6MDA6MDA6MDANCj4gIMKgwqDCoCBp bmV0IDEyNy4wLjAuMS84IHNjb3BlIGhvc3QgbG8NCj4gIMKgwqDCoMKgwqDCoCB2YWxpZF9s ZnQgZm9yZXZlciBwcmVmZXJyZWRfbGZ0IGZvcmV2ZXINCj4gIMKgwqDCoCBpbmV0NiA6OjEv MTI4IHNjb3BlIGhvc3QNCj4gIMKgwqDCoMKgwqDCoCB2YWxpZF9sZnQgZm9yZXZlciBwcmVm ZXJyZWRfbGZ0IGZvcmV2ZXINCj4gMjogZW5wOXMwOiA8QlJPQURDQVNULE1VTFRJQ0FTVCxV UCxMT1dFUl9VUD4gbXR1IDE1MDAgcWRpc2MgZnFfY29kZWwgDQo+IHN0YXRlIFVQIGdyb3Vw IGRlZmF1bHQgcWxlbiAxMDAwDQo+ICDCoMKgwqAgbGluay9ldGhlciAwMDoyMzphZTozMTpk Zjo3MCBicmQgZmY6ZmY6ZmY6ZmY6ZmY6ZmYNCj4gIMKgwqDCoCBpbmV0IDE5Mi4xNjguMS4y MjQvMjQgYnJkIDE5Mi4xNjguMS4yNTUgc2NvcGUgZ2xvYmFsIGR5bmFtaWMgDQo+IG5vcHJl Zml4cm91dGUgZW5wOXMwDQo+ICDCoMKgwqDCoMKgwqAgdmFsaWRfbGZ0IDU2M3NlYyBwcmVm ZXJyZWRfbGZ0IDU2M3NlYw0KPiAgwqDCoMKgIGluZXQ2IGZlODA6OmRiODY6ZGU4Yzo4MjY2 Ojc2LzY0IHNjb3BlIGxpbmsgbm9wcmVmaXhyb3V0ZQ0KPiAgwqDCoMKgwqDCoMKgIHZhbGlk X2xmdCBmb3JldmVyIHByZWZlcnJlZF9sZnQgZm9yZXZlcg0KPiAzOiB3bHAxMnMwOiA8QlJP QURDQVNULE1VTFRJQ0FTVD4gbXR1IDE1MDAgcWRpc2Mgbm9vcCBzdGF0ZSBET1dOIGdyb3Vw IA0KPiBkZWZhdWx0IHFsZW4gMTAwMA0KPiAgwqDCoMKgIGxpbmsvZXRoZXIgMGM6NjA6NzY6 NjY6ZjY6YzQgYnJkIGZmOmZmOmZmOmZmOmZmOmZmDQo+IA0KPiANCj4gDQo+IA0KPiANCj4g cmVzb2x2ZWN0bA0KPiANCj4gIMKgwqDCoMKgwqDCoMKgwqDCoMKgIFByb3RvY29sczogLUxM TU5SIC1tRE5TIC1ETlNPdmVyVExTIEROU1NFQz1uby91bnN1cHBvcnRlZA0KPiByZXNvbHYu Y29uZiBtb2RlOiBzdHViDQo+IA0KPiBMaW5rIDIgKGVucDlzMCkNCj4gIMKgwqDCoCBDdXJy ZW50IFNjb3BlczogRE5TDQo+ICDCoMKgwqDCoMKgwqDCoMKgIFByb3RvY29sczogK0RlZmF1 bHRSb3V0ZSArTExNTlIgLW1ETlMgLUROU092ZXJUTFMgDQo+IEROU1NFQz1uby91bnN1cHBv cnRlZA0KPiBDdXJyZW50IEROUyBTZXJ2ZXI6IDE5Mi4xNjguMS4xDQo+ICDCoMKgwqDCoMKg wqAgRE5TIFNlcnZlcnM6IDE5Mi4xNjguMS4xDQo+ICDCoMKgwqDCoMKgwqDCoCBETlMgRG9t YWluOiBmaW9zLXJvdXRlci5ob21lDQo+IA0KPiBMaW5rIDMgKHdscDEyczApDQo+IEN1cnJl bnQgU2NvcGVzOiBub25lDQo+ICDCoMKgwqDCoCBQcm90b2NvbHM6IC1EZWZhdWx0Um91dGUg K0xMTU5SIC1tRE5TIC1ETlNPdmVyVExTIA0KPiBETlNTRUM9bm8vdW5zdXBwb3J0ZWQNCj4g DQo+IA0KPiANCj4gDQo+IGNhdCAvZXRjL3Jlc29sdi5jb25mDQo+IA0KPiANCj4gIyBUaGlz IGlzIC9ydW4vc3lzdGVtZC9yZXNvbHZlL3N0dWItcmVzb2x2LmNvbmYgbWFuYWdlZCBieSAN Cj4gbWFuOnN5c3RlbWQtcmVzb2x2ZWQoOCkuDQo+ICMgRG8gbm90IGVkaXQuDQo+ICMNCj4g IyBUaGlzIGZpbGUgbWlnaHQgYmUgc3ltbGlua2VkIGFzIC9ldGMvcmVzb2x2LmNvbmYuIElm IHlvdSdyZSBsb29raW5nIGF0DQo+ICMgL2V0Yy9yZXNvbHYuY29uZiBhbmQgc2VlaW5nIHRo aXMgdGV4dCwgeW91IGhhdmUgZm9sbG93ZWQgdGhlIHN5bWxpbmsuDQo+ICMNCj4gIyBUaGlz IGlzIGEgZHluYW1pYyByZXNvbHYuY29uZiBmaWxlIGZvciBjb25uZWN0aW5nIGxvY2FsIGNs aWVudHMgdG8gdGhlDQo+ICMgaW50ZXJuYWwgRE5TIHN0dWIgcmVzb2x2ZXIgb2Ygc3lzdGVt ZC1yZXNvbHZlZC4gVGhpcyBmaWxlIGxpc3RzIGFsbA0KPiAjIGNvbmZpZ3VyZWQgc2VhcmNo IGRvbWFpbnMuDQo+ICMNCj4gIyBSdW4gInJlc29sdmVjdGwgc3RhdHVzIiB0byBzZWUgZGV0 YWlscyBhYm91dCB0aGUgdXBsaW5rIEROUyBzZXJ2ZXJzDQo+ICMgY3VycmVudGx5IGluIHVz ZS4NCj4gIw0KPiAjIFRoaXJkIHBhcnR5IHByb2dyYW1zIHNob3VsZCB0eXBpY2FsbHkgbm90 IGFjY2VzcyB0aGlzIGZpbGUgZGlyZWN0bHksIA0KPiBidXQgb25seQ0KPiAjIHRocm91Z2gg dGhlIHN5bWxpbmsgYXQgL2V0Yy9yZXNvbHYuY29uZi4gVG8gbWFuYWdlIG1hbjpyZXNvbHYu Y29uZig1KSANCj4gaW4gYQ0KPiAjIGRpZmZlcmVudCB3YXksIHJlcGxhY2UgdGhpcyBzeW1s aW5rIGJ5IGEgc3RhdGljIGZpbGUgb3IgYSBkaWZmZXJlbnQgDQo+IHN5bWxpbmsuDQo+ICMN Cj4gIyBTZWUgbWFuOnN5c3RlbWQtcmVzb2x2ZWQuc2VydmljZSg4KSBmb3IgZGV0YWlscyBh Ym91dCB0aGUgc3VwcG9ydGVkIA0KPiBtb2RlcyBvZg0KPiAjIG9wZXJhdGlvbiBmb3IgL2V0 Yy9yZXNvbHYuY29uZi4NCj4gDQo+IG5hbWVzZXJ2ZXIgMTI3LjAuMC41Mw0KPiBvcHRpb25z IGVkbnMwIHRydXN0LWFkDQo+IHNlYXJjaCBmaW9zLXJvdXRlci5ob21lDQo+IA0KDQoNCk9r LCBzbyBJJ20gYmFjayBvbiB0aGUgbGFwdG9wIGFuZCB0eXBpbmcgZnJvbSBpdC4gIEkgbm90 aWNlZCB0aGF0IHRoZSANCnNhbWUgc3ltcHRvbXMgd2VyZSBoYXBwZW5pbmcgb24gaGVyZSB3 aGVuIEkgYm9vdGVkIGludG8gV2luIDEwLiAgU28sIEkgDQp0cmllZCBzb21ldGhpbmcgSSBo YXZlbid0IGRvbmUgaW4geWVhcnMgd2l0aCB0aGUgbGFwdG9wLCBlbmFibGVkIFdpRmkuIA0K T25jZSBJIGRpZCB0aGF0LCBhbmQgYWxzbyBlbmFibGVkIG15IEZpb3MgV2lGaSByb3V0ZXIs IEkgd2FzIGFibGUgdG8gDQpjb25uZWN0IGZ1bGx5Li4uLiBidXQgbm93IGl0IHNlZW1zIHRo YXQgSSd2ZSBsb3N0IG15IHdpcmVkIGRlc2t0b3AgDQpjb25uZWN0aW9uLg0KDQpJIGhhdmVu J3QgdXNlZCBXaUZpIGZvciB5ZWFycyBmb3IgUEMgdG8gcm91dGVyIGNvbm5lY3Rpb24sIHNv IGRvbid0IA0KcmVjYWxsIGlmIEkgY2FuIGNvbm5lY3QgdG8gdGhlIEZpb3Mgcm91dGVyIHNp bXVsdGFuZW91c2x5IHdpdGggYm90aCBXaUZpIA0KYW5kIHdpcmVkIGNvbm5lY3Rpb25zLCBi dXQgSSBzaG91bGQgYmUgYWJsZSB0byEgIEFueSB0aG91Z2h0cyBvbiB0aGF0IA0Kd2VsY29t ZS4gIEl0J3MgcHJvYmFibHkgc29tZXRoaW5nIHdpdGggdGhlIHJvdXRlciBzZXR0aW5ncy4u Li4NCg0KQXMgZmFyIGFzIHRoZSBsYXB0b3AsIHNpbmNlIGl0IG9ubHkgY29ubmVjdHMgYnkg V2lGaSBub3cgb24gYm90aCBXaW4gYW5kIA0KVWJ1bnR1IGFuZCBub3Qgd2lyZWQsIEkgYW0g c3VzcGVjdGluZyBhbiBpc3N1ZSB3aXRoIHRoZSB3aXJlZCBqYWNrIG9yIA0Kc29tZXRoaW5n IG9uIHRoZSBtb3RoZXJib2FyZCg/KS4gIE5vdCBhIGhhcHB5IGNhbXBlciBhYm91dCB0aGF0 LiAgSSANCnByZWZlciBteSB3aXJlZCBjb25uZWN0aW9ucyBvdmVyIHdpcmVsZXNzLg0K

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From wAYNE@21:1/5 to All on Tue Oct 11 12:29:13 2022
    Ok, managed to get everything working again although not quite to my satisfaction.

    Apparently, I had to go into the router and "unblock" my desktop, since
    it uses a wired, and the laptop uses the WiFi. Once that was done, now
    both PCs can simultaneously connect.

    I'm not happy about having to enable WiFi on the laptop to get
    connectivity. Any thought on why the wired no longer works would be
    welcome. As I mentioned, it seems to not work wired on either Win or
    Ubuntu, whichever I boot into. Switching out cat5 cables did not
    remedy. Could it be a connector, motherboard, or bios issue?

    A separate question relating to Wifi frequency. I'm on the old Dell
    Inspiron 1545 laptop. In the Fios router, it seems to have both 2.4 Ghz
    and 5 Ghz. I set up for 2.4. Should I stick with that, or try the 5
    Ghz connection and, if so, what's the advantage if any? As I said, I
    haven't used or configured WiFi in years.

    Thanks in advance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From wAYNE@21:1/5 to Marco Moock on Tue Oct 11 12:48:22 2022
    On 10/11/22 12:26 PM, Marco Moock wrote:
    Am 11.10.2022 um 12:09:13 Uhr schrieb wAYNE:

    and also enabled my Fios WiFi router, I was able to
    connect fully.

    Post the outputs again when connected to WiFi.
    You don't have IPv6 (maybe you can enable that in the router).


    ip a


    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel
    state DOWN group default qlen 1000
    link/ether 00:23:ae:31:df:70 brd ff:ff:ff:ff:ff:ff
    3: wlp12s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
    state UP group default qlen 1000
    link/ether 0c:60:76:66:f6:c4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.151/24 brd 192.168.1.255 scope global dynamic
    noprefixroute wlp12s0
    valid_lft 85017sec preferred_lft 85017sec
    inet6 fe80::99c:a3a7:1955:7435/64 scope link noprefixroute
    valid_lft forever preferred_lft forever



    resolvectl



    Global
    Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub

    Link 2 (enp9s0)
    Current Scopes: none
    Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS
    DNSSEC=no/unsupported

    Link 3 (wlp12s0)
    Current Scopes: DNS
    Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    Current DNS Server: 192.168.1.1
    DNS Servers: 192.168.1.1
    DNS Domain: fios-router.home




    cat /etc/resolv.conf


    # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
    # Do not edit.
    #
    # This file might be symlinked as /etc/resolv.conf. If you're looking at
    # /etc/resolv.conf and seeing this text, you have followed the symlink.
    #
    # This is a dynamic resolv.conf file for connecting local clients to the
    # internal DNS stub resolver of systemd-resolved. This file lists all
    # configured search domains.
    #
    # Run "resolvectl status" to see details about the uplink DNS servers
    # currently in use.
    #
    # Third party programs should typically not access this file directly,
    but only
    # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
    # different way, replace this symlink by a static file or a different
    symlink.
    #
    # See man:systemd-resolved.service(8) for details about the supported
    modes of
    # operation for /etc/resolv.conf.

    nameserver 127.0.0.53
    options edns0 trust-ad
    search fios-router.home

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Tue Oct 11 18:26:08 2022
    Am 11.10.2022 um 12:09:13 Uhr schrieb wAYNE:

    and also enabled my Fios WiFi router, I was able to
    connect fully.

    Post the outputs again when connected to WiFi.
    You don't have IPv6 (maybe you can enable that in the router).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Tue Oct 11 19:58:04 2022
    You also get IPv4 and DNS. Please try ping google.de with Ethernet and
    WIFi.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Killadebug@21:1/5 to wAYNE on Tue Oct 11 20:57:40 2022
    On Tue, 11 Oct 2022 12:29:13 -0400, wAYNE wrote:

    Ok, managed to get everything working again although not quite to my satisfaction.

    Apparently, I had to go into the router and "unblock" my desktop, since
    it uses a wired, and the laptop uses the WiFi. Once that was done, now
    both PCs can simultaneously connect.

    I'm not happy about having to enable WiFi on the laptop to get
    connectivity. Any thought on why the wired no longer works would be
    welcome. As I mentioned, it seems to not work wired on either Win or
    Ubuntu, whichever I boot into. Switching out cat5 cables did not
    remedy. Could it be a connector, motherboard, or bios issue?

    A separate question relating to Wifi frequency. I'm on the old Dell
    Inspiron 1545 laptop. In the Fios router, it seems to have both 2.4 Ghz
    and 5 Ghz. I set up for 2.4. Should I stick with that, or try the 5
    Ghz connection and, if so, what's the advantage if any? As I said, I
    haven't used or configured WiFi in years.

    Thanks in advance.

    % Ghz will give much better thru put, I would use that if your laptop is
    close to your router. % Ghz gets progressively weak the more walls it
    must go thru.

    As far as your wired connection gos, di you try a different network port
    on your router? You also may want to check the wired port speed settings
    on your router for the port that is giving you trouble. I always hard
    code the port speed and duplex. Auto-negotiate is kinda of picky that is
    why I had code.



    --
    Pull my finger

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From wAYNE@21:1/5 to Killadebug on Tue Oct 11 19:40:38 2022
    On 10/11/22 4:57 PM, Killadebug wrote:
    On Tue, 11 Oct 2022 12:29:13 -0400, wAYNE wrote:

    Ok, managed to get everything working again although not quite to my
    satisfaction.

    Apparently, I had to go into the router and "unblock" my desktop, since
    it uses a wired, and the laptop uses the WiFi. Once that was done, now
    both PCs can simultaneously connect.

    I'm not happy about having to enable WiFi on the laptop to get
    connectivity. Any thought on why the wired no longer works would be
    welcome. As I mentioned, it seems to not work wired on either Win or
    Ubuntu, whichever I boot into. Switching out cat5 cables did not
    remedy. Could it be a connector, motherboard, or bios issue?

    A separate question relating to Wifi frequency. I'm on the old Dell
    Inspiron 1545 laptop. In the Fios router, it seems to have both 2.4 Ghz
    and 5 Ghz. I set up for 2.4. Should I stick with that, or try the 5
    Ghz connection and, if so, what's the advantage if any? As I said, I
    haven't used or configured WiFi in years.

    Thanks in advance.

    % Ghz will give much better thru put, I would use that if your laptop is close to your router. % Ghz gets progressively weak the more walls it
    must go thru.

    As far as your wired connection gos, di you try a different network port
    on your router? You also may want to check the wired port speed settings
    on your router for the port that is giving you trouble. I always hard
    code the port speed and duplex. Auto-negotiate is kinda of picky that is
    why I had code.




    Yes, I did try different router ports but no difference. I'm now
    thinking that this is the charger board in the laptop as it contains
    the power jack, USB port and ethernet port. It is a small board that
    can be replaced and I have a replacement on the way. I just got
    finished swapping out the defunct motherboard and it's possible that the charger board is causing trouble.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to wAYNE on Wed Oct 12 09:22:55 2022
    On 10/11/2022 7:40 PM, wAYNE wrote:
    On 10/11/22 4:57 PM, Killadebug wrote:
    On Tue, 11 Oct 2022 12:29:13 -0400, wAYNE wrote:

    Ok, managed to get everything working again although not quite to my
    satisfaction.

    Apparently, I had to go into the router and "unblock" my desktop, since
    it uses a wired, and the laptop uses the WiFi.  Once that was done, now >>> both PCs can simultaneously connect.

    I'm not happy about having to enable WiFi on the laptop to get
    connectivity.  Any thought on why the wired no longer works would be
    welcome.  As I mentioned, it seems to not work wired on either Win or
    Ubuntu, whichever I boot into.  Switching out cat5 cables did not
    remedy.  Could it be a connector, motherboard, or bios issue?

    A separate question relating to Wifi frequency.  I'm on the old Dell
    Inspiron 1545 laptop.  In the Fios router, it seems to have both 2.4 Ghz >>> and 5 Ghz.  I set up for 2.4.  Should I stick with that, or try the 5
    Ghz connection and, if so, what's the advantage if any?  As I said, I
    haven't used or configured WiFi in years.

    Thanks in advance.

    % Ghz will give much better thru put, I would use that if your laptop is
    close to your router. % Ghz gets progressively weak the more walls it
    must go thru.

    As far as your wired connection gos, di you try a different network port
    on your router? You also may want to check the wired port speed settings
    on your router for the port that is giving you trouble. I always hard
    code the port speed and duplex. Auto-negotiate is kinda of picky that is
    why I had code.




    Yes, I did try different router ports but no difference.  I'm now thinking that this is the charger board in the laptop as it contains the power jack, USB port and ethernet port.  It is a small board that can be replaced and I have a replacement on
    the way.  I just got finished swapping out the defunct motherboard and it's possible that the charger board is causing trouble.

    That's one weird board. The Ethernet port connector looks
    like a trouble-maker. Like the wires are SMT and underneath
    the connector body.

    https://www.dcxpower.com/dell-inspiron-1545-1546-pp41l-484aq03011021c11c21-484aq13csc-484aq200sb-484aq230sb-dr1-0853012sc-dc-power-jack-socket-connector-vga-rj45-lan-usb-port-in-charging-board-p-194.html

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From wAYNE@21:1/5 to All on Thu Oct 13 14:39:04 2022
    T24gMTAvMTIvMjIgOToyMiBBTSwgUGF1bCB3cm90ZToNCj4gT24gMTAvMTEvMjAyMiA3OjQw IFBNLCB3QVlORSB3cm90ZToNCj4+IE9uIDEwLzExLzIyIDQ6NTcgUE0sIEtpbGxhZGVidWcg d3JvdGU6DQo+Pj4gT24gVHVlLCAxMSBPY3QgMjAyMiAxMjoyOToxMyAtMDQwMCwgd0FZTkUg d3JvdGU6DQo+Pj4NCj4+Pj4gT2ssIG1hbmFnZWQgdG8gZ2V0IGV2ZXJ5dGhpbmcgd29ya2lu ZyBhZ2FpbiBhbHRob3VnaCBub3QgcXVpdGUgdG8gbXkNCj4+Pj4gc2F0aXNmYWN0aW9uLg0K Pj4+Pg0KPj4+PiBBcHBhcmVudGx5LCBJIGhhZCB0byBnbyBpbnRvIHRoZSByb3V0ZXIgYW5k ICJ1bmJsb2NrIiBteSBkZXNrdG9wLCBzaW5jZQ0KPj4+PiBpdCB1c2VzIGEgd2lyZWQsIGFu ZCB0aGUgbGFwdG9wIHVzZXMgdGhlIFdpRmkuwqAgT25jZSB0aGF0IHdhcyBkb25lLCBub3cN Cj4+Pj4gYm90aCBQQ3MgY2FuIHNpbXVsdGFuZW91c2x5IGNvbm5lY3QuDQo+Pj4+DQo+Pj4+ IEknbSBub3QgaGFwcHkgYWJvdXQgaGF2aW5nIHRvIGVuYWJsZSBXaUZpIG9uIHRoZSBsYXB0 b3AgdG8gZ2V0DQo+Pj4+IGNvbm5lY3Rpdml0eS7CoCBBbnkgdGhvdWdodCBvbiB3aHkgdGhl IHdpcmVkIG5vIGxvbmdlciB3b3JrcyB3b3VsZCBiZQ0KPj4+PiB3ZWxjb21lLsKgIEFzIEkg bWVudGlvbmVkLCBpdCBzZWVtcyB0byBub3Qgd29yayB3aXJlZCBvbiBlaXRoZXIgV2luIG9y DQo+Pj4+IFVidW50dSwgd2hpY2hldmVyIEkgYm9vdCBpbnRvLsKgIFN3aXRjaGluZyBvdXQg Y2F0NSBjYWJsZXMgZGlkIG5vdA0KPj4+PiByZW1lZHkuwqAgQ291bGQgaXQgYmUgYSBjb25u ZWN0b3IsIG1vdGhlcmJvYXJkLCBvciBiaW9zIGlzc3VlPw0KPj4+Pg0KPj4+PiBBIHNlcGFy YXRlIHF1ZXN0aW9uIHJlbGF0aW5nIHRvIFdpZmkgZnJlcXVlbmN5LsKgIEknbSBvbiB0aGUg b2xkIERlbGwNCj4+Pj4gSW5zcGlyb24gMTU0NSBsYXB0b3AuwqAgSW4gdGhlIEZpb3Mgcm91 dGVyLCBpdCBzZWVtcyB0byBoYXZlIGJvdGggMi40IA0KPj4+PiBHaHoNCj4+Pj4gYW5kIDUg R2h6LsKgIEkgc2V0IHVwIGZvciAyLjQuwqAgU2hvdWxkIEkgc3RpY2sgd2l0aCB0aGF0LCBv ciB0cnkgdGhlIDUNCj4+Pj4gR2h6IGNvbm5lY3Rpb24gYW5kLCBpZiBzbywgd2hhdCdzIHRo ZSBhZHZhbnRhZ2UgaWYgYW55P8KgIEFzIEkgc2FpZCwgSQ0KPj4+PiBoYXZlbid0IHVzZWQg b3IgY29uZmlndXJlZCBXaUZpIGluIHllYXJzLg0KPj4+Pg0KPj4+PiBUaGFua3MgaW4gYWR2 YW5jZS4NCj4+Pg0KPj4+ICUgR2h6IHdpbGwgZ2l2ZSBtdWNoIGJldHRlciB0aHJ1IHB1dCwg SSB3b3VsZCB1c2UgdGhhdCBpZiB5b3VyIGxhcHRvcCBpcw0KPj4+IGNsb3NlIHRvIHlvdXIg cm91dGVyLiAlIEdoeiBnZXRzIHByb2dyZXNzaXZlbHkgd2VhayB0aGUgbW9yZSB3YWxscyBp dA0KPj4+IG11c3QgZ28gdGhydS4NCj4+Pg0KPj4+IEFzIGZhciBhcyB5b3VyIHdpcmVkIGNv bm5lY3Rpb24gZ29zLCBkaSB5b3UgdHJ5IGEgZGlmZmVyZW50IG5ldHdvcmsgcG9ydA0KPj4+ IG9uIHlvdXIgcm91dGVyPyBZb3UgYWxzbyBtYXkgd2FudCB0byBjaGVjayB0aGUgd2lyZWQg cG9ydCBzcGVlZCBzZXR0aW5ncw0KPj4+IG9uIHlvdXIgcm91dGVyIGZvciB0aGUgcG9ydCB0 aGF0IGlzIGdpdmluZyB5b3UgdHJvdWJsZS4gSSBhbHdheXMgaGFyZA0KPj4+IGNvZGUgdGhl IHBvcnQgc3BlZWQgYW5kIGR1cGxleC4gQXV0by1uZWdvdGlhdGUgaXMga2luZGEgb2YgcGlj a3kgdGhhdCBpcw0KPj4+IHdoeSBJIGhhZCBjb2RlLg0KPj4+DQo+Pj4NCj4+Pg0KPj4NCj4+ IFllcywgSSBkaWQgdHJ5IGRpZmZlcmVudCByb3V0ZXIgcG9ydHMgYnV0IG5vIGRpZmZlcmVu Y2UuwqAgSSdtIG5vdyANCj4+IHRoaW5raW5nIHRoYXQgdGhpcyBpcyB0aGUgY2hhcmdlciBi b2FyZCBpbiB0aGUgbGFwdG9wIGFzIGl0IGNvbnRhaW5zIA0KPj4gdGhlIHBvd2VyIGphY2ss IFVTQiBwb3J0IGFuZCBldGhlcm5ldCBwb3J0LsKgIEl0IGlzIGEgc21hbGwgYm9hcmQgdGhh dCANCj4+IGNhbiBiZSByZXBsYWNlZCBhbmQgSSBoYXZlIGEgcmVwbGFjZW1lbnQgb24gdGhl IHdheS7CoCBJIGp1c3QgZ290IA0KPj4gZmluaXNoZWQgc3dhcHBpbmcgb3V0IHRoZSBkZWZ1 bmN0IG1vdGhlcmJvYXJkIGFuZCBpdCdzIHBvc3NpYmxlIHRoYXQgDQo+PiB0aGUgY2hhcmdl ciBib2FyZCBpcyBjYXVzaW5nIHRyb3VibGUuDQo+IA0KPiBUaGF0J3Mgb25lIHdlaXJkIGJv YXJkLiBUaGUgRXRoZXJuZXQgcG9ydCBjb25uZWN0b3IgbG9va3MNCj4gbGlrZSBhIHRyb3Vi bGUtbWFrZXIuIExpa2UgdGhlIHdpcmVzIGFyZSBTTVQgYW5kIHVuZGVybmVhdGgNCj4gdGhl IGNvbm5lY3RvciBib2R5Lg0KPiANCj4gaHR0cHM6Ly93d3cuZGN4cG93ZXIuY29tL2RlbGwt aW5zcGlyb24tMTU0NS0xNTQ2LXBwNDFsLTQ4NGFxMDMwMTEwMjFjMTFjMjEtNDg0YXExM2Nz Yy00ODRhcTIwMHNiLTQ4NGFxMjMwc2ItZHIxLTA4NTMwMTJzYy1kYy1wb3dlci1qYWNrLXNv Y2tldC1jb25uZWN0b3ItdmdhLXJqNDUtbGFuLXVzYi1wb3J0LWluLWNoYXJnaW5nLWJvYXJk LXAtMTk0Lmh0bWwNCj4gDQo+ICDCoMKgIFBhdWwNCj4gDQoNCkkndmUgYmVlbiBrZWVwaW5n IGF0IGxlYXN0IG9uZSAxNTQ1IGdvaW5nIGZvciBhYm91dCB0ZW4geWVhcnMgbm93LiAgSXQn cyANCmNoZWFwZXIgdGhhbiBidXlpbmcgbmV3LiAgQWx0aG91Z2ggSSd2ZSByZXBsYWNlZCBt b3RoZXJib2FyZHMgdHdpY2UsIA0KdGhpcyBpcyB0aGUgZmlyc3QgdGltZSBzaW5jZSBJJ3Zl IG93bmVkIG9uZSB0aGF0IEkgaGFkIHRyb3VibGUgd2l0aCB0aGUgDQpwb3J0LiAgSSBmb3Vu ZCBvdXQgdG9kYXkgdGhhdCBJIGNvdWxkIGhhdmUgdXNlZCBhbiBldGhlcm5ldCB0byBVU0Ig DQphZGFwdGVyLCB3aGljaCBJIGRpZG4ndCBrbm93IGFib3V0LCBidXQgdGhlIGNoYXJnZXIg Ym9hcmQgaXMgYWxyZWFkeSBvbiANCnRoZSB3YXkuICBPZiBjb3Vyc2UsIEknbGwgaGF2ZSB0 byByZXBlYXQgdGhlIGRpc2Fzc2VtYmx5IHByb2Nlc3MgbGlrZSANCkknbSBjaGFuZ2luZyBv dXQgdGhlIG1vdGhlcmJvYXJkLCBidXQsIGF0IHRoaXMgcG9pbnQsIEknbSB1c2VkIHRvIGl0 Lg0KDQpUaGUgbW9zdCBhbm5veWluZyB0aGluZyBhYm91dCB0aGUgMTU0NSB3YXMgdGhlIENN T1MgYmF0dGVyeSByZXBsYWNlbWVudC4gDQogIEp1c3QgdG8gY2hhbmdlIGl0IHJlcXVpcmVk IGFsbW9zdCBjb21wbGV0ZSBkaXNhc3NlbWJseSwgYnV0IEkgcmVtZWRpZWQgDQp0aGF0IGJ5 IHVzaW5nIGEgc21hbGwgZHJlbWVsIHRvb2wgdG8gY3V0IGEgc3F1YXJlIGludG8gdGhlIGNh c2luZyBzbyANCnRoYXQsIHdoZW4gdGhlIENQVS8gbWVtb3J5IGNvdmVyIGlzIHJlbW92ZWQs IHRoZSBiYXR0ZXJ5IGNhbiBiZSBjaGFuZ2VkIA0Kb3V0IGFzIHdlbGwgaWYgbmVlZGVkLiBU aGVyZSBpcyBubyB2aXNpYmxlIG1vZGlmaWNhdGlvbiBvbmNlIHRoZSBDUFUgDQpjb3ZlciBp cyBiYWNrIGluIHBsYWNlIGFuZCBpbmZpbml0ZWx5IG11Y2ggZWFzaWVyIGJhdHRlcnkgY2hh bmdlcyEgIE9mIA0KY291cnNlLCB0aGUgbW9kaWZpY2F0aW9uIGhhcyB0byBiZSBkb25lIHdo aWxlIHRoZSBtb3RoZXJib2FyZCBpcyBvdXQgb2YgDQp0aGUgdW5pdDsgb3RoZXJ3aXNlIHN1 cmVseSB0aGUgbWV0YWwgc2hhdmluZ3Mgd291bGQgc2hvcnQgc29tZXRoaW5nLg0K

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to wAYNE on Thu Oct 13 19:45:20 2022
    On 10/13/2022 2:39 PM, wAYNE wrote:
    On 10/12/22 9:22 AM, Paul wrote:
    On 10/11/2022 7:40 PM, wAYNE wrote:
    On 10/11/22 4:57 PM, Killadebug wrote:
    On Tue, 11 Oct 2022 12:29:13 -0400, wAYNE wrote:

    Ok, managed to get everything working again although not quite to my >>>>> satisfaction.

    Apparently, I had to go into the router and "unblock" my desktop, since >>>>> it uses a wired, and the laptop uses the WiFi.  Once that was done, now >>>>> both PCs can simultaneously connect.

    I'm not happy about having to enable WiFi on the laptop to get
    connectivity.  Any thought on why the wired no longer works would be >>>>> welcome.  As I mentioned, it seems to not work wired on either Win or >>>>> Ubuntu, whichever I boot into.  Switching out cat5 cables did not
    remedy.  Could it be a connector, motherboard, or bios issue?

    A separate question relating to Wifi frequency.  I'm on the old Dell >>>>> Inspiron 1545 laptop.  In the Fios router, it seems to have both 2.4 Ghz >>>>> and 5 Ghz.  I set up for 2.4.  Should I stick with that, or try the 5 >>>>> Ghz connection and, if so, what's the advantage if any?  As I said, I >>>>> haven't used or configured WiFi in years.

    Thanks in advance.

    % Ghz will give much better thru put, I would use that if your laptop is >>>> close to your router. % Ghz gets progressively weak the more walls it
    must go thru.

    As far as your wired connection gos, di you try a different network port >>>> on your router? You also may want to check the wired port speed settings >>>> on your router for the port that is giving you trouble. I always hard
    code the port speed and duplex. Auto-negotiate is kinda of picky that is >>>> why I had code.




    Yes, I did try different router ports but no difference.  I'm now thinking that this is the charger board in the laptop as it contains the power jack, USB port and ethernet port.  It is a small board that can be replaced and I have a replacement on
    the way.  I just got finished swapping out the defunct motherboard and it's possible that the charger board is causing trouble.

    That's one weird board. The Ethernet port connector looks
    like a trouble-maker. Like the wires are SMT and underneath
    the connector body.

    https://www.dcxpower.com/dell-inspiron-1545-1546-pp41l-484aq03011021c11c21-484aq13csc-484aq200sb-484aq230sb-dr1-0853012sc-dc-power-jack-socket-connector-vga-rj45-lan-usb-port-in-charging-board-p-194.html

        Paul


    I've been keeping at least one 1545 going for about ten years now.  It's cheaper than buying new.  Although I've replaced motherboards twice, this is the first time since I've owned one that I had trouble with the port.  I found out today that I
    could have used an ethernet to USB adapter, which I didn't know about, but the charger board is already on the way.  Of course, I'll have to repeat the disassembly process like I'm changing out the motherboard, but, at this point, I'm used to it.

    The most annoying thing about the 1545 was the CMOS battery replacement.  Just to change it required almost complete disassembly, but I remedied that by using a small dremel tool to cut a square into the casing so that, when the CPU/ memory cover is
    removed, the battery can be changed out as well if needed. There is no visible modification once the CPU cover is back in place and infinitely much easier battery changes!  Of course, the modification has to be done while the motherboard is out of the
    unit; otherwise surely the metal shavings would short something.

    There is a way to test Ethernet wiring.

    One of the Marvell NIC chips, has the ability to check the
    continuity of Ethernet wires and transformers. (The keyword is
    VCT in the documentation...)

    On this page, in the lower left corner, is a download button
    for the Marvell whitepaper on Virtual Cable Tester.

    https://www.teklib.com/library/vct-marvell-virtual-cable-tester-technology-for-gigabit-networks-white-paper/

    Name: Virtual_Cable_Tester_Marvell_WP.pdf
    Size: 743522 bytes (726 KiB)
    SHA256: 4CA96A44A49ED3EE54055F275DCB89BFEB01299338ABFF1C3B9FE5420EFDE689

    To use the tester, you do the following:

    1) PC with particular Marvel VCT NIC is powered and conducts the test.
    2) Run Ethernet cable to a second piece of equipment.
    3) The second piece of equipment is *unpowered*. This prevents
    HeartBeat activity from screwing up the pulses.
    4) Cable has a max of four pairs (i.e. GbE). The status of
    the pairs can be Short, Open, Good (characteristic termination).

    Marvell ----\||/--------------------\||/----+-------+ Conceptual
    VCT /||\ /||\ | Foreign diagram of
    1of4 pair \||/ \||/ Rterm XCVR method
    ----/||\--------------------/||\----+-------+

    I only own one of those chips, and the motherboard is dead,
    so the chip is now an orphan. But what was pretty funny in
    my mind, is when the motherboard was new, one of the first
    features I tested was VCT... and the Ethernet connector had
    dirt on one pin, and one pair measured open at zero feet :-)
    So it did not pass the test, on the very first usage.
    Just inserting and removing the connector five times,
    cleaned off the manufacturing residue. Then it passed.

    But at least it does show, that it is possible to implement
    Time Domain Reflectometry inside a NIC, for testing that
    a wire is broke somewhere. It can show you, for example,
    that a wire is broken inside a 100 foot long Ethernet cable.
    The distance to the trouble, is only a rough estimate.
    It's not as good as a real TDR instrument with 35pS
    rise time tunnel diode stimulus.

    After giving up on Ethernet, Marvell today does seem to be
    interested in NICs again. But perhaps it will be some
    time before we see a product with the Marvell name on
    the box. (A couple years ago, there were boxes with
    Marvell printed on them, you open the box, and RealTek
    was inside...) Whether they will have VCT, is another matter.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)