Login  
Search All Forums
Dart Home | PowerTCP FTP for ActiveX | Custom Development Reply | PowerTCP FTP for ActiveX Topics | Forums   
AuthorForum: PowerTCP FTP for ActiveX
Topic: Passive FTP Problems with Win2012R2
WSampson

From: Canada
Posts: 1
Member Since: 08/05/14
posted August 5, 2014 11:20 AM

Hi,

We have been using PowerTCP FTP for years without issue. Recently we have come across a problem when used with Windows Server 2012 R2 where the server will report a problem when trying to switch to PASV mode.

Again, this works perfectly fine with Windows Server 2012 (and earlier Windows servers).

Currently we have stripped everything down to bare bones and installed a test server with no firewall and on our local subnet (to remove proxies etc. from the equation). The error always boils down to "Client IP on the control channel didn't match the client IP on the data channel."

(IPs and names changed to protect the innocent)

Sample Problem log (Win2012R2 server)
date time c-ip c-port cs-username cs-host s-ip s-port cs-method cs-uri-stem sc-status sc-win32-status sc-substatus sc-bytes cs-bytes time-taken x-session x-fullpath x-debug
2014-08-05 14:56:06 10.0.0.79 56333 - - FTP-TEST - 10.0.0.206 21 ControlChannelOpened - - 0 0 0 0 0 6521be6a-16da-4c1b-bbf0-073b827d2726 - -
2014-08-05 14:56:10 10.0.0.79 56333 - FTPSVC2 FTP-TEST - 10.0.0.206 21 USER ftptest 331 0 0 23 14 0 6521be6a-16da-4c1b-bbf0-073b827d2726 - -
2014-08-05 14:56:12 10.0.0.79 56333 FTP-TEST\FTPTEST FTPSVC2 FTP-TEST - 10.0.0.206 21 PASS *** 230 0 0 21 17 0 6521be6a-16da-4c1b-bbf0-073b827d2726 / -
2014-08-05 14:56:21 10.0.0.79 56333 FTP-TEST\FTPTEST FTPSVC2 FTP-TEST - 10.0.0.206 21 PASV - 227 0 0 52 6 0 6521be6a-16da-4c1b-bbf0-073b827d2726 - -
2014-08-05 14:56:23 - - FTP-TEST\FTPTEST FTPSVC2 FTP-TEST - 10.0.0.206 51641 DataChannelClosed - - 1223 0 0 0 0 6521be6a-16da-4c1b-bbf0-073b827d2726 - -
2014-08-05 14:56:23 10.0.0.79 56333 FTP-TEST\FTPTEST FTPSVC2 FTP-TEST - 10.0.0.206 21 PORT 10,0,0,79,220,24 200 0 0 30 26 0 6521be6a-16da-4c1b-bbf0-073b827d2726 - -
2014-08-05 14:56:23 10.0.0.79 56333 FTP-TEST\FTPTEST FTPSVC2 FTP-TEST - 10.0.0.206 21 NLST - 425 1236 38 75 6 0 6521be6a-16da-4c1b-bbf0-073b827d2726 / Client+IP+on+the+control+channel+didn't+match+the+client+IP+on+the+data+channel.
2014-08-05 14:56:29 10.0.0.79 56333 FTP-TEST\FTPTEST FTPSVC2 FTP-TEST - 10.0.0.206 21 QUIT - 221 0 0 14 6 0 6521be6a-16da-4c1b-bbf0-073b827d2726 - -
2014-08-05 14:56:29 10.0.0.79 56333 FTP-TEST\FTPTEST FTPSVC2 FTP-TEST - 10.0.0.206 21 ControlChannelClosed - - 0 0 242 75 23125 6521be6a-16da-4c1b-bbf0-073b827d2726 - -

Sample Working Log (Win2012 server)
date time c-ip cs-username s-ip s-port cs-method cs-uri-stem sc-status sc-win32-status sc-substatus x-session x-fullpath
2014-07-30 13:05:19 172.16.0.3 - 10.0.0.2 21 ControlChannelOpened - - 0 0 23440674-17d7-4d63-903a-099608146d67 -
2014-07-30 13:05:19 172.16.0.3 - 10.0.0.2 21 USER WokringLogin 331 0 0 23440674-17d7-4d63-903a-099608146d67 -
2014-07-30 13:05:20 172.16.0.3 FTPSERVER\WokringLogin 10.0.0.25 21 PASS *** 230 0 0 23440674-17d7-4d63-903a-099608146d67 /
2014-07-30 13:05:20 172.16.0.3 FTPSERVER\WokringLogin 10.0.0.25 21 PASV - 227 0 0 23440674-17d7-4d63-903a-099608146d67 -
2014-07-30 13:05:20 172.16.0.3 FTPSERVER\WokringLogin 10.0.0.25 59864 DataChannelOpened - - 0 0 23440674-17d7-4d63-903a-099608146d67 -
2014-07-30 13:05:20 172.16.0.3 FTPSERVER\WokringLogin 10.0.0.25 59864 DataChannelClosed - - 0 0 23440674-17d7-4d63-903a-099608146d67 -
2014-07-30 13:05:20 172.16.0.3 FTPSERVER\WokringLogin 10.0.0.25 21 LIST SYNC.ON 226 0 0 23440674-17d7-4d63-903a-099608146d67 /SYNC.ON
2014-07-30 13:05:20 172.16.0.3 FTPSERVER\WokringLogin 10.0.0.25 21 QUIT - 221 0 0 23440674-17d7-4d63-903a-099608146d67 -
2014-07-30 13:05:20 172.16.0.3 FTPSERVER\WokringLogin 10.0.0.25 21 ControlChannelClosed - - 0 0 23440674-17d7-4d63-903a-099608146d67 -


The error always boils down to "Client IP on the control channel didn't match the client IP on the data channel." In fact, if we disable the dataChannelSecurity items on the server, it will work, but that just doesn't seem trustworthy in the long run.

Almost every other FTP client we have tried does not trigger this problem with the server. The exception being the command line Windows FTP client.

At this point we are not really sure what else to do. The control works everywhere else we've tried and I can't find any problems specific to Windows 2012 R2. We have tried with a test jig using the latest version available through the trial, and it has the same behaviour.

Any suggestions?

thanks.
Jamie Powell (Admin)

From: Rome, NY USA
Posts: 380
Member Since: 03/13/07

Extra Support Options
Custom Application Development

posted August 7, 2014 2:27 PM

Thank you for your post. An email has been sent regarding your support options. If you have not received this email please contact me at jamie.powell@dart.com and I will be happy to resend, or you may call 315.790.5456 ext 124 to speak with me directly.

Thank you again for your post.

Best regards,
Jamie Powell
Reply | PowerTCP FTP for ActiveX Topics | Forums   
This site is powered by PowerTCP WebServer Tool PowerTCP WebServer for ActiveX