Firmware Update via Ftp for Ricoh MP2027

[peterxu256]

Ask for clue for FTP command "Put", very puzzling for remote firmware update as per PUB(c)-059. When input 'put' command as "ftp>put xxxxxxx.rru
200 PORT command successful
150 Opening Binary mode data connection for 'xxxxxx.rru'

However the machine of MP2027 starting to print out garbage characters page by page , looked like acting as Print Command.
Where to correct cmd configuration.

[slimslob]

Re: Firmware Update via Ftp for Ricoh MP2027

Ask for clue for FTP command "Put", very puzzling for remote firmware update as per PUB(c)-059. When input 'put' command as "ftp>put xxxxxxx.rru
200 PORT command successful
150 Opening Binary mode data connection for 'xxxxxx.rru'

However the machine of MP2027 starting to print out garbage characters page by page , looked like acting as Print Command.
Where to correct cmd configuration.

Ricoh .rru firmware is not a binary file and cannot be used with the put command. Binary files have a .bin extension. Changing the extension will not change the file type and may result in a non functional machine, i.e. you would need to do major board replacements to made it operate. Binary files were used with the older machines that did not have SD card slots and used the PCMCIA cards for updates.

[peterxu256]

Re: Firmware Update via Ftp for Ricoh MP2027

If you close the ftp ports, the following services cannot be used:
- recieveing print jobs from ftp clients
- recieving firmware files from remote clients
Binary to ASCII

[KenB]

Re: Firmware Update via Ftp for Ricoh MP2027

Actually, you can use FTP with the .rfu files...it works well.

We did a bunch of MP201s that way a few years back.

However, the MP2027 is too old to have .rfu files; it can only be flashed with a PCMCIA memory card. Ick. (I just checked TSRC.)

[peterxu256]

Re: Firmware Update via Ftp for Ricoh MP2027

Actually, you can use FTP with the .rfu files...it works well.

We did a bunch of MP201s that way a few years back.

However, the MP2027 is too old to have .rfu files; it can only be flashed with a PCMCIA memory card. Ick. (I just checked TSRC.)

THANKS, BUT THE pub(059)-059, did, mention the model B089/B093(MFP-mp2027) OK and OK FOR ALL!, However forget about the error or not. it is quite associated with ftp command category (scope of computer network knowledge), I disabled most functions under TCP/IP, like IPP, LPR RSH/RCP, DIPPIN EXPECT FROM ftp, but FTP "put" command still acting a printing command to print out pages. EVEN IF the machine ftp server don't give the permission of "write" (writing a firmware file), it should return a deny operation message. Now the question is how to disable the RAW protocol of these printing protocols(like IPP, LPR-Line Printer Remote), Web Image Monitor doesn't list RAW- port 9100, at least disable the port to try.

Yes like MP201 or other models MP2000/MP2500 etc, I tested many times, it works fine. Recently PCMCIA adapter(from Texas Instrument ) can not be accessed from HP laptop, heard the sound and checked mass storage driver( PCI-8x12/7x12/6x12 cardbus controller) installed properly. No clue to work out.

[C.Vallon]

Re: Firmware Update via Ftp for Ricoh MP2027

If its printing "Garbage text", sounds like your sending a file to the mfp in a language it doesn't understand (java, post script, ext ext), that would cause it to print page after page of odd characters and text.

Your trying to install firmware update via remote? Maybe alter update methods if possible? I believe you can send the file directly to the MFP if you can connect to it from your laptop, copy the firmware, select the MFP under it's IP address and paste it there. I'll have to look at my notes, I recall covering this a few weeks back while attending a Ricoh class in Costa Mesa.

[KenB]

Re: Firmware Update via Ftp for Ricoh MP2027

I stand corrected, my apologies.

I checked the tech pub and TSRC. There were indeed rfu files for this model, at least from what I saw.

Are you enabling the binary transfer mode in your FTP session? If you don't, the file will most likely get corrupted, and I can see the machine trying to print it instead.

The .rru file extension is a valid one for remote firmware, as well as .rfu. I just don't remember the last time I saw one.

The tech pub seems to spell out the procedure quite clearly. You may want to download a fresh copy of the firmware, in case it got corrupted somehow the first time.

[peterxu256]

Re: Firmware Update via Ftp for Ricoh MP2027

I stand corrected, my apologies.

I checked the tech pub and TSRC. There were indeed rfu files for this model, at least from what I saw.

Are you enabling the binary transfer mode in your FTP session? If you don't, the file will most likely get corrupted, and I can see the machine trying to print it instead.

The .rru file extension is a valid one for remote firmware, as well as .rfu. I just don't remember the last time I saw one.

The tech pub seems to spell out the procedure quite clearly. You may want to download a fresh copy of the firmware, in case it got corrupted somehow the first time.

Yes, enabling binary transfer mode, further, set ON on SP5856 remote ROM update. But it still acted a printer command, I don't need printing, I want to write a file on machine. Issues resulted from some configuration of ftp command

[KenB]

Re: Firmware Update via Ftp for Ricoh MP2027

Perhaps try an FTP client, like Filezilla, instead of using the command prompt.

It's free, and worth a try.

[peterxu256]

Re: Firmware Update via Ftp for Ricoh MP2027

Perhaps try an FTP client, like Filezilla, instead of using the command prompt.

It's free, and worth a try.

Thanks, very good suggestion. Tested with Filezilla client, and got some USEFUL error messages,: Error: Server Returned empty path. failed to retrieve directly listing, Server doesn't support non-ASCII characters....

Therefore using Zenmap to scan ports, there are only 8 ports OPEN, there is only One port number is above 1024, that is, 9100 Jetdirect.

屏幕截图 2015-05-01 17.12.10.jpg

In active mode, the client connects from a random port (1024 or higher) to the server's command port (21). Then, the client starts listening on random port + 1 and informs the server to send communications to random port +1 (PORT command). The server will then initiate a connection to random port + 1 from its local data port (20).
So for example, if the client is sending data from port 1234 (random port) to port 21 on the server, the client will recieve data on port 1235 (random port + 1) from the server's port 20.