Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 341
  • Last Modified:

Problems saving/caching username/password on WinXP?

I have a Windows XP workstation as do nearly all of my customer's users (tens of thousands).

They have a Windows 2000 managed network with AD.  Most of my client's users do log on the the network, but I do not.  I do have a network account, and I am prompted for my domain\username and password when I need to use some resource on the network (fileshare, printer, Exchange).  So, everything secure.

When I go to use a fileshare or Exchange, I am prompted for the information again and again, despite checking the box to remember the credentials.  I would very much like to not do this, but it doesn't seem to matter.  Even if I remain on the network and simply go back to the same Exchange server again and again, I'm prompted.

Is there any reason why I'm even offer the option of saving and is there any way to have my system actually keep these credentials?
0
Gene Klamerus
Asked:
Gene Klamerus
  • 5
  • 4
1 Solution
 
perezjosCommented:
Hello
try this:

type on explorer or start/run/  \\myloginserver\ipc$ where myloginserver is the name of the server where the ressources are or the PDC on the network. You should be propmted for a username and password.  Logging with you credentials doaminname/user and password.

This will create a pipe to that server and maintain your credentials for your session.

Hope this help


Jose


0
 
Gene KlamerusTechnical ArchitectAuthor Commented:
Well, not really.  I don't want to log on to the network.  I'm just not seeing the point of providing logon credentials when they're not being saved.
0
 
perezjosCommented:
Sorry I may miss a point here, but because you are not loggin in the network, every time you ask for a ressource on that network ex the fileshare or Exchange, you will be prompted for identification unless you create a pipe to ipc$ (loggin) or access the share on that network define in your loggin profile. That how security works otherwise what the point of having secure ressources on a network if anybody without accounts could access to share, printers and exchange. Are you accessing the network remotly and why you do not want to loggin in the network again? .

Jose

 

0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Gene KlamerusTechnical ArchitectAuthor Commented:
if I'm not logged on to the network, and I'm not, I need to provide my credentials to be validated.  That's fine

The point is why bother asking if I want those credentials to be saved.  Certainly Windows knows I'm not logged in or it wouldn't ask for them.  The fact that it's asking if I want to save them, suggests to me that it would save them.

But I guess this is just another of the Windows "gaps" that isn't done properly.

Actually, I mis-spoke earlier as well.  It appears I'm not prompted for username/password once I've set up a printer and also not for fileshares that I've visited and told to cache.  It only appears to be Exchange that's the problem.
0
 
perezjosCommented:
Hello again,

Are you using  the normal client  ? or are you axcessing Exchange with your browser ?


Thanks
Jose
0
 
Gene KlamerusTechnical ArchitectAuthor Commented:
I'm using Outlook 2003
0
 
perezjosCommented:
Hello,
I hope this help

http://support.microsoft.com/?kbid=321652

regards

jose

0
 
Gene KlamerusTechnical ArchitectAuthor Commented:
I've come to the opinion that regardless of providing valid username/password, MS Outlook will not cache the information you give it for future use.
0
 
perezjosCommented:
Thank you

good luck !

jose
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now