Re: network printer

"Gatael" <gatael@xxxxxxxxx> wrote in message
news:1132093504.845582.90400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi all,
>
> I'm having an issue where a network printer won't work for all users
> on the network but will randomly work for 5-10 users. The network is a
> windows 2003 server with approximately 50 XP Pro machines. The printer
> is an HP 2300 connected to the server via LPT port.
>
> If I log into all the machines approximately 5-10 will be able to
> print a test page and the rest will give an error saying the printer is
> not available. At first I thought perhaps it was a rights issues so I
> gave access to everyone. This did not help the problem any. If I
> deleted the printer and installed the driver all over agian it would
> work on that machine again. But if I logged into all the machines all
> over again a different set of compters would work.
>
> Anyone have any ideas? I have tried adding the printer via a login
> script but have the same issue.
>
> If this isn't in the correct group I'm sorry but I thought I'd
> start here since it doesn't seem to me to be a issue with the printer
> itself.
>
> TIA
>
> Grant

I don't have any ideas, but since no-one has suggested anything, these are
some questions which hopefully might trigger something:

1. Is it the first 5-10 people who can print? ie the first who try to
connect to the printer?

2. Is there anything relevant logged in the event log- either on the pc
trying to use the printer or on the server?

3. When you say they can't print, do you mean they simply cannot connect to
the printer at all (such as when someone doesn't have access rights - which
I know you've checked).

4. Are there any other printers connected to the server, and if so are those
okay?

Sorry these are questions rather than answers.
--
Brian Cryer
www.cryer.co.uk/brian



.

Relevant Pages

  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • Re: Vista, SBS 2003 and RAS not working
    ... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.win2000.networking)
  • Re: Connecting from Suse to windows workgroup on
    ... > pool of IPs) and I have just installed a Suse 9.3 Enterprise Server ... > From Suse pinging 127.0.0.1 works but no other machines on the Lan. ... problem with the network card or cabling... ...
    (alt.os.linux.suse)