I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.
Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
Showing posts with label laptop. Show all posts
Showing posts with label laptop. Show all posts
Monday, March 19, 2012
Odd authentication issues
I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
Odd authentication issues
I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
Wednesday, March 7, 2012
odbc sql native client
I've installed the SQL Server 2005 client utilities on a laptop that's used
for development. When I try to create an odbc connect to SQL Native Client
2005.90.1399.00 that specific driver doesn't appear in the list of drivers
available for selection. I've verified that it is in fact installed.
What's the problem, why doesn't it appear?
It's hard to say where exactly you are seeing this issue but
I would guess you are trying to create a DSN using the SQL
Native Client. Try updating your MDAC and verify that the
MDAC installation is correct on the laptop. You can check
the MDAC installation using component checker. You can
download component checker as well as the latest MDAC
versions from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 24 Jul 2007 09:12:01 -0700, gracie
<gracie@.discussions.microsoft.com> wrote:
>I've installed the SQL Server 2005 client utilities on a laptop that's used
>for development. When I try to create an odbc connect to SQL Native Client
>2005.90.1399.00 that specific driver doesn't appear in the list of drivers
>available for selection. I've verified that it is in fact installed.
>What's the problem, why doesn't it appear?
>
>
|||I have a similar issue with one desktop in our office. The SQL Native
Client doesn't appear in the ODBC list when opening up "User DSN".
Nothing seems to be different on this system from the 20 others that
it does appear on. MDAC is the latest one also. Have any other ideas
of what I might look for?
Sue Hoegemeier wrote:[vbcol=seagreen]
> It's hard to say where exactly you are seeing this issue but
> I would guess you are trying to create a DSN using the SQL
> Native Client. Try updating your MDAC and verify that the
> MDAC installation is correct on the laptop. You can check
> the MDAC installation using component checker. You can
> download component checker as well as the latest MDAC
> versions from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> -Sue
> On Tue, 24 Jul 2007 09:12:01 -0700, gracie
> <gracie@.discussions.microsoft.com> wrote:
for development. When I try to create an odbc connect to SQL Native Client
2005.90.1399.00 that specific driver doesn't appear in the list of drivers
available for selection. I've verified that it is in fact installed.
What's the problem, why doesn't it appear?
It's hard to say where exactly you are seeing this issue but
I would guess you are trying to create a DSN using the SQL
Native Client. Try updating your MDAC and verify that the
MDAC installation is correct on the laptop. You can check
the MDAC installation using component checker. You can
download component checker as well as the latest MDAC
versions from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 24 Jul 2007 09:12:01 -0700, gracie
<gracie@.discussions.microsoft.com> wrote:
>I've installed the SQL Server 2005 client utilities on a laptop that's used
>for development. When I try to create an odbc connect to SQL Native Client
>2005.90.1399.00 that specific driver doesn't appear in the list of drivers
>available for selection. I've verified that it is in fact installed.
>What's the problem, why doesn't it appear?
>
>
|||I have a similar issue with one desktop in our office. The SQL Native
Client doesn't appear in the ODBC list when opening up "User DSN".
Nothing seems to be different on this system from the 20 others that
it does appear on. MDAC is the latest one also. Have any other ideas
of what I might look for?
Sue Hoegemeier wrote:[vbcol=seagreen]
> It's hard to say where exactly you are seeing this issue but
> I would guess you are trying to create a DSN using the SQL
> Native Client. Try updating your MDAC and verify that the
> MDAC installation is correct on the laptop. You can check
> the MDAC installation using component checker. You can
> download component checker as well as the latest MDAC
> versions from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> -Sue
> On Tue, 24 Jul 2007 09:12:01 -0700, gracie
> <gracie@.discussions.microsoft.com> wrote:
Subscribe to:
Posts (Atom)