Mahmmoud Mahdi

Boston File Sharing -> On Network Discovery -> Off IPv4 -> 192.168.0.1/24 IPv6 -> ffd00::1

Boston

Dcsrv1 File Sharing -> On Network Discovery -> Off IPv4 -> 192.168.0.2/24 IPv6 -> ffd00::2

Dcsrv1

Open the properties of Local Area Connection Double-click Internet Protocol Version 4 (TCP/IPv4). In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click the Advanced button, and then click the WINS tab in the Advanced TCP/IP Setting dialog box. In the NetBIOS Setting area

Enable: select Default, and then click OK. This option enables NetBIOS unless a DHCP server disabled it. Disable: select Disable NetBIOS Over TCP/IP, and then click OK.

Click OK to close the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, and then click OK to close the Local Area Connection Properties dialog. Restart the computer.

In Network Connections, open the properties of Local Area Connection. In the Local Area Connection Properties dialog box
Enable: select the Internet Protocol Version 6

(TCP/IPv6) check box. Disable: clear the Internet Protocol Version 6 (TCP/IPv6) check box.

Restart the computer.

1. 2.
3.

4.

5.

Open Network And Sharing Center. In the Sharing and Discovery area, click the Off button next to Network Discovery Select Turn On Network Discovery, and then click Apply. A Network Discovery message appears, asking whether you want to turn on Network Discovery for all Public networks. Click Yes, Turn On Network Discovery for all Public Networks. Note that this option is only recommended for test environments. Restart the computer.

Explore the name resolution mechanisms that are available in windows networks before a DNS server is installed and configured. Attempt to connect to a computer in three ways:
Ping
UNC path (network path to a remote computer) Network windows

Boston
NetBIOS -> Disable IPv6

Dcsrv1
NetBIOS -> Disable IPv6

-> Disable Network Discovery-> Off

-> Disable Network Discovery-> Off

Boston >Ping Dcsrv1

Dcsrv1

The Ping request could not find the host

Note: without NetBIOS, Boston has no way to the name dcsrv1 on IPv4 only network for which DNS has not been configured.

Boston
Ping 192.168.0.1

Dcsrv1

You receive a response from 192.168.0.1

Note: you can determine that connectivity is established between the two computers; the problem is name resolution only.

Boston \\dcsrv1

Dcsrv1

Windows cannot access \\dcsrv1

Note: A Network Error message appears, indicating that Windows cannot access \\dcsrv1.

Boston \\192.168.0.1

Dcsrv1

A connection is established

Note: A n open window, displaying the shared folders on

Dcsrv1. At this time only the printers folder is shared.

Boston Network

Note: The Network displays no computers. In the window, a yellow band displays a message indicating that Network Discovery is turned off.

Boston
NetBIOS -> Disable IPv6

Dcsrv1
NetBIOS -> Disable IPv6

-> Enable Network Discovery-> Off

-> Enable Network Discovery-> Off

Boston Ping Dcsrv1

Dcsrv1

The Ping request could not find the host

Note: IPv6 by itself does not facilitate name resolution.

Boston Ping fd00::1

Dcsrv1

A connection is established

Note: you receive a response, indicating that you can now

ping Dcsrv1 by its IPv6 address in addition to its IPv4 address.

Boston \\dcsrv1

Dcsrv1

Windows cannot access \\dcsrv1

Note: A Network Error message appears, indicating that Windows cannot access \\dcsrv1. By itself, IPv6 does not enable you to use a UNC path connect to a computer specified by name.

Boston \\fd00-1.ipv6-leteral.net

Dcsrv1

A connection is established

Note: The fd00-1.ipv6-literal.net window opens, displaying the

Printers Share on Dcsrv1. This is the syntax you must use to connect a computer by specifying its IPv6 address in UNC path.
Notice that in the IPv6 UNC path you replace each of the colons in the original IPv6 address with a hyphen and append the suffix .ipv6-literal.net to address.

Boston Network

Note: The Network still displays no computers.

Boston
NetBIOS -> Enable IPv6

Dcsrv1
NetBIOS -> Enable IPv6

-> Disable Network Discovery-> Off

