Bug with Vista Network Password Management?

[Guest]

I just upgraded from XP to Vista and for the most part everything is okay.
However, I believe the Manage Network Passwords capability has changed.

I have a company exchange server that I connect through via an exchange
proxy using Microsoft Anywhere, but I am off-site and need to go through a
seperate corporate proxy just to be able to access the exchange proxy. In
XP, I had the domain *.corporate.com in the managed passwords, and all
windows components automatically logged into the proxy and Outlook was able
to access its exchange proxy without any issues.

In Vista, it appears as though this doesn't work. I can no longer do
*.corporate.com and have vista recognize the proxy login. So I entered my
information and told it to remember my password. This created a new entry
that looks like this: Microsoft_WinInet_proxy.corporate.com:80/Corporate
(and I cannot see the rest as it spans off the screen). SO now Ie remembers
my login credentials, but it still does not automatically log me into the
proxy.

I have tried mucking with the security settings in IE (specifically the auto
logon section). However, I wonder if this applies to proxies? Anyone have
any ideas what may be going on and how I can get this to work as it used to?

Thanks!

 

[Guest]

I agree that MS changed the XP network password functionality. Why I don't
know but I'd guess it's security-related.

Under XP you could create entries of the form DOMAIN\* but under Vista all
you can do is create either specific names or wildcards of the form
*.domain.com.

Unfortunately, if you want to use the wildcard entry, you have to specify
the complete FQDN in every command. To use a shortname (netBIOS), you have to
have an explicit entry in the network password list for it.

Also, I've noticed that you can no longer change your domain account
passwords under Vista related to each of these entries. You have to change it
elsewhere and then change it for each specific entry in the network password
list. This is a step backwards in functionality, IMHO.

I've yet to get MS to address any of these issues. Hopefully they will soon.

Regards,

Stuart.