Unsolved
This post is more than 5 years old
4 Posts
0
9454
October 20th, 2004 19:00
Unable to connect to printer
Since 10/17/04 when I downloaded W*XP SP2 on my Dell Dimension 8250 it has been unable to communicate with my Canon MultiPASS F80 copier/printer/scanner. No response when I try reconnecting using the Services applet in Control Panel. No response when I try reinstalling using the supplied CD-ROM.
I don't know for sure if it's the service pack, but reading the other messages in this section sure point to the culprit. (Also there are random freezes when I try to navigate around the computer).
What should I do? Uninstall SP2?
Appreciate any advice.................../s/David
No Events found!
jmfmvps
517 Posts
0
October 20th, 2004 21:00
jwatt
4.4K Posts
0
October 20th, 2004 23:00
[IPC]
Address=127.0.0.2
8. Change ONLY the number in this document to the following:
127.0.0.1
After the change, the document will read as follows:
[IPC]
Address=127.0.0.1
There's a fix available for the "127.0.0.1 only" "feature" introduced in Service Pack 2. See this Microsoft article for details.
Jim
delta7000
2 Intern
•
454 Posts
0
October 20th, 2004 23:00
I have a 8250 with a Canon Multipass F60 and experienced the same problem after installing SP2. For some reason I was not able to download their fix so I contacted Canon. This is what they told me to do. It seems a lot more complicated to do then it really is
If the issue persists, please do the following to resolve the issues
related to installing Windows XP Service Pack 2 with the MultiPASS Suite
installed:
1. Restarting Windows or attempting to print, the following message
appears: 'Unable to Communicate with the device. Please start
'MPService' from the Services applet in the Control Panel.'
2. Attempting to scan, the following message appears: 'Server Busy -
This action cannot be completed because the other program is busy.
message appears.
3. Opening [Windows Explorer], [My Computer] or [My MultiPASS], takes
too long and appears to hang.
Please change the IP address in file MPNETIPC.INI to 127.0.0.1. This
file is located in WINNT\SYSTEM32\ (depending on the computer, the path
may be WINDOWS\SYSTEM32\).
1. On Windows desktop, click [Start] and then [Search].
2. In [Search Results] window, click on [All files and folders].
3. In [All or part of the file name:] box, type mpnetipc.ini.
4. Verify that [Local Hard Drives] is selected in [Look in:] drop-down.
5. Click on the [Search] button.
6. Once search is complete, double-click on the file [mpnetipc.ini] to
open the document.
7. In the document, you will notice it reads the following:
[IPC]
Address=127.0.0.2
8. Change ONLY the number in this document to the following:
127.0.0.1
After the change, the document will read as follows:
[IPC]
Address=127.0.0.1
9. Click [File] and then [Save].
10. Close the file and all open Windows.
11. Restart the computer.
After performing the above troubleshooting suggestions, please respond
to us with feedback regarding the results of the change. Did this
resolve your issue?
Are you able to print and scan now?
Please let us know if you need further assistance with this issue by
replying to this message and including the email history. This will
allow us to respond "
JD Scot
115 Posts
0
October 21st, 2004 15:00
First step: Go into your printer folder.
See if the printer is listed. Try to run a test page ( This isolates whether it is the printer or the program attempting to access it is the issue).
If the printer does not run a test page, uninstall the driver, and unplug the printer from the system. Then reboot the system. Connect your printer to see if XP installs a driver for it ( My Knowledge XP does carry a lot of drivers for hardware). If it does not carry the driver for your printer, it will prompt you to put in the manufacturor's driver disk. Once the driver is installed via either method listed, lok in the printer folder and see if the printer is listed. Then try running a test page to see if it spools a page.
Most important: When you reinstall your printer and driver TURN OFF THE ANTI VIRUS SOFTWARE!!!
Early Riser
4 Posts
0
October 21st, 2004 19:00
Dear Jim...............Your suggestion -- notable for its logic and simplicity -- worked, though the Canon instructions leave something to be desired and the download triggered a dire warning that the originator of the patch was suspect.
Thank you and thanks to the others whose solutions also seemed plausible.
/s/David
jmfmvps
517 Posts
0
October 21st, 2004 20:00
Glad you got it worked out!
Message Edited by jmfmvps on 10-21-200405:03 PM
Message Edited by jmfmvps on 10-21-2004 05:03 PM