-> Disable Network Discovery-> Off

Boston Ping Dcsrv1

Dcsrv1

You receive a reply from the IPv4 address of 192.168.0.1.

Note: This response demonstrates that NetBIOS resolves computer names in an IPv4-only subnet without a DNS server.

Boston \\dcsrv1

Dcsrv1

A connection is established

Note: The dcsrv1 window opens, displaying the Printers share on Dcsrv1. We can determine from this step that NetBIOS resolves local computer names specified in a UNC.

Boston Network

Note: The Network window is still empty. In Windows server 2008 networks, NetBIOS is not used to display computers in the Network window.

Boston
NetBIOS -> Enable IPv6

Dcsrv1
NetBIOS -> Enable IPv6

-> Enable Network Discovery-> Off

-> Enable Network Discovery-> Off

Boston Ping Dcsrv1

Dcsrv1

You receive a response

Note: Notice that with NetBIOS enabled and the Network Discovery disabled, the response is from the IPv4 address of Dcsrv1, even though both IPv4 and IPv6 are enabled.

Boston Network

Note: The Network window is still empty. We do not need to check for UNC path connectivity because we know this will work when NetBIOS is enabled. Adding a protocol or a service (In this case IPv6) never removes name resolution functionality.

Boston
NetBIOS -> Disable IPv6

Dcsrv1
NetBIOS -> Disable IPv6

-> Disable Network Discovery-> On

-> Disable Network Discovery-> On

Boston Ping Dcsrv1

Dcsrv1

The Ping request could not find the host

Note: you receive a message indicating that the ping request could not find the host. In an IPv4-only network, you need NetBIOS to be able to ping a computer by a name. Network Discovery does not provide this functionality.

Boston \\dcsrv1

Dcsrv1

Windows cannot access \\dcsrv1

Note: In an IPv4-only network, you cannot connect to a computer by specifying its name in a UNC pathname unless NetBIOS is enabled. Network Discovery does not enable this functionality in IPv4 networks.

Boston Network

Boston

Dcsrv1

Note: The Network window displays either Boston, or Dscrve1, or both. Both will eventually appear if you refresh the screen. Network Discovery is the feature that populates the Network window in IPv4.

Boston
NetBIOS -> Enable IPv6

Dcsrv1
NetBIOS -> Enable IPv6

-> Disable Network Discovery-> On

-> Disable Network Discovery -> On

Boston Network
Dcsrv1

Note: when Dcsrv1 appears in the Network window, doubleclick its icon.
The Dcsrv1 window opens, displaying the Printers share on Dcsrv1.

Boston
NetBIOS -> Disable IPv6

Dcsrv1
NetBIOS -> Disable IPv6

-> Enable Network Discovery-> On

-> Enable Network Discovery -> On

Boston Ping Dcsrv1

Dcsrv1

You receive a response

Note: you receive a response from the link-local IPv6 address on Dcsrv1.
As this step shows, Network Discovery provides name resolution services for IPv6 that it does not provide for IPv4. In an IPv4 network, you need to have NetBIOS enabled to ping a computer by name.

Boston \\dcsrv1

Dcsrv1

You receive a response

Note: Again this procedure shows that Network Discovery provides services for IPv6 that it does not provide for IPv4. In an IPv4 network, you need NetBIOS to connect to another computer by specifying its name in a UNC. In an IPv6-only network, you need Network Discovery to perform this same task.

Boston Network
Dcsrv1

Note: when Dcsrv1 appears in the Network window, doubleclick its icon.
The Dcsrv1 window opens, displaying the Printers share on Dcsrv1.

Boston
NetBIOS -> Enable IPv6

Dcsrv1
NetBIOS -> Enable IPv6

->Enable Network Discovery ->On

->Enable Network Discovery -> On

Boston Ping Dcsrv1

Dcsrv1

You receive a response

Note: you receive a response from the link-local IPv6 address on Dcsrv1. Note that when IPv6, IPv4, Network Discovery, and NetBIOS are all enabled in a subnet without DNS, LLMNR is used to resolve names, and it does so by first resolving the name to an IPv4 address.

Contact Me: qursaan@gmail.com