PDA

View Full Version : SNMP Port 161 & 162 enabled, but not open



Thorsten Kuhla
02-10-2010, 04:08 AM
Hi,

we have trouble to open the snmp Port 161&162 on Canon Fiery Controllers, mainly A - series & J100/200.The Ports are shown enabled on the config page, but definetly not open (checked by portscanner!).
Any tipp is welcome !

Karl_T
02-11-2010, 05:49 PM
Hello,

Are you unable to connect to this Fiery using any of the utilities - such as Command Workstation?

By default, these ports are open unless they are disabled in setup under Network Setup/Protocol Setup/TCP IP setup. Of course, the correct state should show up on the configuration page, unless the system software has somehow become corrupted.

Please also indicate which port scanning software you used to test this and whether you ran the port scanner on the Fiery or on a client PC.

Many Thanks,


Karl

Thorsten Kuhla
02-19-2010, 02:48 AM
Hi Karl,

many thanks for your reply!

I use "advanced Portscanner 1.1" its a freeware tool, but works perfectly!
I have the same issues with Canon Q2, GX300 Fierys. The ports were open since 31.12.2009, in the beginning of this year they were suddenly closed. Sounds incredible, but so it is. We need these Ports to be open, cause a 3rd party software needs them to get the device status of our printsystem.

Best regards

Thorsten


Hello,

Are you unable to connect to this Fiery using any of the utilities - such as Command Workstation?

By default, these ports are open unless they are disabled in setup under Network Setup/Protocol Setup/TCP IP setup. Of course, the correct state should show up on the configuration page, unless the system software has somehow become corrupted.

Please also indicate which port scanning software you used to test this and whether you ran the port scanner on the Fiery or on a client PC.

Many Thanks,


Karl

Karl_T
03-05-2010, 01:01 PM
Hi Thorsten,

Thanks for that info.

Are you able to connect with any utilities such as CWS?

I could understand something happening on one system as the result of corruption of the snmp settings on one system but for the same thing to happen to several all at once is highly suspicious. In order for these ports to be closed (even though they are enabled in Fiery Setup), something changed on the Fiery controller side.

Is there any third-party firewall running on these systems that wasn't running previously? If the Fiery is joined to your domain, were any new policies enacted recently in your network environment?

Thanks,


Karl