subscribe to the RSS Feed

Saturday, February 11, 2012

.NET Framework 2.0: The data channel uses the previous IP address incorrectly when an FtpWebRequest instance in .NET Framework 2.0 uses the PASV mode on a multi-home computer

Posted by TechSupport


SUPPORT PROBLEM: The data channel uses the previous IP address incorrectly when an FtpWebRequest instance in .NET Framework 2.0 uses the PASV mode on a multi-home computer

Applications Supported:

COPYRIGHT NOTICE: (c) 2007 Microsoft Corporation. All rights reserved.

SUPPORT SOLUTION:
Consider the following scenario:
You assign multiple IP addresses on a network adapter of a muti-home computer. You specify the adapter to use an FtpWebRequest instance in the PASV mode to connect to FTP servers by using the Microsoft .NET Framework 2.0.You set the ServicePoint object in the instance to use a new IP address instead of the previous IP address of the adapter.In this scenario, the control channel of the connection uses the new IP address but the data channel of the connection uses the previous IP adapter. .This problem occurs because a method in the System.Net.FtpControlStream class does not read the value of the ServicePoint.BindIPEndPointDelegate property..Hotfix information
2, ‘resolution’);
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Prerequisites
3, ‘resolution’);
You must have the .NET Framework 2.0 Service Pack 2 (SP2) installed to apply this hotfix. Restart requirement
3, ‘resolution’);

You do not have to restart the computer after you apply the hotfix if the affected files are not being used.
Hotfix replacement information
3, ‘resolution’);

This hotfix does not replace any other hotfixes.
File information
3, ‘resolution’);

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.For all supported x86-based versions of Windows Server 2003 and of Windows XP
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformSystem.dll2.0.50727.44563,186,68801-Jun-201009:57×86For all supported x64-based versions of Windows Server 2003 and of Windows XP
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformSystem.dll2.0.50727.44563,186,68801-Jun-201009:29×64For all supported IA-64-based versions of Windows Server 2003 and of Windows XP
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformSystem.dll2.0.50727.44563,186,68801-Jun-201009:29IA-64.Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section..

For File Repair and Data Recovery, visit File Repair / Data Recovery

Add A Comment