Ricoh Printers going offline on Windows 2003 server

[Captain Scott]

Hi all,

I have a large customer that has recently had issues whereby all there printers (MP4000, MP3350, MPC3000, AF 3245) are going offline on there Windows 2003 server using the TCP/IP port, the customer has changed the port to LPR port and all is o.k except for slow printing (unix services for printing). They want to use TCP/IP. When eg I go to the ports section for the PCL6 or PS and change it from LPR back to the TCP/IP port it will take about 60 secs before the printer will go offline on the server. I have tried adjusting the TCP/IP port by clicking change and selecting LPR with LP as the queue name and I get the same result. The only way to recover is to restart the spooler. The machines have been working fine for a long time and the IT can't think of any major changes that would of caused this... I have checked firmware and updated still no go...Ideas Please!!

[Captain Scott]

SNMP!!

I found the below info on the net, will give it a go and report back.


"We finally upgraded our print servers to SP2 and had a problem. I banged my head with it for about one hour and thought it would be worth reporting the solution since it's a potential problem for others:

Symptomes: Some network printers published by a Windows 2003 SP2 server will be marked as "offline" and cease to be available. Restarting the spooler will make the printers briefly available (for 30 seconds or so) before they reset to offline status.

Problem: MS has changed the way SNMP-enabled printer are handeled in SP2. I don't have the full detail, but apparently any printer that is marked as SNMP enabled (by the driver, I assume) will REQUIRE (by default) SNMP to be setup correctly and working on both the printer and local server (community names). Never mind if these printer all have SNMP actually disabled.

Solution: On the properties of each printer (on the server), select the "port" tab, local the correct port, click on "configure" and uncheck "SNMP enabled". Once you click "ok" the printer's status will be instantly turned back to normal.'

[Vulkor]

Good to know, thanks!

[TheOwl]

Windows in general has a problem with SNMP Status reporting and has never really worked well.

Lets say for instance you have SNMP Status enabled in the printer port, but have it disabled on the copier. Windows will freak out because the copier isn't reporting back.

If both have SNMP status enabled, then it will work to some fashion, but I don't think that Windows can cope with the varied responses that a copier can report back. If you have one tray that is out of paper, Windows reports 'No paper' in the machine and stalls the print queue.

At the end of the day, most digital machines have their own print server in built to deal with printing. Turn SNMP off on the printer port for everything and let the copier handle itself if there is an error.

[KenB]

Just a quick note on the Ricoh line.

As I recall, the RPCS driver requires SNMP to be functioning. If it is not, stapling and other features don't work.

Of course, RPCS is a really bad idea on a server install; I normally only use it when workstations are printing directly.

I also had an account where SNMP (Port 161) was turned off at the switch, causing RPCS issues.

Lastly, Smart Device Monitor (both Client and Workstation versions) require SNMP to do their thing.

[Captain Scott]

SNMP settings

Hi all,

I visited the site, client IT had set an IP address of their server in the SNMP setting area are of all their MFP's. When I removed the IP Address of the server all started to work again. seems a touch overkill on security side.. but all works again so happy.

Thanks for your help and input..