A number of the problems associated with the integration of older systems with XP in a Windows 7 network are due to the fact that Microsoft has already completely redesigned and redesigned the network stacks of its Windows operating systems.
Incorrect network assignment is a common problem
Among the innovations that Microsoft introduced with Windows Vista and consistently continued in Windows 7 is the network and sharing center with the network overview in it. This is considered by many administrators and users only as a nice "graphical triad", which can hardly be used in practice. However, this graphical representation of the network architecture can sometimes provide valuable guidance when configuring a network with Windows 7 machines, such as when troubleshooting.
Change the network identifier
Why does it happen again and again that individual computers are not shown in this overview or the devices are not arranged correctly in the display? One reason why, e.g. Even a Windows Vista or Windows 7 computer does not appear in this view: This specific system may be connected to a network that has the network address of this computer in the Public Network category
Windows XP: Problems with the LLTP protocol
Of the three possible network profiles, this is the safest, but this also means that such a public profile is possibly closed off. Thus, for example, the network identification is always switched off, so that such a system can not be "seen" by other window systems.
Visibility through update
This is why it is basically easy to fix: After calling up the network and release cen- ter on the corresponding PC, a user has to click on the option "Change extended sharing settings" and can select another profile (private or workspace) or set the setting for the Change network identification to the Public Network profile.
Afterwards, the system is then also visible from the other Windows systems and appears correctly in the network overview. However, we strongly advise against making these changes to the public profile.
If this change is not subsequently withdrawn, a once activated network identifier or file / printer enable is always active when the system selects a public profile. This happens e.g. Usually by a service known as network location awareness (NLA) when the system connects to a new network.
Remote access to the home network - How it works
It can then happen that a user establishes a connection with a public WLAN, in the good faith that he is protected by the public profile. Therefore, you should always make such changes by selecting a corresponding profile. If the computer is a member of a Windows domain, this mapping is typically set by using appropriate group policies. It can not be changed by the user.
The LLTP (Link Layer Topography Discovery) protocol is one of the other innovations that the new network stack has brought to Windows systems from Windows Vista. This term can be best translated with topology detection for the link layer. This is also the protocol used in Windows Vista and Windows 7 when a user selects the Show Entire Overview entry in the Network and Share Center.
Remote Access for Admins - How it works
Most users will notice that their XP systems simply do not appear on this otherwise very clear graphic. Since this overview is created with the help of the LLTP protocol, only systems that respond to an appropriate request from this protocol will appear here. By default, XP is not equipped with this protocol.
Microsoft has released an update at the time of Windows Vista and the then current XP release with SP2. It is still available for download.
Manual installation does not provide a clean solution
This update installs a response program on XP systems, which then also appear in the overview. However, this program is only available for XP systems with SP2 - whoever tries to install it on an XP system with SP 3 (the current state for this operating system) gets the message that his operating system is on a more up-to-date level than this update , Which is why it should not be installed.
It is therefore likely that Microsoft has brought this response program as part of the Service Pack 3 with these systems, but this is not true: The XP systems with SP3 are not found in the overall overview as standard and Microsoft offers for this Systems only a hotfix, which can only be obtained by direct demand from the manufacturer's support, as can be read in the corresponding Knowledge Base article.
We have tried to manually install the update package for the SP2 release on a test system by unpacking the EXE file using the -x switch and then copying the corresponding files to the XP computer. After that, however, the overall overview on the Windows 7 systems was not to start at all. It monopolized an incompatible router with each call, as long as the appropriately prepared XP system was on the net.
The best network hard drives
According to several sources on the Internet, this behavior also occurs with the Microsoft-provided fix for the SP3 release. A workaround is to deactivate the Response for connection layer topology detection on the Windows systems in the network protocols of the interfaces. After that, the overall overview will work again - though not always with clear results like the screenshot at the bottom.
However, it is also possible to access Windows XP computers on the network using the usual release mechanisms, as shown in the screenshot below. These systems can also access the shares of a Windows 7 workgroup, provided that the rights are set appropriately. Therefore, we advise against using this workaround for the connection layer topology detection, as long as the overall overview in the network and release center is not required.
No comments:
Post a Comment