Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 6389 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to Network print - Invalid checksum

AlexC

I'm unable to print to a network printer. The firewall log shows that spoolsv.exe to the remote printer port is blocked because of an Invalid Checksum, it's coming from localhost(any).

I've tried searching the computer for all instances of spoolsv.exe and have added it to the checksum list in the firewall configuration, since the log doesn't tell me the file path of the specific application it blocked... I've also ensured that the LAN IP address of the printer is added to the trusted list.

Neither works - when I allow all traffic I can print without any problem, so the firewall is definitely the culprit here.

I'd be grateful for any suggestions?

:3017


This thread was automatically locked due to age.
Parents
  • 0

    Hello all,

    Solved my problem but thought to post here for sake of documenting and to save wasting anyones time replying.

    To determine the active process, go into Services under Administrative Tools and then find Print Spooler - open this and it will show the location of the spoolsv.exe.

    Add this to the checksum list in firewall configuration (remove any other spoolsv.exe in the list first), then also add it to trusted applications and hidden processes. I also added a Global Rule to allow outbound TCP to the remote IP address and port specified in the firewall block log rule when I experienced problems.

    Not sure which of the three things I applied is the actual solution, haven't got time to play about and find out now, but hope to do so soon!

    :3019
Reply
  • 0

    Hello all,

    Solved my problem but thought to post here for sake of documenting and to save wasting anyones time replying.

    To determine the active process, go into Services under Administrative Tools and then find Print Spooler - open this and it will show the location of the spoolsv.exe.

    Add this to the checksum list in firewall configuration (remove any other spoolsv.exe in the list first), then also add it to trusted applications and hidden processes. I also added a Global Rule to allow outbound TCP to the remote IP address and port specified in the firewall block log rule when I experienced problems.

    Not sure which of the three things I applied is the actual solution, haven't got time to play about and find out now, but hope to do so soon!

    :3019
Children
No Data