Select the product you need help with
You cannot access a host that is hosting the IPv4 file share by using SMB v1 from a Windows 7-based or Windows Server 2008 R2-based DirectAccess clientArticle ID: 2444558 - View products that this article applies to. On This PageSYMPTOMSConsider the following scenario:
CAUSEWhen the latter connection (Condition B) is established to the file share server, the server compares the client IPv4 address of this connection with the former connection (Condition A). If these two connections use the same client IPv4 address, then the server disconnects the former connection (Condition A). In this case, NAT device acts as a proxy for the SMB protocol or for DirectAccess and uses the same IPv4 address from the two client connections. Therefore, the former connection (Condition A) is disconnected when the latter connection (Condition B) is established from the same NAT device. RESOLUTIONHotfix informationA supported feature that modifies the default behavior of the product is available from Microsoft. However, this feature is intended to modify only the behavior that this article describes. Apply this feature only to systems that specifically require it. This feature might receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next software update that contains this feature.If the feature is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the feature. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific feature. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the feature is available. If you do not see your language, it is because the feature is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.Registry informationImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756 To use the hotfix in this package, you must create a registry subkey. To do this, follow these steps:
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows
Restart requirementYou may have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows 7 and Windows Server 2008 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
For all supported x86-based versions of Windows 7Collapse this table
For all supported x64-based versions of Windows Server 2008 R2Collapse this table
For all supported IA-64-based versions of Windows Server 2008 R2Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about DirectAccess, visit the following Microsoft TechNet website: Introduction to DirectAccess For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://technet.microsoft.com/en-us/network/dd420463.aspx)
301673
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301673/
)
You cannot make more than one client connection over a NAT device 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Additional file informationAdditional file information for Windows Server 2008 R2 and for Windows 7Additional files for all supported x86-based versions of Windows 7Collapse this table
Additional files for all supported x64-based versions of Windows Server 2008 R2 and of Windows 7Collapse this table
Additional files for all supported IA-64-based versions of Windows Server 2008 R2Collapse this table
PropertiesArticle ID: 2444558 - Last Review: December 28, 2010 - Revision: 3.0 APPLIES TO
|
Back to the top
