Windows 10: IPEnableRouter

Hi. Trying to add IPEnableRouter as a 1 in the registry editor in windows 11, but when we do a reeboot on the pc, it disappears from the registry. When asking for ipconfig /all, it is still disabled. Do you have any tips on how to solve this in windows11 pro? Has worked fine on windows 10 before

:)

 

How to enable WINS Proxy and IP Routing in Windows 10

Neither WINS Proxy or IP Routing are enabled in Windows 10 on my laptop, which I found out by opening a black screen using "cmd" prompt in the "run" box and typing in "ipconfig /all". Here I could see that both the WINS Proxy and IP Routing are not
enabled on my laptop. Looking for a solution with the help of a google search I was led to the Registry Editor. To enable the IP Routing I found the following thread: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Netbt\Parameters, where I found IPEnableRouter
and proceeded to modify it by giving it a value of "1".

To enable the WINS Proxy I went to the same Registry thread, hoping to follow this instruction: "Right-click the \"EnableProxy\" key and select \"Modify.\" In the popup box, enter \"1\" and click the \"Ok\" button."
However, there is no "EnableProxy" key listed under Parameters on the right side of the Editor so now I'm confused.

If any of this makes any sense to anyone, I would greatly appreciate help on how to enable the WINS Proxy. Without it I am having some trouble getting some things to work. Thank you!

<Moved from: Windows / Windows 10 / Performance & system failures>

 

Windows 10 IP Forwarding

I am trying to provide Windows 10 with router capabilities(IP Forward). Yes I know I could buy a router or switch. This setup is for TESTING only.

Found a good resource: GG9BET สล็อตเว็บตรงอันดับ 1 แหล่งรวมเกมสล็อต แจกเครดิตฟรี

However after setting everything up, I still cannot get to the internet from LAN2(USB). LAN1 can get to internet. My setup:

• Computer 1
  
  • Lan1 (main connection, can access Internet)
    
    
  • Lan2 (USB NIC)
    
    
• Computer 2
  
  • Lan1 (Connected to Lan2 of Computer1)
    
    

In regedit I have enabled IPEnableRouter. I rebooted my computer.

• I can ping Lan1-Computer2 192.168.140.48 from Lan2-Computer 1 192.168.140.47
  
• I can ping Lan2-Computer1 192.168.140.47 from Lan2-Computer2 192.168.140.46
  
• I can ping LAN1-Computer1 192.168.130.47
  

So LAN1 can contact LAN2 vice versa but not the internet (which gateway is 192.168.130.1)

Any help please?

 

Providing Network Access to a Windows 10 Pro Guest Under Hyper-V Using an Internal Virtual Switch

I am running Windows 10 Pro 1903 on a physical machine. On that machine, I am running Hyper-V. I have a Windows 10 Pro 1903 guest running under Hyper-V.

I would like the guest to have network access beyond the host (i.e. access to my LAN and to the Internet). This should be possible in three ways:

1. The Hyper-V NAT-based default virtual switch
   
2. A Hyper-V external switch
   
3. A Hyper-V internal switch
   

Hyper-V NAT-Based Default Virtual Switch

The usual way to provide network access to a guest is to bind the guest's NIC to the Hyper-V default switch. This gives network access via NAT.

I prefer to not do this for two reasons:

1. When I perform network captures at various places in my network, traffic from the host and traffic from the guest are indistinguishable since all guest traffic gets NATed to have a source IP equal to that of the host.
   
2. Connections to the guest cannot be made without getting into port forwarding configuration via PowerShell.
   

Hyper-V External Virtual Switch

Network access can be provided by binding the guest's NIC to a Hyper-V external switch. This will put the guest directly on the physical LAN.

This solution works only if the host has a wired Ethernet connection. It does not work if the host's network connectivity is via Wi-Fi. Hence, this is not an option for me.

Hyper-V Internal Virtual Switch

It seems that one should be able to provide network access to a guest using these steps:

1. Binding the guest's NIC to a Hyper-V internal virtual switch that is shared with the host
   
2. Designating the host as the guest's default gateway
   
3. Enabling IP forwarding on the host
   

I have set up this configuration but have been unable to get it to work.

Unsure if IP Forwarding is Properly Enabled

To enable IP forwarding on the host, I made this registry setting:

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\IPEnableRouter
  
• REG_DWORD
  
• 1
  

I also enabled the Routing and Remote Access service.

My experience on Windows 7 and earlier was that only the registry modification was necessary. For Windows 10, I've seen many references that one must also enable Routing and Remote Access. I am unsure what the proper way to enable IP forwarding in Windows 10 is since I haven't seen it work with either the registry modification or the enabling of Routing and Remote Access, alone or in combination.

Firewall on Host

I have added / enabled both inbound and outbound firewall rules on the host that explicitly allow all traffic from the guest.

I had already tried disabling the firewall on the host and found no difference in behavior. So, I did not expect this to make a difference, and indeed it did not.

Request for Help

Is anybody able to see where I may be going wrong in attempting to provide network access to the guest via a Hyper-V internal switch?

If additional information is needed, I will be glad to provide it.

Thank you in advance for any assistance provided.