Re: Can't print to my Windows 98 shared printer from my XP compute

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



Thanks for the reply. Yes I agree that the printer name has to be 12
characters or less or else the printer won't be visible to the Win 98
machine. This applies to the reverse case where the 98 machine is connecting
to a shared printer over the network. But this is not my problem here as I'm
connecting from a XP computer and besides I can see the remote printer.

Anyway, thanks for posting the useful URLs.

"MartynB" wrote:

> Martin,
>
> You mention the VSERVER issue, but have you re-updated W98 Dial up
> Networking since you re-installed W98?
>
> I seem to remember that having a printer name or description that is too
> long may cause W98 printer networking problems.
>
> This could also be a sharing permission issue. There are different scenarios
> described here:- http://support.its.ied.edu.hk/stufaq/7.3.html.
>
> You may be eligible for Microsoft's "Individual Chat Support" for Windows XP
> issues, which is free for 2 support requests.
> http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=3518&gprid=185522
>
>
>
> "Martin Healy" <MartinHealy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4B92D08F-7DAB-4163-B024-698F4F47EEE5@xxxxxxxxxxxxxxxx
> >I can't print from the printer attached to my Windows 98 machine using my
> >XP
> > computer. I can successfully browse for the printer under
> > \\Martin\LEXMARK
> > when adding the printer in XP. When I select Next in Add Printer Wizard
> > after browsing to the correct print queue name above, an error message is
> > displayed as "The server for the 'Lexmark Z52 Series ColorFine' printer
> > does
> > not have the correct printer driver installed etc". As a result, I then
> > clicked OK to continue and selected the built-in XP Lexmark Z52 driver
> > from
> > the manufacturer's list. Next the Default Printer page appears in the Add
> > Printer Wizard requesting me to use this printer as the default printer.
> > After choosing YES and selecting Next to this, the final Add Printer page
> > appears stating: "You have successfully completed the Add Printer Wizard
> > etc".
> >
> > However, when I attempt to print a test page from my XP system over the
> > network, it displays the following message: "Test page failed to print.
> > Would
> > you like to use the print troubleshooter for assistance? operation could
> > not
> > be completed".
> >
> > The status of my Lexmark on Martin network printer shows up as 'Ready' in
> > Add Printer wizard and has a pipe attached, indicating a network printer.
> > If
> > I print locally from my Windows 98 machine, I can see the document queue
> > and
> > the document being processed from my XP system by double clicking on the
> > printer icon. In other words I can see the test page being printed on my
> > 98
> > machine from my XP computer. Also, the Documents would show 1 on my XP
> > printer icon. It's strange that I can see pages being printed locally
> > over
> > the network and that I can't print over the network using my XP computer.
> > Incidently, Lexmark represents the share name of my printer and Martin
> > represents the name of the Windows 98 machine.
> >
> > Also, I can view all shared resources on my Windows 98 machine over the
> > network from my XP laptop. Furthermore, I can access shared folders on
> > the
> > 98 machine and I can successfully ping the 98 machine from my XP laptop.
> > From the point of troubleshooting, I elimimated a potential VSERVER.vxd
> > conflict message when adding the File and Printer Service in Microsoft
> > Networks in Windows 98 by extracting a new copy of this file to the
> > C:\Windows\System Directory. This corrected that problem but did not
> > resolve
> > my existing print issue. I would also like to remind you that I was able
> > to
> > print over the network in the past from my XP laptop without ever having
> > to
> > select the built-in XP driver for that printer. I'm using the same
> > printer
> > driver for my Lexmark Z52 on my 98 machine as I did in the past when it
> > last
> > worked. I still have a copy of this print test page from last December.
> > The
> > driver name showed up as UNIDRV.DLL on my XP test page when it last
> > worked.
> > I have done virtually everything as this stage to solve this remote
> > printing
> > issue. There is no real simple solution to this problem as I have found
> > out
> > over the last 3 weeks. It's only since I carried out a reinstallation on
> > my
> > 98 machine a couple months ago, that this problem has arisen. I find it is
> > very strange because I have a perfectly working network connection and I'm
> > using the built-in XP driver on my XP laptop when connecting to the 98
> > printer over the network.
> >
> > This inability to print over the network from my XP laptop is a major
> > drawback because it also means that I can't use this network printer for
> > incoming faxes.
> >
> > The only thing left for me to do now after correcting the VSERVER issue on
> > the 98 machine is to uninstall and reinstall the LAN connection components
> > on
> > my XP laptop etc. TCP/IP, WLAN protocols, File & Printer sharing etc in
> > Network properties which could be problematic in its own way. Please
> > note, I
> > can print locally from my printer and I can access shared folders on the
> > 98
> > machine from my XP laptop but I just can't print over the network using
> > the
> > printer attached to the 98 machine.
> >
> > Could you please tell me if there is any technical online chat (SIP)
> > facility available in relation to this issue as this problem is ongoing
> > for a
> > long time now. I don't think the manfacturer of my XP laptop will assist
> > me
> > with this problem as the 98 machine is from a different manufacturer. At
> > this stage, I feel the problem lies on the XP side rather that from the 98
> > machine. This is why I have posted the problem here rather than the
> > Windows
> > 98 community site. Recent windows updates or patches on my XP laptop may
> > have lead to this problem. It's is not a Lexmark issue either as it
> > worked
> > before using this printer and I have carried out the exact same procedure
> > in
> > setting up the network printer as in the past. Finally it is not a
> > printer
> > driver issue as well since I'm using the built-in Lexmark Z52 XP driver on
> > my
> > XP system while adding the printer - even though I succeeded without this
> > driver in the past by just using the UNIDRV.DLL driver on the 98 side.
> > The
> > printer port settings are also correct as it shows up as \\Martin\Lexmark
> > in
> > XP and LPT1 in 98. I also ensured that the default data type is set to
> > RAW
> > in the XP printer properties.
> >
> > Once again, I would appreciate any suggestions that may fix this problem
> > if
> > at all possible.
> >
> > Thanks
>
>
>
.



