Belkin Print Server deletes printer driver from client machines
I am trying to set up an HP 1219 PSC connected via USB to a Belkin Print Server which is connected to a Belkin wireless Router, which in turn serves 4 wireless clients, all running XP Home. The problem descibed below happens irrespective of whether the Print Server is hard wired or wirelessly connected to the Router.
I follow the Belkin Print Server installation procedure to the letter and successfully get a test page printed during the process. But as soon as the process is finished, the printer is deleted from the list of installed printers on the client machine(s) and the supposedly "networked" printer can no longer be printed to.
From the client machine(s) I can access the web interface of the Router (192.168.2.1) which shows the Print Server as a client (at address 192.168.2.x). I can also access the web interface of the Print Server (at address 192.168.2.x) and it shows the HP 1219 PSC connected and ready.
The only way out of this is to re-install the printer as a local connected printer on each of the client machine(s) and start again, but the whole cycle just repeats itself.
I have noted that the Print Server installation process adds a "Belikin Port" to the list of available printer ports, but this too disappears when the installation process is complete.
If I try and "add a network printer" at a client machine, I cannot "see" the printer connected to the Print Server. No combination of Print Server Name and/or IP address brings the printer into view. Neither can I see the printer under "my network places" or "my network connections".
If I try and "add a local printer" at a client machine and then select (or redefine, if not there) the Belkin Port, that does not work either.
This has been driving me mad, so I would be grateful for any help offered.
socross
I follow the Belkin Print Server installation procedure to the letter and successfully get a test page printed during the process. But as soon as the process is finished, the printer is deleted from the list of installed printers on the client machine(s) and the supposedly "networked" printer can no longer be printed to.
From the client machine(s) I can access the web interface of the Router (192.168.2.1) which shows the Print Server as a client (at address 192.168.2.x). I can also access the web interface of the Print Server (at address 192.168.2.x) and it shows the HP 1219 PSC connected and ready.
The only way out of this is to re-install the printer as a local connected printer on each of the client machine(s) and start again, but the whole cycle just repeats itself.
I have noted that the Print Server installation process adds a "Belikin Port" to the list of available printer ports, but this too disappears when the installation process is complete.
If I try and "add a network printer" at a client machine, I cannot "see" the printer connected to the Print Server. No combination of Print Server Name and/or IP address brings the printer into view. Neither can I see the printer under "my network places" or "my network connections".
If I try and "add a local printer" at a client machine and then select (or redefine, if not there) the Belkin Port, that does not work either.
This has been driving me mad, so I would be grateful for any help offered.
socross
ASKER
Thanks for the quick response.
The model is Belkin Wireless G USB Print Server, F1UP0001, VER.2002uk.
I will try your sugegsted static IP approach and let you know, but it won't be until tomorrow.
socross
The model is Belkin Wireless G USB Print Server, F1UP0001, VER.2002uk.
I will try your sugegsted static IP approach and let you know, but it won't be until tomorrow.
socross
I would return it for another.
T
T
ASKER
I have tried the static IP approach suggested by garycase but it makes no difference.
Any other suggestions, anyone?
Any other suggestions, anyone?
Are there any other non-standard TCP/IP printer ports on these machines (e.g. Epson)? Since you have a state where you can access the print server and it sees the printer as "ready", the problem is probably in the software on the clients. I also have difficulties in visualising a scenario where a print server actually removes anything from other nodes on a LAN...
/RID
/RID
You could also try to add a standard TCP/IP port for the new printer instead of the "Belkin port", using the IP of the print server (static is good practice!) and standard Windows TCP/IP port.
/RID
/RID
ASKER
I've deleted all other printers installed on the client(s) and tried adding a standard TCP/IP port, but it maked no difference (static or dynamic IP). The installed printer simply disappears before my eyes from the list of installed printers as the add port wizard is applied.
So sorry, but no solution yet.
socross
So sorry, but no solution yet.
socross
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Ed. Will try this out over the next few days, but I'm up to my neck in other stuff right now. Anyway, hopefully you've got the solution and I will be able to accept. Don't go away !
socoss
socoss
Well, the process I described _could_ have helped, given that it bypassed the wizard, but I wouldn't describe it as a sure fix without testing. So whatever the moderators make of that situation...
Ed
Ed
ASKER
Please keep this question live for a while. I just have not had time to try the proposed solution, but will do so within the next month or so.
Thanks
SoCross
Thanks
SoCross
Hi SoCross
any updates?
Daleoran
EE Cleanup Volunteer
any updates?
Daleoran
EE Cleanup Volunteer
ASKER
No update yet, but please keep this question open. I do need to resolve this, but so far higher priority jobs get in first.
SoCross
SoCross
ASKER
Thanks for your help Ed. All working fine now. Sorry it took so long to get this question accepted/closed.
socross
socross
You're welcome-- glad it worked for you.
Ed
Ed
If the print server supports it, you should try assigning a static IP to the print server -- something "out of the way" but in the same subnet => e.g. 192.168.2.99 would work well.