DescentBB

Problem:

The one pc on our office network takes extremely long to access the network printer and to print a document (30s - 1min). This isn't isolated to Word but all applications & is constant.

System:

WinXP SP2
P4 3gHz (intel)
512mb ram
80gig SATA HDD
MOBO: MSI PM8PM-V
Onboard LAN
F-Secure 2006

Setup:

Did the network myself.
5 pc's total
3 = XP & 2 = Win98
Printer is on one of the 98 boxes
File content is all on a XP box
Printer: Xerox Workcenter M15i

To note:

1) 2 of the XP boxes are identical setups. The only difference is that the network documents are stored on the one box that doesn't have this issue.

2) The box having this issue doesn't show on My Network Places of any of the other pc's & not even on the pc itself

3) WinXP's firewall is disable

4) The network adapter is set as a trusted source in F-Secures firewall settings which is enabled

5) Internet sharing (currently dial-up) and accessing the documents work fine

6) The setups of the two pc looks to be identical when it comes to the Network settings

So I'm stumped on this one and a bit crammed for time to look around endlessly on the web for an answer with work, law studies and having to manage the offices IT stuff on the fly and so forth.

I would really appreciate some help on this to were the problem might be and how to solve it.

I won't ask why you are still running Windows 98.

And when you say everything is \"the same\" on the two XP systems, I'm guessing (hoping) the computer names and IP addresses are at least unique for each machine correct?

You could try running it through the home or small office network wizard keeping everything set up the same, I've seen that fix mystery issues in XP networking before. If not, start by uninstalling and reinstalling the entire network stack/drivers and the printer driver for the computer that has the problem.

If that doesn't work let us know, I have a few other ideas that might help find the problem.

Both PCs are in the same workgroup? This shouldn't make a difference but you never know. Also, try re-adding the printer. Delete it and re-add it.

ALso, try restarting the printer spooler service.

Terrific advice in this thread, also some Adobe apps. will cause weirdness. Sometimes logging off and rebooting does it, but I usually try the Networking Wizard and 80% of the time the issue is resolved.

Also toggle the Network Share on the printer box. Turn share Off, Turn 'puter off, turn 'puter on, enable share.

Or buy a small print server; Little Linksys and use the 98 box for D2.

I cant tell you the number of times I had illogical and downright stupid reasons for XP's network not functioning right, only to have it magically working again after using that damn wizard. Forget setting things manually, thats not the micro$oft way.

NetBUI could very well be your answer.

You see, Win98 can't hardly see (or broadcast) squat without NetBUI installed and running. That's the mechanism Win98 relies on to \"spread the word\" about stuff it has and stuff it want's to know about.

NetBUI is NOT required (and preferred to do without) unless you're network sharing something from the Win98. This is why Win98 is always trying to add it in when you turn on sharing in Win98.

NetBUI is NOT secure, can hog bandwidth, is 'chatty', and has limited distance and some other limitations... but using it on a Win98 does wonders to improve it's ability to see and broadcast shares on small local networks.

DISCLAIMER: You can be sure some will disagree with me, but years of using Win95 and Win98 at work with shared devices... is my experience. (Thankfully, we don't have Win95, Win98, and WinNT on our networks anymore).

Also... I like Canuck's suggestion. Get a Print server device. Best long term answer.

Not to pull a Mobius, but its NetBEUI.

the saner thing to do, if its an option, is to get a network adapter for the printer. If not, you need to find a print server that has a LPT port.

Beyond that, convert that 98 machine into a linux one and run samba, it should make things work a bit better on the network.

Yes Krom please don't ask because I still can't seem to get it through management that we need to replace those machines because not having enough ram to install XP well nuf said hey!

And yes I meant the general settings not the computers Identities my bad.

Uninstalled and Reinstalled the Networkcard as you suggested as well as the Printer which gives me a short term solution. The pc now only takes a long time to do the first print off the application in use after which if you keep the application running it access the printer almost immediately but close it and reopen it your back to square one. Tried running the wizard after the reinstall again but to no avail.

And all the pc's including this box with the problem are set to the same workgroup. Went to Component Services and restarted the printer Spooler and still the same.

Oh and at least the pc now also shows on the workgroup of network and on itself.

What bugs me is that My PC runs and access the printer 100% and is an identical system to that of the one with the problem except for the documents being stored on my box. I've already tried to print a local document from that pc and it makes no difference.

I'll look into the Print Server but again that depends on getting it through to management as a essential component

Is the print spooler service set to automatic startup on the computer with the problem? Also are the files and programs you are loading on a network drive, or just a network share not mapped to a drive? Try printing a locally stored document from the problem computer and see what happens.

Also check event viewer for any errors or warnings related to networking.

Print spooler is set to automatic startup. Its mostly just office documents on the network which I mapped as a drive for pc impaired fokes at the office & there's no diff in printing a document from local / network drive. When I've got a spare minute again I'll check the event viewer for anything funky but in word I've notice in progress bar it states \"connecting to printer\" when it takes its time on first print.

Just wanted to thank you all for the input and let you know I solved my problem. An unforeseen move of the one office partition made it possible to hook up a XP pc to the printer and low and behold everything works like a charm now!