eEye Digital Security

I recently bought a Xerox Phaser 6180MFP printer/scanner, and it's setup as a network (home) printer via the router. The printer uses port 21. With Blink enabled, it works OK as a printer, but will neither scan to a designated folder, nor to FTP folder. On the other hand, when Blink is shutdown, I can scan to the folders.

Where should I create the rules for Blink to accept the Xerox printer for scanning to the shared folders?

Ozone

Ozone:

Where should I create the rules for Blink to accept the Xerox printer for scanning to the shared folders?

Okay first step you can try is this.

1.  Go into Blink's Options at the top.

2.  Select the Firewall tab.

3.  Put a check mark in the "Enable Firewall Passive Mode".

Now at this point go ahead and run your program and follow through the steps to do whatever you want to do with your printer.  At this point, if Blink's firewall is blocking something from happening, you will see log entries in Blink's logs that show what traffic was being blocked and needs a rule for it to pass successfully.  You should be able to right click on one of these and select the function that createa the rule for you.

After your done be sure to turn off the firewall's passive mode setting...if you don't, your firewall will allow anything in and out of your system without asking you. :)

If this does not work, I can try to provide you with other ideas and recommendations.

Thanks. Carried out instructions, and created a rule. IP Address of printer - 192.168.0.201. IP Address of computer -192.168.0.101 (confirmed via ipconfig). Server Type - SMB. Still not able to scan to folder with Blink enabled. Any further ideas?

Try changing your firewall rule to reflect the following:

Protocol: UDP

Direction:  Any Directions

Local IPs:  Allow any Local IP

Local Address -

Rule applies to all IP addresses of this computer

Specify local ports for this rule:  21, 137-139, 445

 Remote Address -

Specify Remote IP addresses for this rule:  (IP of your printer)

Specify remote ports for this rule:  21, 137-139, 445

=============================================

You may try allowing both TCP and UDP (if the above does not work) for the protocols.  I am trying to allow as little as possible in your case though.  CAN you narrow it down to being ONLY the firewall causing this (if you disable the firewall only)?

Thanks for your suggestion. I tried all you suggested, but still no go if Blink is enabled. The scanner of the printer system activates with its lamp movement back & fro, but does not complete the process of sending to the folder, yet as soon as Blink is shutdown, it scans and processes the information to the folder instantly. Another observation -- it could scan to folder before the latest update to v4.3. All this started AFTER the latest update a few weeks ago.

     Alright, well here is your next option then.  You will need to create a debugging log of the issue for eEye to look at because it sounds like something internal that I can not assist with.

To do this, follow the instructions located in the begining of this post:  http://forums.eeye.com/forums/t/873.aspx

Email the debug log to moh@eeye.com and lnicula@eeye.com  and reference this post so they can hopefully assist you.

Thanks. I'll do that and post the results.

You can try to post the results (but that will be a lonnng post considering how much information will be in the text log file after your done).  Probably be better to just send it to the two folks that I listed above at eEye.

I would recommend doing the following:

If your able to, see if a particular module (Firewall, AV, IPS, etc) in Blink is stopping your printer from working properly.  You do this by disabling one at a time and then attempting to use your printer.  It may not just be one module within Blink, but if it is you disable all of the other modules (except that one).  Next you start the debugging process and then follow through with the steps of using your printer the way you want to use it.  After that you disable the debugging process and send the required log file (listed in the post I pointed out above to follow) to the folks at eEye.

If it is just something within Blink (and not a module) that is causing your issue, leave everything enabled and then run the debugging process as I have described to you.

First, I must thank you for suggesting I forward my problem to the folks at eEye. Laurentiu Nicula was my support person.

After many emails back and forth with Laurentiu, since April 1st, to pin down the bug, and to confirm the fix, early this afternoon (DST) the problem was solved. It's fix is reflected in Laurentiu's response to another post at http://forums.eeye.com/forums/p/967/4156.aspx#4156.

Ozone

Good deal!  I would go ahead and remove the firewall rules that you made before and then allow the system to prompt you to make new ones over again when you try to use your printer.

Good idea. As a matter of fact, during the fact-finding mission to find the bug, I was asked to create a similar rule -- after allowing Blink to log its error in passive mode. At that time the bug wasn't fixed, so the printer still would not scan to folder. In any case, I removed the firewall rule as you suggested.

With the fix, and the rule removed, it scans OK. Incidentally, we found the printer could scan when Intrusion Prevention was disabled. With logs from WireShark, Dbgview, and Blinksvc, Lauretiu found the bug and solved the problem. Our small office is now humming with glee for the network printer.