I have a Cisco 678 and have no problems connecting to FTP servers that use the sensible, universally accepted default port of 21. Unfortunately I have a genuine need to connect to an FTP server that inexplicably is using another port.
What *appears* to be happening is this: when my FTP client sends over the PORT command (which tells the FTP server which port he can use to connect to ME for transfers), the router obviously does not see a packet destined for port 21 and while it may still be fixing up the source address to match the routable address of the 678, it does not know to go into the FTP data itself to patch up the "return address" information contained in the FTP data.
I have seen discussions of this issue being resolved by Cisco but always in the context of their IOS rather than CBOS which runs on the 678. What they did for IOS was add support for a command that would effectively tell the router to treat some other port like it was the ftp port. This is all that I really need, but I have been unable to figure out how to do it for the 678.
Any help would be immensely appreciated,
Rob
What *appears* to be happening is this: when my FTP client sends over the PORT command (which tells the FTP server which port he can use to connect to ME for transfers), the router obviously does not see a packet destined for port 21 and while it may still be fixing up the source address to match the routable address of the 678, it does not know to go into the FTP data itself to patch up the "return address" information contained in the FTP data.
I have seen discussions of this issue being resolved by Cisco but always in the context of their IOS rather than CBOS which runs on the 678. What they did for IOS was add support for a command that would effectively tell the router to treat some other port like it was the ftp port. This is all that I really need, but I have been unable to figure out how to do it for the 678.
Any help would be immensely appreciated,
Rob