Stored user names and passwords BROKEN in Vista

It seems that stored usernames and passwords no longer works in Vista (XP
works fine).

We use this feature to connect to SQL Servers using a particular UID/PW
combination so we dont have to use clear text authentication (i.e. SQL
Server Auth).

On XP we could create a wildcard domain and UID/PW and save it in "stored
user names and password" then the user could use for example iSQL or
Enterprise Manager to connect to the server via windows authentication.

If I try this with Vista it either sends my current domain id/pw OR (if
the machine is not in a domain) it seems to send NULL instead.

Anyone have any ideas on what/where something might be adjusted to fix this
issue ???

BTT


Anyone ????

Is no one else using this feature in XP ????



"WayCool" <someone@msn.edu> wrote in message
news:42E250C7-D585-4E67-9815-F74B911D3A4F@microsoft.com...

> It seems that stored usernames and passwords no longer works in Vista (XP
> works fine).
>
> We use this feature to connect to SQL Servers using a particular UID/PW
> combination so we dont have to use clear text authentication (i.e. SQL
> Server Auth).
>
> On XP we could create a wildcard domain and UID/PW and save it in "stored
> user names and password" then the user could use for example iSQL or
> Enterprise Manager to connect to the server via windows authentication.
>
> If I try this with Vista it either sends my current domain id/pw OR (if
> the machine is not in a domain) it seems to send NULL instead.
>
> Anyone have any ideas on what/where something might be adjusted to fix
> this issue ???

Yes me too...same situation and same problem...but no solution.. :-(

"WayCool" wrote:

> It seems that stored usernames and passwords no longer works in Vista (XP
> works fine).
>
> We use this feature to connect to SQL Servers using a particular UID/PW
> combination so we dont have to use clear text authentication (i.e. SQL
> Server Auth).
>
> On XP we could create a wildcard domain and UID/PW and save it in "stored
> user names and password" then the user could use for example iSQL or
> Enterprise Manager to connect to the server via windows authentication.
>
> If I try this with Vista it either sends my current domain id/pw OR (if
> the machine is not in a domain) it seems to send NULL instead.
>
> Anyone have any ideas on what/where something might be adjusted to fix this
> issue ???
>

I too am experiencing this problem and really would like a solution.

As a consultant who's laptop is never homed to a domain, this causes me no
end of headaches. XP's feature was a great help to those of us who roam
between domains. I personally can't see this as a security breach as it will
only work if you already have valid credentials on the domain in the first
place. And since you can store Logins/Passwords for any machine on the
domain anyway, it really is just an improved management feature.

Microsoft please restore this feature and explain why it was considered such
a security hole that needed to be removed in the first place. Or at least
give us a chance to say why you need to bring this back.

Thnx
TED


"Emiliano" <Emiliano@discussions.microsoft.com> wrote in message
news:C55C6C1E-9867-42CE-9E39-1F9533E79727@microsoft.com...

> Yes me too...same situation and same problem...but no solution.. :-(
>
> "WayCool" wrote:
>

Having the same issue. Have had to use a very awkward workaround for our new
batch of students (*.domain) thats going to cause a few headaches down the
line. Would be nice to have domain\* back, or at least an alternative.

"WayCool" wrote:

> It seems that stored usernames and passwords no longer works in Vista (XP
> works fine).
>
> We use this feature to connect to SQL Servers using a particular UID/PW
> combination so we dont have to use clear text authentication (i.e. SQL
> Server Auth).
>
> On XP we could create a wildcard domain and UID/PW and save it in "stored
> user names and password" then the user could use for example iSQL or
> Enterprise Manager to connect to the server via windows authentication.
>
> If I try this with Vista it either sends my current domain id/pw OR (if
> the machine is not in a domain) it seems to send NULL instead.
>
> Anyone have any ideas on what/where something might be adjusted to fix this
> issue ???
>