Hi
I just installed MSDE over my Windows 2003 box and facing an small problem.
I installed it with SQL security mode and also set a password for user "sa".
Everything looks just fine using "osql" as it uses local address.
But I can't connect to my server from another computer using VS.NET Server Explorer.
It seems as MSDE is set to reject connections from outside by default.
My question is how to enable it so I can connect using my "sa" account.
Appreciate your help in advance.OK. are you trying to connect by IP address or server name? do you have a firewall installed?|||Since I am connecting from outside of the server, I am using IP address.
And also I don't have any firewall installed.|||at a guess I'd say you have only windows authentication enabled. not 100% sure how to change that in MSDE, but I'll scout around and see.
Showing posts with label password. Show all posts
Showing posts with label password. Show all posts
Friday, March 23, 2012
Remote(over a network) Database Connection Issue
This has to be an easy question.
WORK2 - My workstation (xp pro)
WORK3 - Location of SQL Express 2005
WORK3\COMPANY
sa,password
WORK3 is a XPPro, both WORK2 and 3 have full admin rights to their machines and the network, I am using SQL Authentication (sa, password)
I have used the SQL Server Config app to enable the 4 Protocols, then restarted service. I can connect locally to my database via "SQL Server Management Studio Express", and through my VB application. I have checked "allow remote connections" in the database properties.
I do not know what i am missing? any thoughts?
Thanks in Advance
Are
you using a connection string? which is?|||Are you using a connection string? which is?
|||My VB6 connectionstring is:
This works PERFECT when the data souce is a local SQL Express Database
mstrProvider = "SQLNCLI.1" 'SQL Server 2005 Express
mstrPassword ="password"
mstrDataSource =<my database name>
goSQLDataSource= "WORK/SQLSERVER"
ConnectString = "Provider=" & mstrProvider & ";" & _
"Persist Security Info= False" & ";" & _
"Integrated Security=SSPI" & ";" & _
"User ID=sa" & ";" & _
"Password=" & mstrPassword & ";" & _
"Initial Catalog=" & mstrDataSource & ";" & _
"Data Source=" & goSQLDataSource
When i use the SS Management Studio i cant connect to a remote SQL Server even though the allow remote connection is enbled.
|||How is your authentication mode? if you are using a sql logins like a "sa", the authentication mode must be "sql server and windows authen....."
|||are you refering to this?
"Integrated Security=SSPI" & ";" & _
I am always going to use SQL Authentication...Local or remote.
When I use SSMS i have to change it from Windows Auth to SQL b/c it doesnt let you enter a password if you are using Windows.
Does that answer your question?
|||Sorry, when I told verify the authentication mode I mean on the SQLserver configuration properties.
|||Verify the authentication mode on <INSTANCE>\properties\security\server authentication...
|||The option button is select for "SQL Server and Windows Authentication mode" under the Server Properties/security
|||Why does Microsoft have to be so difficult? lol...sorry just venting|||
Verify this other one option <INSTANCE>\properties\connections\"alow remote connection s to this server"
Maximum number of concurrent connections=0
Use query gov. = unchecked
default connection options= all unchecked
allow remote connections to this server=checked
remote query timeout=0
require distrubited transactions=unchecked
Configured values=selected
sqlTuesday, March 20, 2012
Remote server configuration
hi,
can u help me in configuring a remote server using client-network utility
I got the username, password and the IP address of the server.
regards
In client network utility, you may have to add a TCP/IP alias, if the remote server cannot be reached directly by name.
Then use sp_addlinkedserver, and sp_addlinkedsrvlogin to create a linked server. See SQL Server Books Online for more information and examples.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Aneesh" <aneesh.r@.eostek.com> wrote in message news:OncMDTJlEHA.1652@.TK2MSFTNGP09.phx.gbl...
hi,
can u help me in configuring a remote server using client-network utility
I got the username, password and the IP address of the server.
regards
can u help me in configuring a remote server using client-network utility
I got the username, password and the IP address of the server.
regards
In client network utility, you may have to add a TCP/IP alias, if the remote server cannot be reached directly by name.
Then use sp_addlinkedserver, and sp_addlinkedsrvlogin to create a linked server. See SQL Server Books Online for more information and examples.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Aneesh" <aneesh.r@.eostek.com> wrote in message news:OncMDTJlEHA.1652@.TK2MSFTNGP09.phx.gbl...
hi,
can u help me in configuring a remote server using client-network utility
I got the username, password and the IP address of the server.
regards
Friday, March 9, 2012
Remote logins for SQL 2000?
Hi all,
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:
>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:
>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter
Remote logins for SQL 2000?
Hi all,
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:
>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:
>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter
Remote Laptop SA Password
Hi All,
We have remote users using sql server 7 on laptops. They use a vb app and replicate with the main server.
I have just discovered they have weak passwords on their sa account.
Others are suggesting that the laptops do not need strong passwords for their sa account as they are only subscribers . Are they talking rubbish?
Thanks,
JJCYou may want to give a look at the article in BOL about xp_cmdshell. Basically, if a dba (or many programmers for that matter) can get your sa password, that dba/programmer can own your laptop. There was a virus that searched the internet for SQL Servers that had no sa password, and it was shockingly effective.
If the laptops are only subscribers, and you do not allow anonymous pull subscriptions, you should be ok at the central server, but those laptops really should have their security beefed up.|||END USERS SHOULD NOT BE USING SA ACCOUNTS!
Even DBAs shouldn't be using the SA account!
Even System Administrators should not use the SA account! They should set up an account that grants themselves only the permissions necessary to do their day-to-day tasks, and only log in as SA when absolutely necessary. Otherwise, sooner or later you WILL do something you wish that you hadn't. Don't think of user accounts as restricitions. Think of them as safeguards!
Give all your users SQL logins or NT logins, and then change your sa password.
blindman|||If possible, set your users' laptops to Windows Authentication only. This way you'll come out clean without having to remember each laptop's SA password, or having to create a user on each laptop.
We have remote users using sql server 7 on laptops. They use a vb app and replicate with the main server.
I have just discovered they have weak passwords on their sa account.
Others are suggesting that the laptops do not need strong passwords for their sa account as they are only subscribers . Are they talking rubbish?
Thanks,
JJCYou may want to give a look at the article in BOL about xp_cmdshell. Basically, if a dba (or many programmers for that matter) can get your sa password, that dba/programmer can own your laptop. There was a virus that searched the internet for SQL Servers that had no sa password, and it was shockingly effective.
If the laptops are only subscribers, and you do not allow anonymous pull subscriptions, you should be ok at the central server, but those laptops really should have their security beefed up.|||END USERS SHOULD NOT BE USING SA ACCOUNTS!
Even DBAs shouldn't be using the SA account!
Even System Administrators should not use the SA account! They should set up an account that grants themselves only the permissions necessary to do their day-to-day tasks, and only log in as SA when absolutely necessary. Otherwise, sooner or later you WILL do something you wish that you hadn't. Don't think of user accounts as restricitions. Think of them as safeguards!
Give all your users SQL logins or NT logins, and then change your sa password.
blindman|||If possible, set your users' laptops to Windows Authentication only. This way you'll come out clean without having to remember each laptop's SA password, or having to create a user on each laptop.
Subscribe to:
Posts (Atom)