This could just be a name resolution problem.
Are you running a WINS server in the domain with the printer? If so, is the server the printer is attached to a WINS client? It should be.
Also, is the Win98 machine a WINS client? It needs to be.
If you are running WINS on the domain, and all 350 computers are WINS clients, then definiately make sure the WIn98 box is a WINS client also.
Now, if WINS is not an option, you are gonna have to set up a LMHOSTS file on the Win98 box that has the 350 clients configured in it.
Win98 uses the Netbios names for resolution, but it will only get the resolution from 1)WINS 2)LMHOSTS file or 3)broadcast resolution, which is the least desirable of the 3.
Here is a TechNet doc on how to set up a LMHOSTS file:
http://support.microsoft.com/support/kb/articles/Q180/0/94.ASP
This article talks about modifing the upper limit for the number of machines that can be loaded in the LMHOSTS file. The limit is 100. Looks like you will need more:
http://support.microsoft.com/support/kb/articles/Q101/9/27.asp
Next: if the domain with the Win98 machine has its own WINS server, then you can make that server and a WINS in the NT domain push-pull replication partners. That way, your Win98 box coulduse its own WINS server for resolution, but the total database would be shared between WINS servers. The Win98 box WOULD get name resolution. Here is an article on this:
http://support.microsoft.com/support/kb/articles/Q168/5/09.ASP
Last, if youdon't want to do any of these steps, you can just manually add a static route to the one machine with the printer. Here is another TechNet article on this:
http://support.microsoft.com/support/kb/articles/Q210/3/27.ASP
There is a lot of stuff onname resolution, network browsing, and all of the headaches that can result.
Hope this helps.
