Properties IPV4

No need to start a new thread about this well known problem.

The Network Settings for the used NIC couldn't be changed in build 10049, MS locked those and there isn't a way around (yet). You've to use the settings given by installation for your NIC, Network Sharing is working well.

 

u can use DNS Jumper to change ur DNS, i'm using it

 

With DNS Jumper you could change the DomainNameServers to others than your ISP, BUT: not the internal IP of your NIC (NetworkInterfaceCard)! And that's the problem which many users, include myself are facing!

 

Open CMD
For Static IP, Subnet Mask, Default Gateway:
netsh interface ip set address name="Ethernet" static 192.168.1.2 255.255.255.0 192.168.1.1

For DNS Servers: here am using Google DNS, change with your own
netsh interface ipv4 add dnsservers "Ethernet" 8.8.8.8 index=1
netsh interface ipv4 add dnsservers "Ethernet" 8.8.4.4 index=2

Change "Ethernet" to your own Network Device name

 

That didn't works!

Simply, MS 'locked' the IP Settings in Build 10049, which will be open again in later builds, according to MS Support!

 

Its worked for me.

 

We're talking about the Pro version and NOT the Enterprise! That differs a bit regarding Network and it's settings.

 

any idea if this is fixed in 10051

 

Nope still locked down, Im also getting an error about not being able to access UNC Shares, Instantly pops back up and says that You don't have permisions when It worked back on 10041, tired it on 10049 and 10051 same thing

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

If you get such result, the connection to your Router/Modem are ok!

Now you need to check the destination machine you like to connect via Network.

Those machine must be connected to the same IP Range 192.168.178.x with the same Netmask and Gateway of your Main/Test Computer!

If that isn't the case, you need to 'adjust your network settings which isn't possible in Windows 10 TP build 10049,10051
and others. To solve that, you will need to change the setting in your Modem/Router and the other machines!

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Also, in your Modem/Router DHCP must be enabled. If that isn't, you'll face problems as well, special while W10TP assigns an IP for that computer you'd installed it!