• ipconfig discrepancies, Pro toHome.

    From micky@21:1/5 to All on Fri Jun 6 12:01:12 2025
    XPost: alt.comp.os.windows-11

    Even though this is all on win10, I've added the win11 group because I
    think the results could be the same, and because you guys all had win10
    at earlier times

    Is it normal for two computers, both connected by cable to the same
    router, and both showing the same wired-connection icon in the systray,
    to have different IPv4 and Link-local IPv6 addresses?

    Is it normal for two computers, one win10 home and one pro to display
    ipconfig results differently?
    Home starts with a duplicate copy of this, which also appears further
    down. For Pro, it only appears further down (it would take extra time
    to check but it's possible one cmd window has administrative priveleges
    and the other doesn't. Could that make a difference?:
    "Unknown adapter Local Area Connection:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : "

    Is it normal for the Home computer to have, without Link-local:
    IPv6 Address fd42:f4ce:1c43:aa2e:8201:6ef2:c89b:d14b
    But the Pro computer has no IPv6 address (except with Link-local)?

    Is it normal for the Home computer to have 2 Temporary addresses as
    follows:
    Temporary IPv6 Address . . : fd42:f4ce:1c43:aa2e:801d:c6a1:6c60:717
    Temporary IPv6 Address.. . : fd42:f4ce:1c43:aa2e:a460:b8d3:41ef:42b2
    But the Pro computer has NO temporary addresses?

    Is it normal for the win10 Home *laptop" connected by cable to lose the internet connection when it sleeps and even just when the screen goes
    black, and take up to a minute to regain it, but the win10 Pro *desktop* desktop takes only 1 or 2 seconds to regain its internet connection, as
    shown by the systray icon? Could this be related to the temporary
    addresses referred to just above?


    And related, I posted a while ago about how my laptop didn't go to sleep
    when I clicked on Windows-icon, then clicked within the Shut Down list
    on Sleep. As soon as I posted it started working correctly! By which I
    mean it can't be awakened by the external mouse and the system status
    light switches from blue to slowly blinking red or orange. But after 2
    weeks it stopped doing that, went back to not working correctly, and the
    light always remains blue and it awakens merely by moving the mouse.
    On the other hand, if it times out and goes to sleep, that is real
    sleep. But clicking on Windows/Sleep does not make it sleep!!
    That is the laptop running Home. The desktop running Pro does go to
    sleep when I click on Windows/Sleep. How do I fix the laptop?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to micky on Fri Jun 6 13:42:40 2025
    XPost: alt.comp.os.windows-11

    On Fri, 6/6/2025 12:01 PM, micky wrote:
    Even though this is all on win10, I've added the win11 group because I
    think the results could be the same, and because you guys all had win10
    at earlier times

    Is it normal for two computers, both connected by cable to the same
    router, and both showing the same wired-connection icon in the systray,
    to have different IPv4 and Link-local IPv6 addresses?

    Is it normal for two computers, one win10 home and one pro to display ipconfig results differently?
    Home starts with a duplicate copy of this, which also appears further
    down. For Pro, it only appears further down (it would take extra time
    to check but it's possible one cmd window has administrative priveleges
    and the other doesn't. Could that make a difference?:
    "Unknown adapter Local Area Connection:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : "

    Is it normal for the Home computer to have, without Link-local:
    IPv6 Address fd42:f4ce:1c43:aa2e:8201:6ef2:c89b:d14b
    But the Pro computer has no IPv6 address (except with Link-local)?

    Is it normal for the Home computer to have 2 Temporary addresses as
    follows:
    Temporary IPv6 Address . . : fd42:f4ce:1c43:aa2e:801d:c6a1:6c60:717
    Temporary IPv6 Address.. . : fd42:f4ce:1c43:aa2e:a460:b8d3:41ef:42b2
    But the Pro computer has NO temporary addresses?

    Is it normal for the win10 Home *laptop" connected by cable to lose the internet connection when it sleeps and even just when the screen goes
    black, and take up to a minute to regain it, but the win10 Pro *desktop* desktop takes only 1 or 2 seconds to regain its internet connection, as
    shown by the systray icon? Could this be related to the temporary
    addresses referred to just above?


    And related, I posted a while ago about how my laptop didn't go to sleep
    when I clicked on Windows-icon, then clicked within the Shut Down list
    on Sleep. As soon as I posted it started working correctly! By which I
    mean it can't be awakened by the external mouse and the system status
    light switches from blue to slowly blinking red or orange. But after 2
    weeks it stopped doing that, went back to not working correctly, and the light always remains blue and it awakens merely by moving the mouse.
    On the other hand, if it times out and goes to sleep, that is real
    sleep. But clicking on Windows/Sleep does not make it sleep!!
    That is the laptop running Home. The desktop running Pro does go to
    sleep when I click on Windows/Sleep. How do I fix the laptop?


    I keep hearing the theme music from "rod serling twilight zone"...

    Did one of the machines connect itself to an open Wifi ?

    *******

    rundll32.exe powrprof.dll,SetSuspendState 0,1,0

    https://learn.microsoft.com/en-us/windows/win32/api/powrprof/nf-powrprof-setsuspendstate

    BOOLEAN SetSuspendState(
    [in] BOOLEAN bHibernate, <=== 0 could mean Sleep
    [in] BOOLEAN bForce, <=== 1 force doesn't do anything
    [in] BOOLEAN bWakeupEventsDisabled <=== 0 wakeup events (mouse/keyboard) disabled
    );

    If you run that from an Administrator window, it could throw an error,
    which might be about as much info as you would get from event viewer.

    It could be that the machine is Modern Standby.

    https://answers.microsoft.com/en-us/windows/forum/all/pc-not-entering-sleep-using-rundll32exe/d4161b9c-534c-414e-8826-40736f96e2c8

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Char Jackson@21:1/5 to All on Fri Jun 6 13:45:29 2025
    XPost: alt.comp.os.windows-11

    On Fri, 06 Jun 2025 12:01:12 -0400, micky <NONONOmisc07@fmguy.com>
    wrote:

    Is it normal for two computers, both connected by cable to the same
    router, and both showing the same wired-connection icon in the systray,
    to have different IPv4 and Link-local IPv6 addresses?

    Different/unique IP addresses are normal and expected. You should be
    concerned if you discover two or more devices that have the *same*
    address, as that would cause collisions.

    <snip>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to Jackson on Fri Jun 6 15:34:45 2025
    XPost: alt.comp.os.windows-11

    In alt.comp.os.windows-10, on Fri, 06 Jun 2025 13:45:29 -0500, Char
    Jackson <none@none.invalid> wrote:

    On Fri, 06 Jun 2025 12:01:12 -0400, micky <NONONOmisc07@fmguy.com>
    wrote:

    Is it normal for two computers, both connected by cable to the same
    router, and both showing the same wired-connection icon in the systray,
    to have different IPv4 and Link-local IPv6 addresses?

    Different/unique IP addresses are normal and expected. You should be >concerned if you discover two or more devices that have the *same*
    address, as that would cause collisions.

    I'll be on the lookout for that. Thanks, to both of you.

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