G
Gamelounge78
I added a second network adapter and an IP address to the new adapter in Windows 10 Build 2004. I now have the primary (Routable on the first adapter) and alternate IP addresses (peer-to-peer on a second network adapter). The client sometimes think that it's not on a Domain network even after it's joined.
So I used powershell to tell the alternate IP address that it is not the primary. An example of what I used:
Set-NetIPAddress -IPAddress 192.168.50.2 -SkipAsSource $true
or
Set-NetIPAddress -IPAddress 192.168.50.2 -SkipAsSource 1
When I ping 192.168.50.2, the result is returned:
Pinging 192.168.50.2 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
The network adapter is not disabled in Windows, but according to the documentation about using the -SkipAsSource 1 or $true
Indicates whether an address is a primary IP address. This parameter identifies the primary IP address for outgoing traffic in a multiple IP address scenario. If this parameter is set to True, the address is not used for outgoing traffic and is not registered in DNS.
Set-NetIPAddress (nettcpip)
My issue is that....this is not a solution to using Multiple IP Addresses in a Domain environment, but this switch disables the network adapter's communication. It should have the ability to use outgoing traffic, but not register in DNS. Is there a better solution to using multiple IP's and identifying them? Is there a way to enable the Alternate IP Address tab in a Domain environment or something similar?
Continue reading...
So I used powershell to tell the alternate IP address that it is not the primary. An example of what I used:
Set-NetIPAddress -IPAddress 192.168.50.2 -SkipAsSource $true
or
Set-NetIPAddress -IPAddress 192.168.50.2 -SkipAsSource 1
When I ping 192.168.50.2, the result is returned:
Pinging 192.168.50.2 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
The network adapter is not disabled in Windows, but according to the documentation about using the -SkipAsSource 1 or $true
Indicates whether an address is a primary IP address. This parameter identifies the primary IP address for outgoing traffic in a multiple IP address scenario. If this parameter is set to True, the address is not used for outgoing traffic and is not registered in DNS.
Set-NetIPAddress (nettcpip)
My issue is that....this is not a solution to using Multiple IP Addresses in a Domain environment, but this switch disables the network adapter's communication. It should have the ability to use outgoing traffic, but not register in DNS. Is there a better solution to using multiple IP's and identifying them? Is there a way to enable the Alternate IP Address tab in a Domain environment or something similar?
Continue reading...