ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » could not connect to remote ''FTP'' server

Post new topic  Reply to topic
 could not connect to remote ''FTP'' server « View previous topic :: View next topic » 
Author Message
chenna.hari
PostPosted: Tue Aug 23, 2011 7:13 am    Post subject: could not connect to remote ''FTP'' server Reply with quote

Centurion

Joined: 21 Mar 2009
Posts: 103

I am getting below error while conecting one of the application FTP from Message broker. Can you please help why these errors are coming. and there port number is 34179 which i didnt give at all. it is autimatically assigne

Quote:
RecoverableException BIP3380E: File node ''FileOutput'' in message flow ''Sample_MFL'' could not connect to remote ''FTP'' server ''/xx.xx.xx.xx:34179''. Reason: ''timeout(5000)'.'
The FileInput or FileOutput node failed to open a connection to a remote server. Possible reasons for this failure are that the server could not be contacted, the initial FTP protocol was not observed, or an error situation exists at the server. The reason text is from the detected connection failure.
Ensure that:
- The server address is correct and is locally resolved to a valid IP address.
- The server port is correctly specified (the default port for FTP is 21, and for SFTP it is port 22).
- A firewall does not block access to the remote server.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Aug 23, 2011 7:20 am    Post subject: Re: could not connect to remote ''FTP'' server Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

chenna.hari wrote:
Can you please help why these errors are coming.


Because you can't get to that port. Obviously enough.

chenna.hari wrote:
there port number is 34179 which i didnt give at all.


What happens if you explicitly assign port 21?

Does your network do any nifty port shuffling (for workload balancing or other reasons) which the network people should have mentioned?

Can you do a standard ftp from a command prompt from the broker machine to the target machine?

Indeed, what have you already tried aside from posting here?

What version of WMB on what platform(s)?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
chenna.hari
PostPosted: Tue Aug 23, 2011 7:26 am    Post subject: Reply with quote

Centurion

Joined: 21 Mar 2009
Posts: 103

i have already tried with port number 21, still it is taking unknown port number

i have tried to FTP from Broker machine it is connected successffuly

ftp xxx.xx.xx.xx
Connected to xxx.xx.xx.xx.
220 (vsFTPd 2.2.2)
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Aug 23, 2011 7:36 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

chenna.hari wrote:
i have already tried with port number 21, still it is taking unknown port number

i have tried to FTP from Broker machine it is connected successffuly

ftp xxx.xx.xx.xx
Connected to xxx.xx.xx.xx.
220 (vsFTPd 2.2.2)


You see? You mention these things originally, I won't suggest things you've already tried.

So when you "tried with port number 21" you mean you hard coded it into the node parameters?

And the ftp you quote above is from the Broker machine to the same target url?

And the version of WMB is? Running on?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
chenna.hari
PostPosted: Tue Aug 23, 2011 7:38 am    Post subject: Reply with quote

Centurion

Joined: 21 Mar 2009
Posts: 103

yes..

i hardcoded the port number 21 in MB fileoutput node. like ipaddress:21

and also i have tried from Message broker server from putty, it got connected.

OS is Unix and message broker is 6.1
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Aug 23, 2011 7:42 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

chenna.hari wrote:
message broker is 6.1


Some days it's like pulling teeth - which 6.1? Are you up to date? Mr Google reports a number of fixes for the FileInput / FileOutput node in 6.1.0.9 (and of course WMBv7)
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
chenna.hari
PostPosted: Tue Aug 23, 2011 7:46 am    Post subject: Reply with quote

Centurion

Joined: 21 Mar 2009
Posts: 103

I hope its not the problem with the version

then why ftp connectivity is working for another servers?

please let me know what is the reason for the error
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Aug 23, 2011 8:09 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

FTP always opens dynamic ports.

Perhaps it's an issue with you needing to specify passive mode FTP.
Back to top
View user's profile Send private message
chenna.hari
PostPosted: Tue Aug 23, 2011 8:17 am    Post subject: Reply with quote

Centurion

Joined: 21 Mar 2009
Posts: 103

please let me know where do i need to mention passive?

is it connectionType?
Back to top
View user's profile Send private message
mapa
PostPosted: Tue Aug 23, 2011 11:03 am    Post subject: Reply with quote

Master

Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden

A quick search in the information center for the product will give you the answer...

Quote:
connectionType
The FTP data socket connection. It is either ACTIVE or PASSIVE.

_________________
Brgds, Magnus Palmér
Enfo Zystems
Back to top
View user's profile Send private message Visit poster's website
chenna.hari
PostPosted: Thu Aug 25, 2011 1:18 am    Post subject: Reply with quote

Centurion

Joined: 21 Mar 2009
Posts: 103

i tried with connectionType with Passive, but still not working

can anyone suggest on this issue?
Back to top
View user's profile Send private message
chenna.hari
PostPosted: Tue Aug 30, 2011 5:22 am    Post subject: Reply with quote

Centurion

Joined: 21 Mar 2009
Posts: 103

Please can any one help how to resolve this issue???
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Aug 30, 2011 5:25 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

You can get official help by opening a PMR or attending an IBM-provided training class.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » could not connect to remote ''FTP'' server
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.