>Hi guys
>
>Been looking all over the net for help with this because its not a fox problem, but when all else has failed, this forum usually has something to offer.
>
>Here's the problem.
>
>In one particular location, I can connect to a remote printer in DOS but not Windows 2000 (the exact opposite of the most common Win2k print problem on this forum)
>
>I carry my machine around with me to various sites and don't have the problem in most places. Nor do I have the problem at home (where I plug into a simple 4 station home LAN)
>
>One particular site just won't play ball. I can see all the computers in the workgroup. I can (sometimes) even click on to a selected workstation and get the list of shared devices. One or two even, occasionally, let me use their shared printer.
>
>One station in particular, however, just will not let me get at the printer under Windows (though it will happily pump out DOS printing till the cows come home).
>
>The spooler goes berserk (starts using 60-70% CPU resources and pumping out an ever increasing stream of data) and the machine effectively "hangs". If I try to close down the print folder, explorer shuts down and I'm left without a desktop and have to log off or restart. (I can, however, go into the control panel, admin services and shut down the Print services that way without losing the desktop)
>
>Naturally this is the most useful printer I need access to as it is in the same room that I work in.
>
>I have been wrestling with it for weeks now. I have played around with protocols on each station. I've deleted and re-installed drivers, changed share names, deleted and re-installed print file sharing. I've changed network cards and even tried new memory. I've deleted the spooler file and re-extracted it from the cab files. The troublesome site is running on a Novell 4.12 network with mostly Win98 workstations and a few Win2K. I have no similar problems on other Novell sites (4.12 and 5.1).
>
>And just to further confuse the issue, I use a dual boot system and when I boot in Win98 mode, the problem disappears.
>
>If I couldn't connect to any remote printers anywhere, I would assume I'm doing something wrong. But as I can connect elsewhere, and in DOS only for this one, and in any form I like with this one under Windows 98, I'm now officially stumped.
>
>Any suggestions?

A client of mine had bad wiring. He was setting up a computer in an office that had ostensibly been wired for Ethernet years previously; however, no computer had ever been set up in that office before his. He had similar problems to what you're seeing.

He rolled his computer table into another office with a known good connection and he had no problems.

Unless your patch cable from your PC to the wall jack is "known good", try a replacement there too.