On 5/8/2019 10:24 AM, Gene Heskett wrote: > On Wednesday 08 May 2019 03:49:34 am Joe wrote: > >> On Tue, 7 May 2019 18:47:50 -0400 >> >> Gene Heskett <[email protected]> wrote: >>> Greetings all; >>> >>> First it doesn't have a clue what to do with a wired network. >>> It sure wants to hook up to all the neighborhoods wifi, all of which >>> are secured. >>> Second, its like stretch seems locked to ipv6 but its ipv4 for at >>> least a hundred miles in any direction from my 10-20 in North >>> Central WV. >>> >>> Third, I can't find a place to enter a netmask route or gateway, its >>> been sleeping with dhcp for way too long. >>> >>> I finally find what sort of looks like the old xp network >>> configurator but it error beeps at me to the entry of any address on >>> my local net that isn't already taken. >>> >>> So how do I convince this brand new unibody HP to use a static wired >>> network setup? >>> >>> In the FWIW category, it takes winders 10 about 10x longer to boot >>> than any of my linux machines. Makes me wonder if they should have >>> named it window-0.1 because it is boringly slow. >> >> Shouldn't. I have a W10 netbook, though I'm not familiar with it, it >> had Debian installed within a week. Boot (from definitely off) is less >> than thirty seconds. Booting should not be held up by network issues. >> >> Open up the properties of the Ethernet adaptor, select TCP/IPv4, >> Properties, then untick the automatic options. You should be able to >> enter values in the address, mask and gateway boxes, and specify DNS >> servers below. It shouldn't need a reboot. > > There is no place in that sequence to select TCP/IPv4 on this machine. > If ipv6 dhcp fails, you are apparently screwed. And they call this an > OS? Not where (and when) I went to school. >
Why not trying command line (netsh)? -- John Doe
