WinXP networking to WinNT4 problems

Several Windows NT 4 SP6 peer-to-peer with Win XP Home edition SP1 plus some misc. Windows Updates since... 2 HP LaserJet IIID printers, one attached directly to LPT1: on an NT server box, the other on the network via Intel NetportExpress (small IP network print server box).

Two problems (or 3 if you count both parts of problem 1 separately....):

Problem 1: This problem has 2 parts. I have a DOS application that needs to print on these printers, and successfully does so from other NT4 machines. However, from the new XP boxes

Part 1: As a 'limited' user on XP (not admin), I can NOT "NET USE LPT1: \\server\printer" these printers at all. When I try, I get "Not authorized" response. I need the users to be non-admin, and they need to use these printers. Any ideas?

Part 2: If I use ADMIN account on XP, I can "NET USE" the NetPort printer fine, but the NT4 printer responds with "SYSTEM ERROR 66. The network resource type is not correct ". Any ideas as to why different responses, and what the 66 error is all about? (and how to get around it?)

Problem 2: There appears to be some sort of file conflict with the DOS programs when they run on XP that does not exist when running on NT4 workstations. A file shared from an NT4 server in the network does not OPEN from the dos app on XP if it is in use by another dos app in the network, whereas dos apps on NT4 have no problem processing this shared file. Any way to force XP to handle shared file like NT4 does?

 

I think the clue here is in the XP Home part of the network. AFAIK you cant use XP Home with a domain full stop.

Somebody else may be of more help though as I dont touch XP Home, bit like Me - business doesnt want it

 

Not in a domain - no domain controller, etc. This is a peer-to-peer network, with one NT 4 server participating in the mix, which shares files with users on NT4 workstations, and now some XP boxes (new replacements for som of the really old NT4 boxes).

 

My apologies, read something that wasnt there !

I assumed that NT server was a DC

 

Sounds like you’re in a real grey area here using Home in a corporate environment.
Check the server logs and see if there are some Master Browser errors. That XP box may be competing with the server for who takes that responsibility.
You may have to change master browsing to "False" in the registry.
That is located in:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Parameters\MaintainServerList from "True" to "False "