You mention that this occurs when people are streaming jobs. Are you by chance using VeSofts STREAMX product? If so, then this is STREAMX trying to determine "who" you are. I've seen this before. Another time where this will show up is if you have multiple systems running Security/3000 and you are setup to not require passwords when you DS from one to the other (that's one exampkle scenario). In that case, when you logon from as a VT from a PC, Security/3000 tries to determine "who" you are and that results in the dreaded VT Error 42 (since your not another 3000, but a PC). Not the most "technical" explaination, but its been a while since I've messed with it :) Regards, Michael L Gueterman Easy Does It Technologies Allaire Alliance Partner email: [log in to unmask] http://www.editcorp.com voice: (888) 858-EDIT -or- (509) 943-5108 fax: (509) 946-1170 -- > -----Original Message----- > From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On > Behalf Of Marcus E. Carlson > Sent: Wednesday, November 25, 1998 12:17 PM > To: [log in to unmask] > Subject: [HP3000-L] NetIPC ERROR IN VT > > > Greetings: > > Neophyte wants (needs) to know: > > We recently installed an Ethernet network with a second > server running NT > 4.0 SP3. We upgraded the 937RX to MPE 5.5, pp 4? (sorry maybe > 5 but I can't > remember, if it becomes germane I'll find out), HPs' new > 100base-TX NIC > (don't try this at home!), a memory upgrade, HD upgrade. > > We were all direct through DTC's. Now of course we're running > just about > everything over the network but now the console frequently > displays the > following errors: > > ** NS/3000 NetIPC ERROR IN VT; Job: #S...; PIN: ...; Info: 1 > -Error: 42; > > Everything works fine, just these errors. Are they something > to worry about? > Maybe its just collisions? > > It seems to be related to streaming print jobs over the > network, rather than > through the DTCs, but then again, maybe not. The Job number > doesn't relate > to anything visible running so I thought maybe print jobs. > Job# & PIN# seem > to be random. > > Anyone know? > > TIA, > > Marcus >