Can't connect from a vista client to SQL 2005 box,other machines work fine

Hey. I've a windows vista machine which can't connect to SQL 2005 box. Other machines which are lower than vista work fine. Also, vista box can connect to other SQL 2005 instances but can't connect to only one instance. But, I can connect to the instance fine from my XP box. Also, it's not a permissions issue. This user is an SA and can connect form some other machine. SQL 2005 box is at 2047 version right now. And, the user is able to connect to some other boxes which are also at 2047. Please help. Thank you

Add the account sepcifically to the SQL Server. When you connect from Vista (because of the UAC) it strips out your group SID from local admins, so SQL Server doesn't know who you are, and that's probably what is causing your issue. Add the user's account by name to the box.

If this post answers your question, make sure you mark it "answered" so others can find it quickly.

Thanks -

Buck Woody
http://www.buckwoody.com

Can't connect as SA through ODBC manager...why?

Hi All,
I can connect to my MSDE server by logging in as SA from the command line
but not through the ODBC manager utility in windows. I need to setup system
DSNs for a few applications but can't because they require I use SQL
authentication. When I reach that step in the ODBC manager I type in SA and
the password and hit next I get a 18456 "login failed for sa" error. My
server is in mixed mode (I checked the registry), the domain admins group has
login privilages to MSDE, I have no firewall active on any NICs, and none of
my passwords contain a semicolon. I have no clue what I'm missing here. Can
some one point me in the right direction or link me to a good article on how
to setup system dsns through the command line?
Thanks,
Prikly Pete Peterson
MSDE can only be used as the source of the data. It's not licensed to host
Reporting Services (as we discuss in our Reporting Services
book --www.sqlreportingservices.net). Chapter 2 (freely downloadable from
the site) explains why.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"ComfortablySAD" <ComfortablySAD@.discussions.microsoft.com> wrote in message
news:32E686BF-63A6-4DFF-9A7D-A00E8B6CAE09@.microsoft.com...
> Hi All,
> I can connect to my MSDE server by logging in as SA from the command line
> but not through the ODBC manager utility in windows. I need to setup
> system
> DSNs for a few applications but can't because they require I use SQL
> authentication. When I reach that step in the ODBC manager I type in SA
> and
> the password and hit next I get a 18456 "login failed for sa" error. My
> server is in mixed mode (I checked the registry), the domain admins group
> has
> login privilages to MSDE, I have no firewall active on any NICs, and none
> of
> my passwords contain a semicolon. I have no clue what I'm missing here.
> Can
> some one point me in the right direction or link me to a good article on
> how
> to setup system dsns through the command line?
> Thanks,
> Prikly Pete Peterson
sql

Cant Connect anymore

