Urgent - Printer share problem on network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I posted this Monday without response. Can anyone offer suggestions as I
need to resolve problem?

I have a hubbed network with W2K server, two W2K hosts and a Riscos PC
host. Riscos and one PC connect via cable, other PC host via WLAN. I can
ping and exchange files all round without any problem, but I cannot share
printers on the other two PC's - even when ZoneAlarm is disconnected. When
I try to add printer, I get error message "could not connect to the
printer. You either entered printer name that was incorrect or the
specified printer is no longer connected to the server". Something is
wrong because I am using the allocated share name and the Riscos machine
is able to share printers. In the latter case, I have to specify the path
but I thought with W2K this was not necessary. Has anyone got any thoughts
on this?
Many thanks
David
 
Are these printers connected to the server and do you have them shared from
the server?
With W2K hosts, do you mean W2K-Pro-clients? What is the Riscos PC?

Marina
 
Both printers connected to the server and both shared from the server.
Don't worry about 'Riscos PC' - Riscos (Reduced Instruction Set Computer
Operating System is a different operating system with quite a wide user
base in UK and Netherlands (go to www.riscos.org/cgi-bin/artcl?a=welcome
and http://productsdb.riscos.com/admin/riscos.htm). I've defined the exact
printer path on the Riscos software so I would expect it to use the server
printers
Yes, W2K-Pro server and hosts
HELP!!
David
 
So you want the W2K-clients to be able to print. When do you get the
errormessage? Is it when you try to look in active directory, or the second
option when choosing networkprinter?

Marina
 
Hi Marina

You can ping printers?? How do you do that? I never knew printers had an
IP address.
David
 
Marina, I may have got to the reason why. Tried to access server from one
of the hosts via 'My Network Places'. Host icon comes up but double
clicking gives error message "Hostname not accessible. The server is not
configured for transactions". But host-to-host access is perfect. So
although I can ping etc, something is making the host unrecognisable. On
re-booting, I *can* access the server from my host just after the network
is activated, but not after the server has fully booted. Make any sense?
David
 
Yes Marina, it was installed on all machines. I'm right up to date on all
security patches.
David
 
Back
Top