File transfer always failed
hi guys just new here in forum. i have a problem on my file transfer always failed please help me how to fix this thanks a lot
6
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Pandion requires that there is no firewall or NAT between the sender and receiver of a file. The sender listens on a random (but configurable) port. The receiver then connects to that port and requests the file.
You can set up a port map and configure the public IP address in the Settings dialog of the sender. -
Inappropriate?great thanks for quick response :)
-
Inappropriate?I am too facing the same issue. :-(
Which public IP address & port map do we need to put in setting dialog ? -
Inappropriate?Let me explain it with an example. This description is for a Pandion user behind NAT trying to send a file to someone on the Internet.
Alice, using Pandion at home, has IP address 192.168.1.5 for her laptop.
Her broadband router has IP address 74.125.45.100 (example).
First, Alice logs in to her router's web interface and configures a port map of 45678/TCP to 192.168.1.5 (this can be any available port number)
Then she configures Pandion to listen for file transfers on port 45678 and enters the public IP address 74.125.45.100
Now she can send files to any Pandion user on the Internet. -
Inappropriate?pandion has been success login to openfire server, but the transfer file always failed.
I have set transportmap to my server IP and I use a same port on server setting to transfer file (e.g : 192.168.2.13:7733)
But I still have that's problem....
How about this problem ? -
Inappropriate?If you are trying to send files within the LAN then there's no need for a portmap. If you are trying to send files to Internet users then you need to type the public IP address, instead of the private 192.168.*.* address.
-
Inappropriate?I have Spark and Pandium on the same box and logged in and stll can't send files. Bet sending files between Sparks with a colleague is not a problem.
-
Pandion and Spark use different protocols for file transfer so they are not compatible on this feature. Try sending between two Pandion clients. -
Inappropriate?What does the future look like for File Transfer? Ideally, you should be able to transfer files from any XMPP client to any XMPP client and also from Pandion to say an MSN user via a transport.
I suspect part of the above isn't exactly a Pandion issue, but would be great to understand your take on it. -
Inappropriate?The solution described don ́t work for our company. We have aprox. 60 users, 20 in headquarters and the others users in various offices around Brazil. How many time to new version and transparent file transfer between Pandion clients ? We don ́t like to change the client, but Spark works fine with this function, but we preffer Pandion, for many reasons. Still wating.
Congratullations for all team of Pandion.
I’m frustrated
-
Inappropriate?I'm using 2.6.59 and can't see "file send" in Actions menu. Should i configure anything?
-
Inappropriate?It's temporary disabled until we have the new file transfer system up and running that will be compatible with all Jabber clients.
-
Inappropriate?This is great news! Dries, can you elaborate a bit on what you are planning? Will it also facilitate sending via transports to MSN, etc?
I’m excited
-
Inappropriate?We'll use Jingle compatible file transfers. I'm not sure if that will (ever) work with transports, that depends on the transport developers.
Loading Profile...




EMPLOYEE

EMPLOYEE