Strange password problem

[databarn]

Folk,<br>
<br>
Has anyone run into this before?<br>
<br>
On an NT 4.0, SP4, network at work. Every once in a while, even though I've logged into the network properly, I'll be prompted for a password for a network printer share. Every fifth or sixth time, the password will be rejected (even though it is correct) and I will be summarily locked out of all local network resources. I can still see the intranet, but I cannot access any resource on my 'home' server.<br>
<br>
This happens only to me, insofar as I am aware. My NT admin thinks it is 'local', i.e., configuration of my system. Problem I have with that is that I've had this problem with five different boxes, two of which are laptops, one my desktop machine, and two 'standby' machines. I'm working on the assumption that it is some configuration tied to my UserID. My admin rejects this concept, mostly because of the time it would take to research.<br>
<br>
This happens both when I dial in (ISDN) and when I am 'plugged in' directly to the network.<br>
<br>
Any ideas?<br>
<br>
Make a good day . . .<br>
. . . barn<br>

 

[unit512]

Have you tried logging in with another name and password...say one with more rights (at least temporarily)?

 

[databarn]

Abelson,<br>
<br>
'Preciate the response. The NT admin is 'convinced' that the problem is 'local' to my machines(s). He provided me with an alternate logon ID, but it doesn't have all the connectivity that my 'original' ID had, so it's not really the same. <br>
<br>
I could probably get around the problem by going to NT, but that's not a viable alternative so long as I have to provide support for a Win9x group - need to be able to 'see' the same things they do. (Comes under the heading of describing the colour 'purple'.) Anyway, that would not resolve the problem, 'twould just avoid it.<br>
<br>
Make a good day . . .<br>
. . . barn<br>

 

[Zelandakh]

How is the network printer joined to the network? Directly to the home server, Jet Direct card, IP, DHCP?<br>
<br>
Zel

 

[databarn]

It's an HP LaserJet 4 with an internal JetDirect card. Don't know the IP address off hand.<br>
<br>
Oh, one other thing. If I attempt to print remotely, I'll usually have the password problem the next time I connect directly at the office even if the print job was successful.<br>
<br>
Make a good day . . .<br>
. . . barn<br>

 

[TANKERx]

Just a couple of thoughts....<br>
<br>
Is your profile kept on your local machine or on the server? WindowsNT has had problems with Roaming Profiles and it could be that something is wrong with that.<br>
<br>
If it is kept on your local machine, is it possible that you've done something to the account you'e using because if you have a username Bob, delete the user and recreate another user called Bob, even with the same rights, the system will see the new Bob as different to the old Bob (SIDs or SAMs, I think).<br>
<br>
If your admin is convinced its your PC, then (s)he has probably checked your computer's account on the PDC and all that.

 

[databarn]

TANKERx,<br>
<br>
And rightly thunk thoughts they are. Yep, the admin _is_ convinced it's my laptop, and doesn't want to hear me when I tell him that this has happened on several (five) different boxes. Don't blame him, really, I'd not want to hear that either. Cannot replicate the problem on my home network, but I don't heve it set up for dial-in access - and probably wouldn't matter if I did.<br>
<br>
All the profiles are kept server-side, so anyone can log in from amy machine on the network, just specify appropriate username, password, and domain/server. I don't have the ability to make changes to the account. However, I do have 'multiple profiles' because of my work. That is, my login includes the standard profile for my departmental group, another profile for another departmental group, and a third profile that involves some development stuff. Oh, the printer access is machine-based, not profile-based.<br>
<br>
These are all straightforward profiles, I just end up with a bunch of network connections with my 'standard' logon that most other folk don't have. <br>
<br>
The ISDN and standard DUN profiles are handled on the mainframe end of the network, so I don't have much info on the profiles involved there. The DUN (standard 56K modem) access allows me to specify whether to log on the the network in the modem configuration, but the ISDN login pretty much logs me onto the network willy-nilly - I don't have any option there, it's all tied to the ISDN profile.<br>
<br>
Make a good day . . .<br>
. . . barn<br>

 

[Zelandakh]

How does the printer print? Via IP or DLC? I'm inclined to go with the profiles idea detailed above but anyway. If you delete the accounts on the servers, delete the associated password list files on the local machines and recreate, you should cure the problem.<br>
<br>
If not, repost...<br>
<br>
Zel

 

[Zelandakh]

Alternatively, delete the printer and re-create that.

 

[RoadRunner]

I believe it has to do with the cached profile.<br>
<br>
The default on the server is set to expire after so many successful login attempts.<br>
<br>
Or try this:<br>
<br>
PRINTING TO A NETWORK PRINTER<br>
=============================<br>
<br>
You might have problems printing to a networked shared third-party printer. The solution is to redirect LPT1 through an MS-DOS window to the third-party share, and <br>
then use the printer setup for LPT1.<br>
<br>
For example, if a network printer is connected to LPT1, follow these steps:<br>
<br>
1. At the MS-DOS prompt, type:<br>
<br>
net use lpt1: \\servername\sharename<br>
<br>
(This command might be different on the network you are using. Check the product documentation to find out how to redirect an LPT port.)<br>
<br>
2. Start Control Panel, double-click Printers, and then double-click Add Printer.<br>
<br>
Cautionary Note: Be sure to use a 8.3 name. Sometimes NT 4.0 has a problem with long printer names.<br>
<br>
BB<br>