Relevant Pages

  • Re: SP2 Causes Blue Screen Crashes--"BAD_POOL_HEADER"
    ... allow my laptop to share the ... I downloaded the Netgear MA111 V2.0 driver from the website, ... wireless connection and created a new ad-hoc "preferred network" under ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Cant print to my Windows 98 shared printer from my XP compute
    ... >>>I can't print from the printer attached to my Windows 98 machine using my XP ... >>>Add Printer wizard and has a pipe attached, indicating a network printer. ... >>>98 machine and I can successfully ping the 98 machine from my XP laptop. ... >>>driver name showed up as UNIDRV.DLL on my XP test page when it last worked. ...
    (microsoft.public.windowsxp.network_web)
  • Re: XP Peer to Peer Network: all OK except for this ...
    ... >I have connected a laptop and deskptop via a crossover ... >cable using Windows XP networking capabilities. ... "Network access: Sharing and security model", and ensure it's set to "Classic - ... If you set the Local Security Policy to "Guest only", ...
    (microsoft.public.windowsxp.network_web)
  • Re: how did Microsoft break away from OS/2?
    ... a Windows laptop got infected simply by being connected to a network. ... The issue here is whether Windows is secure or not, ... It is connected to a network where there are compromised Windows ...
    (comp.os.os2.advocacy)
  • [NMRC Advisory] Microsoft Windows Wireless Exposure on Laptops
    ... Application: Wireless Network Connection ... This advisory documents an anomaly involving Microsoft's Wireless Network ... If a laptop connects to an ad-hoc network it can later start ... This is known as a Link-Local address, and by default Link-Local is turned on on all Windows platforms on all interfaces, including wireless interfaces. ...
    (Bugtraq)