Re: network printer not working

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Wed, 24 May 2006 08:44:02 -0700, usnst <usnst@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

"Chuck" wrote:

On Mon, 22 May 2006 11:59:02 -0700, usnst <usnst@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

I work in an office that has about 15 work stations. My problem is there are
a couple of PC's that will not print to a printer on the network. I thought
the problem might be a conflict between XP and 98, because the printer is
physically attached to a PC that is running 98, however another workgroup
computer is running xp as well and works flawlessly with the printer. The
problem PC "sees" the printer when i browse the network, but it will not
connect to it or let me add it. When i try and manually enter a IP and port
for the printer, it says port name not valid etc. Ive tried all the basics
and nothing seems to work. Any insight would be appreciated.

I'd look for LSP / Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

Do i run those things on the problem PC or the PC that is physically attached
to the printer?

You have an office with about 15 computers, and just a couple that won't print.
And there are other computers like the problem ones, that will print. So run
those things on the computers that won't print.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.

Relevant Pages

  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • HALP! My XPs ports are unusually opened!!
    ... I have Windows XP Pro. ... I used an IP scanner to check all the computers ... on the network and it shows 3 computers on the network (including ... First I connected at port 19. ...
    (microsoft.public.windowsxp.network_web)
  • Re: {workgroup}"...is not accessible" after removing NWLINK
    ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)