Need help. I changed my TCP connect port for SQL2005 to port 9601.
(ON THE SERVER..went into SQL Config manager >
SQL 2005 Net Config / TCPIP Properties
Changed TCP Port to 9601
Changed TCP PORT for IP2 section to 9601 where ip is 127.0.0.1
Changed TCP for IPAll section to 9601
Dynamic TCP Port was unchanged and remained blank..
Under SQL Config Manager > SQL Native Client Network
Changed TCP PORT to 9601
--
On my laptop went to
SQL Server Config manager
Changed TCP Port to 9601
under SQL Native Client /
Client Protocols / TCPIP..
REBOOTED EVERYONE..
I have a vb.net app, tried to access SQL DB and it failed, so I added the
new port (9601) in the connect
string, and then it worked, so I know the server port was changed to 9601.
However, can no longer connect VIA SQL 2005 Management STUDIO, says
An error has occ while establich connect... TCP Provider error: No
connection could be
made.. target machine actively refused it. Error #10061).
The vb.net app works with new port, why doesn't SQL Management studio?
Changed back to 1433 and everything works again. I've got to change the
port,
How can I and get SQL Management studio to work with a non default port?
Tried the Management studio on another machine.. same error, although vb.net
app connects fine under new port. This is crazy..
The server has an internet Ip address and I am accesing it via .com name (
in the vb.net app too)
( I tried the straight IP address, didn't work either)
Thanks BUCI stumbled across the answer, if I change the default port, I HAVE to create
an alias name and use it in the login box instead of the servername itself..
BUC
<Buc> wrote in message news:%23rm9$GUSGHA.4600@.TK2MSFTNGP11.phx.gbl...
> Need help. I changed my TCP connect port for SQL2005 to port 9601.
> (ON THE SERVER..went into SQL Config manager >
> SQL 2005 Net Config / TCPIP Properties
> Changed TCP Port to 9601
> Changed TCP PORT for IP2 section to 9601 where ip is 127.0.0.1
> Changed TCP for IPAll section to 9601
> Dynamic TCP Port was unchanged and remained blank..
> Under SQL Config Manager > SQL Native Client Network
> Changed TCP PORT to 9601
> --
> On my laptop went to
> SQL Server Config manager
> Changed TCP Port to 9601
> under SQL Native Client /
> Client Protocols / TCPIP..
> REBOOTED EVERYONE..
> I have a vb.net app, tried to access SQL DB and it failed, so I added the
> new port (9601) in the connect
> string, and then it worked, so I know the server port was changed to 9601.
> However, can no longer connect VIA SQL 2005 Management STUDIO, says
> An error has occ while establich connect... TCP Provider error: No
> connection could be
> made.. target machine actively refused it. Error #10061).
> The vb.net app works with new port, why doesn't SQL Management studio?
> Changed back to 1433 and everything works again. I've got to change the
> port,
> How can I and get SQL Management studio to work with a non default port?
> Tried the Management studio on another machine.. same error, although
> vb.net app connects fine under new port. This is crazy..
> The server has an internet Ip address and I am accesing it via .com name
> ( in the vb.net app too)
> ( I tried the straight IP address, didn't work either)
> Thanks BUC
>|||Sounds like you don't have the sqlbrowser service running. The browser
service maps incoming requests to the port where the database is listening
so without the sqlbrowser service running, you have to specify the port in
the connect string.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<Buc> wrote in message news:OzOFXlUSGHA.524@.TK2MSFTNGP10.phx.gbl...
>I stumbled across the answer, if I change the default port, I HAVE to
>create an alias name and use it in the login box instead of the servername
>itself..
> BUC
> <Buc> wrote in message news:%23rm9$GUSGHA.4600@.TK2MSFTNGP11.phx.gbl...
>

Can't connect after Windows XP SP2

Has i reviewed here after Windows XP SP2, MSDE has some problems conecctiong
over a network.
I installed SP3a for MSDE 2000 but the problem persists.
I put a permission to sqlserver.exe but my access to it over a network (and
internet) is blocked.
How can i solve this problem?
thanks,
Goncalo Boleo
hi,
"john raub" <john_raub@.ascendrms.com> ha scritto nel messaggio
news:20c601c4bdd8$f28b0840$a601280a@.phx.gbl
> problem with a customer that installed a 3rd party
> firewall software. He has since uninstalled, but we still
> can't connect to the machine containing the MSDE server.
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];884012
to see if they can help
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Can't connect after changing IP address

After changing from DHCP network address to a static IP address I can
not connect to my local database using ".\MyDBS" notation, howver
"127.0.0.1\MyDBS" works. Also, both work after restarting the SQL
service.
I am using the query analyzer to test success or failure.
My event logs show nothing and my SQL logs show no errors.
Any ideas on how to debug this further or solve it altogether?
Thank youHi Arron,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
From your information, after change the IP, in the Query Analyzer, you
could not connect to my local database using ".\MyDBS" while
"127.0.0.1\MyDBS" works. After you restart the SQL Server service, this
problem do not happen, right?
I want to go forward with some more information since I could not
re-produce this problem on my computer. Do you encouter any error message
when using ".\MYDBS" that indicating you cannot connect to the server? How
about using the '(local)'? If you do not restart the SQL Server service,
it will not connect to the server even after some time? If you connect from
another machine by Query Analyer, do you meet the same problem?
When a SQL Server is started, it will listen to the IP and the port of when
it is started. So, when you change the IP address, you should restart the
SQL Server service and then it will listen to the new IP address. For the
localhost and the 127.0.0.1 will be the local machine.
You could refer to the following article for the name resolution:
http://www.microsoft.com/technet/pr.../ewsa/ewsach08.
mspx#XSLTsection124121120120
Hope this helps. If you still have questions, please feel free to post
message here and I am glad to help.
Thanks.
Sincerely Yours
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Aaron,
I am reviewing you post and since we have not heard from you for some time
in the newsgroup, I wonder if you got answer from my answer. For any
question, please post your message here and we are glad to help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Can't connect after change the security setting

Hi, Experts! I very new to SQL server. I made a stupid movement by mistakenl
y
change the security of property of local(windows NT) from log in using this
account to system account. After the machine restarted, i can't no longer
start up SQL server. When I click local (window NT) in enterprise manager it
says "a connection could not be established to local. Reason, SQL serer
doesn't exist or access denied". I think it is the change of security that
the access was denied. How should I resolve this problem' Thanks so much.Thats weird, did the SQLServer service start up ? Look in the Service
manager. The service account can be switched in here. if you changed
the authentication method you can set it back via the registry entry as
mentioned in here:
---
http://support.microsoft.com/defaul...b;EN-US;q285097
---
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
---
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSq
lServer\LoginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
-URL---
HTH, Jens Suessmeyer.|||Jens,
Thank you so very much for your reply. I changed the registry loginmode from
2 to 1 and it did not work; I tried to change from 1 to 0, it did not work
either. In the service, I was not able to start up MSSQLSERVER. I got this
message "MSSQL SERVER service on local computer started and then stopped.
Some services stop automatically if they have no work to do ...".
Thanks.
"Jens" wrote:

> Thats weird, did the SQLServer service start up ? Look in the Service
> manager. The service account can be switched in here. if you changed
> the authentication method you can set it back via the registry entry as
> mentioned in here:
> ---
> http://support.microsoft.com/defaul...b;EN-US;q285097
> ---
> INF: How to Change the Default Login Authentication Mode to SQL While
> Installing SQL Server 2000 Desktop Engine by Using Windows Installer
> ---
> <snip>
> Another way to change the security mode after installation is to stop
> SQL Server and set the appropriate registry key for your installation:
>
> Default instance:
> HKLM\Software\Microsoft\MSSqlserver\MSSq
lServer\LoginMode
>
> Named instance:
> HKLM\Software\Microsoft\Microsoft SQL Server\Instance
> Name\MSSQLServer\LoginMode
>
> to 2 for mixed-mode or 1 for integrated. (Integrated is the default
> setup for the SQL Server 2000 Data Engine.)
> </snip>
>
> -URL---
>
> HTH, Jens Suessmeyer.
>|||Lokk in the event log to see why it failed, did you try to change the
service accoutn back to the original one in the service manager ?
Some error occured and you have to know which one, this information is
presented in the event log.
Jens Suessmeyer.|||Thank you Jens. You saved me. I was panic about it. It is the evaluation
period expired. We have license now. How can I update the license without
losing the data? If not doable it is ok too. Thanks. whew...
"Jens" wrote:

> Lokk in the event log to see why it failed, did you try to change the
> service accoutn back to the original one in the service manager ?
> Some error occured and you have to know which one, this information is
> presented in the event log.
> Jens Suessmeyer.
>|||http://support.microsoft.com/defaul...kb;en-us;281574
HTH, Jens Suessmeyer.|||Thank you so very much Jens. You are very helpful!!
"jsuessmeyer@.web.de" wrote:

> http://support.microsoft.com/defaul...kb;en-us;281574
> HTH, Jens Suessmeyer.
>

Can't connect after change the security setting

Hi, Experts! I very new to SQL server. I made a stupid movement by mistakenly
change the security of property of local(windows NT) from log in using this
account to system account. After the machine restarted, i can't no longer
start up SQL server. When I click local (window NT) in enterprise manager it
says "a connection could not be established to local. Reason, SQL serer
doesn't exist or access denied". I think it is the change of security that
the access was denied. How should I resolve this problem? Thanks so much.
Thats weird, did the SQLServer service start up ? Look in the Service
manager. The service account can be switched in here. if you changed
the authentication method you can set it back via the registry entry as
mentioned in here:
http://support.microsoft.com/default...;EN-US;q285097
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
-URL---
HTH, Jens Suessmeyer.
|||Jens,
Thank you so very much for your reply. I changed the registry loginmode from
2 to 1 and it did not work; I tried to change from 1 to 0, it did not work
either. In the service, I was not able to start up MSSQLSERVER. I got this
message "MSSQL SERVER service on local computer started and then stopped.
Some services stop automatically if they have no work to do ...".
Thanks.
"Jens" wrote:

> Thats weird, did the SQLServer service start up ? Look in the Service
> manager. The service account can be switched in here. if you changed
> the authentication method you can set it back via the registry entry as
> mentioned in here:
> http://support.microsoft.com/default...;EN-US;q285097
> INF: How to Change the Default Login Authentication Mode to SQL While
> Installing SQL Server 2000 Desktop Engine by Using Windows Installer
> <snip>
> Another way to change the security mode after installation is to stop
> SQL Server and set the appropriate registry key for your installation:
>
> Default instance:
> HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginMode
>
> Named instance:
> HKLM\Software\Microsoft\Microsoft SQL Server\Instance
> Name\MSSQLServer\LoginMode
>
> to 2 for mixed-mode or 1 for integrated. (Integrated is the default
> setup for the SQL Server 2000 Data Engine.)
> </snip>
>
> -URL---
>
> HTH, Jens Suessmeyer.
>
|||Lokk in the event log to see why it failed, did you try to change the
service accoutn back to the original one in the service manager ?
Some error occured and you have to know which one, this information is
presented in the event log.
Jens Suessmeyer.
|||Thank you Jens. You saved me. I was panic about it. It is the evaluation
period expired. We have license now. How can I update the license without
losing the data? If not doable it is ok too. Thanks. whew...
"Jens" wrote:

> Lokk in the event log to see why it failed, did you try to change the
> service accoutn back to the original one in the service manager ?
> Some error occured and you have to know which one, this information is
> presented in the event log.
> Jens Suessmeyer.
>
|||http://support.microsoft.com/default...b;en-us;281574
HTH, Jens Suessmeyer.
|||Thank you so very much Jens. You are very helpful!!
"jsuessmeyer@.web.de" wrote:

> http://support.microsoft.com/default...b;en-us;281574
> HTH, Jens Suessmeyer.
>
sql