Before I just manage the SQL serve in LAN.
Right now i have a SQL server on internet I want to Remote manage
Can I still use QA and Enterprise Manager ?Yes, you can use Query Analyzer and SQL Enterprise Manager to manage a server that is open to the Internet. I would consider making an exception at your firewall to allow that server to remain part of your NT domain, so that you can use NT Authentication instead of SQL Authentication.
-PatP|||how can I set some config on my Enterprise manager or QA?|||Huh? I don't understand what you are asking.
-PatP|||Sorry about confuse,
I dont have this kind of experience. Before i just install client software like
QA or Enterprise in my PC ,i can use this software manage my SQL Server on LAN.
Right now another SQL server on WAN ,i dont know can i use QA to find
SQL server or I have to get some remote software to log on remote server
and use remote server's QA?
Do i make me clearly?|||Now I understand the question better!
When you are making the connection to the server in Query Analyzer, type either the server's name or IP address into the box labled SQL Server. Except for the lack of ability to enumerate remote servers (having Query Analyzer locate the SQL Servers and provide a list of them for you), the connection process is exactly the same as a "local" SQL Server.
-PatP
Showing posts with label lan. Show all posts
Showing posts with label lan. Show all posts
Friday, March 9, 2012
Saturday, February 25, 2012
Remote connection to MSDE
I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
Any ideas?
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?
|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?
|||Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.
|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
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
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegr oups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
Any ideas?
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?
|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?
|||Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.
|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
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
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegr oups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>
Remote connection to MSDE
I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server do
es not
exist or access denied.
Any ideas?I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?|||Yes. It's a named instance (SHAREPOINT). I can connect locally.|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>Yes. It's a named instance (SHAREPOINT). I can connect locally.|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
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
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>|||somebody on this forum "sameer" gave me a clue that
1433 is not listened on due to the "slammer" virus requiring SP1 for SQL
Server 2005...I am just begiing on this so what do I know
"Roger Wolter[MSFT]" wrote:
> If it is indeed WMSDE, it only supports local connections so it will never
> listen on a port. WMSDE is an OS component that can only be connected to
by
> selected Microsoft software running locally.
> --
> 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
> "laurin1" <laurin1@.osai.com> wrote in message
> news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>
>
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server do
es not
exist or access denied.
Any ideas?I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?|||Yes. It's a named instance (SHAREPOINT). I can connect locally.|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:
>Yes. It's a named instance (SHAREPOINT). I can connect locally.|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
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
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>|||somebody on this forum "sameer" gave me a clue that
1433 is not listened on due to the "slammer" virus requiring SP1 for SQL
Server 2005...I am just begiing on this so what do I know
"Roger Wolter[MSFT]" wrote:
> If it is indeed WMSDE, it only supports local connections so it will never
> listen on a port. WMSDE is an OS component that can only be connected to
by
> selected Microsoft software running locally.
> --
> 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
> "laurin1" <laurin1@.osai.com> wrote in message
> news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>
>
Subscribe to:
Posts (Atom)