Jump to content

TubeMan

  • Content Count

    396
  • Joined

  • Last visited

About TubeMan

  • Rank
    MS SRV

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. when you set static ip. by netsh, windows clear all ip settings that's why you need to set GW and DNS
  2. Why !!!! Don't you know why, then start som basic IP lerning GW = default route DNS = to resolv ip to host or Host to IP
  3. correct way is found in general 2019/2016 thread
  4. "FelipeRolim Well, my computers use Windows Server in Core mode, with no GUI. All I do is by command line. I leave, to facilitate, remote access enabled, so that I can command the two computers through the notebook (mstsc.exe). When the computer has the IP set as fixed (task for which use the command netsh interface ipv4 set address name ="Ethernet" source=static addr=192.169.0.1 mask=255.255.255.252), there's no internet access. And, as the Audiophile Optimizer only needs internet at the time of installation and configuration (and this only in the Beta version), when I use it, just activate DHCP again, through the command netsh interface ipv4 set address name="Ethernet" dhcp. I then connect the computer to the router. To revert, just fix the IP again and you're done. I find it simple and, for my case, fully functional. For a user of a JCAT network card (which has two possible connections), this isn't even necessary. Just swap the network port. " when you set staic IP you neeed to set GW and DNS also, same as you do in Sconfig !! netsh interface ip set address name="Ethernet" static 192.168.0.1 255.255.255.0 (GW) 192.160.0.x netsh interface ipv4 add dnsserver "Ethernet" address=xxx.xxx.xxx.xxx
  5. importent https://support.micr...pdate-kb4489899 Applies to: Windows 10, version 1809Windows Server 2019, all versions After installing this update on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the “Default Audio Device”. Examples of applications that may stop working include:
  6. " Yep - I have been doing similar to that for a few years now since AO 1.0... it has been an irritating feature since way back then also 🙂 " And I have used it since Windows NT 3.1 way back in time (if some one here knows what NT 3.1 is )
  7. "shutdown -s -t 0" = shutdown computer "shutdown -r -t 0" = restart computer
  8. https://support.micr...pdate-kb4489899 Applies to: Windows 10, version 1809Windows Server 2019, all versions After installing this update on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the “Default Audio Device”. Examples of applications that may stop working include:
  9. " I am not seeing the "cmd/command" as a choice in the ST. " will probably be added in next beta of AO
  10. as cmd is default shell in core mode, Right choice is to select default shell to get cmd prompt in core, "What am I seeing here? Can anybody explain this for me please? " This is a bug that happens if you start explorer.exe twice on on each other, when Server core addon FOD is installed
  11. "More surprising thing is it seems one can switch modes in 2019, not? " NO It's not possible
×
×
  • Create New...