Information Technology Reference
In-Depth Information
6. On your server, open the Local Area Connection Properties dialog box, click the
File and
Printer Sharing for Microsoft Networks
check box to reenable this service, and then click
OK
.
7. On your Vista computer, try again to access
\\ServerXX
. You should see a list of shared fold-
ers and printers on ServerXX. If the folders aren't displayed immediately, close the Explorer
window and try again. It might take several attempts before the folders appear.
8. Close all open windows on Vista and your server.
Log off Vista and log back on
. You must
log off to clear any open connections with your server, which is necessary for the next steps.
If logging off Vista doesn't seem to have cleared open connections, restart
your Vista computer.
9. On your Vista computer, open the Network Connections window and then the Local Area
Connection Properties dialog box. Click to clear the
Client for Microsoft Networks
check
box, and then click
OK
.
10. Click
Start
, type
\\serverXX
in the Start Search text box, and press
Enter
. The Network
Error message should be displayed. Click
Diagnose
. Unfortunately, Windows Network
Diagnostics is unable to determine the problem. Click
Cancel
.
11. Open the Local Area Connection Properties dialog box. Click to enable the
Client for
Microsoft Networks
check box again, and then click
OK
.
12. Try again to access
\\serverXX
. You should see the list of shared folders and printers.
13. Close all open windows and log off Vista.
8
Network Bindings
By default, every installed service and protocol is bound to every
network connection. As you have seen, however, you can disable bindings on a network con-
nection. When you have multiple network adapters and, therefore, multiple network connec-
tions, you might also need to change the order in which adapters and protocols are bound to
network services. For example, you have both IPv4 and IPv6 installed and bound to a network
connection, the default configuration in Windows Server 2008 and Vista. When you attempt
to access a Windows share on another computer using Client for Microsoft Networks,
Windows sends the request by using all protocols bound to Client for Microsoft Networks.
However, Windows waits until it receives a response from the highest priority protocol before
continuing.
To see why, examine Figure 8-12. Client for Microsoft Networks has both IPv4 and IPv6
bound to it. IPv4 is listed first, so it's the highest priority protocol. Even if a response is received
from IPv6 first, Windows waits for a response from IPv4 or until it times out. For now, this is
probably what you want because IPv4 is likely your predominant protocol. Suppose your net-
work switches over to IPv6, however, and some of the servers have disabled IPv4. Everything still
works, but there might be a noticeable delay because Client for Microsoft Networks times out
waiting for a response from IPv4 before it uses the response from IPv6.
Fortunately, you can reorder protocol bindings by simply selecting the protocol whose order
you want to change and clicking the up or down arrows you see in the Adapters and Bindings
tab in Figure 8-12. Binding order applies to network connections as well. Looking at Figure 8-12
again, two Local Area Connections are configured on this computer. When a service attempts to
access a network resource or respond to a resource request, the network connections are prior-
itized in the order shown. If the connections aren't listed in the order of primary use, you should
change the order by clicking the up or down arrow.
To open the Advanced Settings dialog box for network connections, click
Advanced, Advanced Settings from the menu in the Network Connections
window. To enable the menu bar on a Vista computer, you must click
Organize on the toolbar, point to Layout, and click Menu Bar.
Search WWH ::
Custom Search