Hello,
I need to create an ODBC DNS that points to a remote MSDE instance, but I
can only get it to work if I turn Windows Firewall off. Both the local and
remote machines are WinXP SP2 and have SQL2000 and MSDE, same domain and I
can login as the same person on each machine.
On the remote machine I've enabled TCP/IP and the default port, and I've
added that port to the firewall, but when I try to add a DSN (on the local
machine) in the ODBC control panel it says
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
I've looked at the instance via Enterprise Manager and my domain login has
admin privs, and can connect a DSN to the SQL2000 server on that machine.
Stumped.
Suggestions?
Keith
hi Keith,
Keith wrote:
> Hello,
> I need to create an ODBC DNS that points to a remote MSDE instance,
> but I can only get it to work if I turn Windows Firewall off. Both
> the local and remote machines are WinXP SP2 and have SQL2000 and
> MSDE, same domain and I can login as the same person on each machine.
> On the remote machine I've enabled TCP/IP and the default port, and
> I've added that port to the firewall, but when I try to add a DSN (on
> the local machine) in the ODBC control panel it says
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
> exist or access denied.
> I've looked at the instance via Enterprise Manager and my domain
> login has admin privs, and can connect a DSN to the SQL2000 server on
> that machine.
did you define an exception on the server's firewall on the MSDE used TCP/IP
port or on the service itself?
http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||>
> did you define an exception on the server's firewall on the MSDE used
> TCP/IP port or on the service itself?
> http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
> http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Well, after some reboots and a walk around the block it works now.
I finally got it to work either with firewall port exception, or a service
exception, but neither way seemed very consistent. Making changes to the
firewall while it is running just doesn't seem to work that well; perhaps I
wasn't waiting long enough for the changes to propagate or I just need to
stop/start the firewall after changing something.
And I suspect that some of the changes that don't "require" rebooting really
do.
Anyway, thanks for the quick response and support links.
Keith
Showing posts with label firewall. Show all posts
Showing posts with label firewall. Show all posts
Saturday, February 25, 2012
Friday, February 24, 2012
Can't connect to SQL server in Windows XP SP2
Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris Pankhurst
Sometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>
|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com... [vbcol=seagreen]
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL
>
|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com.. .
>is
>This
>SQL
>
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris Pankhurst
Sometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>
|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com... [vbcol=seagreen]
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL
>
|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.4ax.com.. .
>is
>This
>SQL
>
Can't connect to SQL server in Windows XP SP2
Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris PankhurstSometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
>
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL[vbcol=seagreen]
>|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
>is
>This
>SQL
>
set to windows or sql authentication. I believe I opened them with the
correct TCP/UDP combination. I also told windows firewall about
sqlserver.exe, however I suspect that is more for outbound connections.
I understand the security reasons why the normal error message has to be
vague about sql server does not exist or access denied. Is it possible to
configure SQL server into a diagnostic mode where it will tell the client
that the sql server does exist but it was just that access was denied? This
would help me narrow down the problem.
If not, how can I tell if it is networking/firewall type problem or an SQL
server security problem?
Chris PankhurstSometimes you can tell from the full text of the error
messages. You could turn on failed login auditing to see if
the login is hitting the server and failing. You can also
monitor for login failures in Profiler. You won't get a lot
of information on the login failure but enough to see if the
client is hitting the server.
-Sue
On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Yes, I opened the ports 1433 and 1434 in Windows Firewall and SQL server is
>set to windows or sql authentication. I believe I opened them with the
>correct TCP/UDP combination. I also told windows firewall about
>sqlserver.exe, however I suspect that is more for outbound connections.
>I understand the security reasons why the normal error message has to be
>vague about sql server does not exist or access denied. Is it possible to
>configure SQL server into a diagnostic mode where it will tell the client
>that the sql server does exist but it was just that access was denied? This
>would help me narrow down the problem.
>If not, how can I tell if it is networking/firewall type problem or an SQL
>server security problem?
>Chris Pankhurst
>|||Thanks, I'm not sure how to turn on login auditing, but using profiler is a
good idea. I wonder why I didn't think of it.
Chris Pankhurst
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
> Sometimes you can tell from the full text of the error
> messages. You could turn on failed login auditing to see if
> the login is hitting the server and failing. You can also
> monitor for login failures in Profiler. You won't get a lot
> of information on the login failure but enough to see if the
> client is hitting the server.
> -Sue
> On Fri, 23 Sep 2005 12:01:20 +1200, "Christopher Pankhurst"
> <christopher_pankhurst@.hotmail.com> wrote:
>
is[vbcol=seagreen]
This[vbcol=seagreen]
SQL[vbcol=seagreen]
>|||For login audits, in Enterprise Manager, right click on the
server and select properties. Go to the Security tab and you
can set the audit level for logins (success, failure or
all). You need to restart the service for the settings to
take effect.
-Sue
On Mon, 26 Sep 2005 08:32:32 +1200, "Christopher Pankhurst"
<christopher_pankhurst@.hotmail.com> wrote:
>Thanks, I'm not sure how to turn on login auditing, but using profiler is a
>good idea. I wonder why I didn't think of it.
>Chris Pankhurst
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:u257j19kdbt8s946sb7mu633v2nm1tb8el@.
4ax.com...
>is
>This
>SQL
>
Thursday, February 16, 2012
Can't Connect to SQL 2005 Using Remote Desktop and Local Administr
I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to the
server (no firewall involved) using Remote Desktop, I can't login to
Management Studio using the local administrator account. However, I can log
in using the domain administrator account. The local administrator account i
s
not locked out. I get the following error when trying to access Management
Studio using the local admin. account:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (.Net SqlClient Data Provider)
Any ideas?***UPDATE***
Actually, it has nothing to do with remote connectivity. I tried to log in
to Management Studio locally as the local administrator, and it still
wouldn't let me and gave the same error. As mentioned previously, the domain
admin. works.
Thanks.
"Marks70" wrote:
> I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to th
e
> server (no firewall involved) using Remote Desktop, I can't login to
> Management Studio using the local administrator account. However, I can lo
g
> in using the domain administrator account. The local administrator account
is
> not locked out. I get the following error when trying to access Management
> Studio using the local admin. account:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (.Net SqlClient Data Provider)
> Any ideas?
server (no firewall involved) using Remote Desktop, I can't login to
Management Studio using the local administrator account. However, I can log
in using the domain administrator account. The local administrator account i
s
not locked out. I get the following error when trying to access Management
Studio using the local admin. account:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (.Net SqlClient Data Provider)
Any ideas?***UPDATE***
Actually, it has nothing to do with remote connectivity. I tried to log in
to Management Studio locally as the local administrator, and it still
wouldn't let me and gave the same error. As mentioned previously, the domain
admin. works.
Thanks.
"Marks70" wrote:
> I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to th
e
> server (no firewall involved) using Remote Desktop, I can't login to
> Management Studio using the local administrator account. However, I can lo
g
> in using the domain administrator account. The local administrator account
is
> not locked out. I get the following error when trying to access Management
> Studio using the local admin. account:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (.Net SqlClient Data Provider)
> Any ideas?
Tuesday, February 14, 2012
Can't connect to server - real newbie here
SLQ 2000, Win XP Pro network
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!
Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!
Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
Can't connect to server - real newbie here
SLQ 2000, Win XP Pro network
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> > SLQ 2000, Win XP Pro network
> >
> > I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> > turned off)
> >
> > The SQL server seems to be running fine in that I can access the
> > default tables from the local computer. The problem is, I can't
> > connect to the SLQ Server from another XP Pro client computer using
> > Enterprise Manager. That is, I can't register it. I get a "server
> > does not exist" error.
> >
> > I've tried both Windows authentication and SQL Server authentication.
> > To use SQL auth. I'm assuming that all I have to do is create a new
> > login on the server, which I have done. I've made sure this login is
> > an administrator with ownership and public rights to each database.
> >
> > What else should I check or setup?
> >
> > All help greatly appreciated!!
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> > SLQ 2000, Win XP Pro network
> >
> > I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> > turned off)
> >
> > The SQL server seems to be running fine in that I can access the
> > default tables from the local computer. The problem is, I can't
> > connect to the SLQ Server from another XP Pro client computer using
> > Enterprise Manager. That is, I can't register it. I get a "server
> > does not exist" error.
> >
> > I've tried both Windows authentication and SQL Server authentication.
> > To use SQL auth. I'm assuming that all I have to do is create a new
> > login on the server, which I have done. I've made sure this login is
> > an administrator with ownership and public rights to each database.
> >
> > What else should I check or setup?
> >
> > All help greatly appreciated!!
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
can't connect to remote sql server with SBS 2003
Hi,
I can't make a connection to my host's sql server via EM on a SBS 2003
server.
I suspect this is because of the firewall.
Any help appreciated!
many thanks
NEIL
In news:d35nil$1e8$1$8300dec7@.news.demon.co.uk,
Neil Jarman <neil@.tNOiSPAMvPLEASEy.co.uk> wrote:
> I can't make a connection to my host's sql server via EM on a SBS 2003
> server.
> I suspect this is because of the firewall.
You need to ask the host what IP and Port his SQL server is running.
Maritte Knap - MVP
http://www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53
|||On Fri, 08 Apr 2005 11:43:15 +0100, Neil Jarman wrote:
> Hi,
> I can't make a connection to my host's sql server via EM on a SBS 2003
> server.
> I suspect this is because of the firewall.
I would hope so - exposing the SQL management ports to the public is just
plain stupid when it comes to management or security. If they have any
brains they will only allow EM through a secure (VPN) connection or a IP
to IP connection, not just exposed with a password.
spam999free@.rrohio.com
remove 999 in order to email me
I can't make a connection to my host's sql server via EM on a SBS 2003
server.
I suspect this is because of the firewall.
Any help appreciated!
many thanks
NEIL
In news:d35nil$1e8$1$8300dec7@.news.demon.co.uk,
Neil Jarman <neil@.tNOiSPAMvPLEASEy.co.uk> wrote:
> I can't make a connection to my host's sql server via EM on a SBS 2003
> server.
> I suspect this is because of the firewall.
You need to ask the host what IP and Port his SQL server is running.
Maritte Knap - MVP
http://www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53
|||On Fri, 08 Apr 2005 11:43:15 +0100, Neil Jarman wrote:
> Hi,
> I can't make a connection to my host's sql server via EM on a SBS 2003
> server.
> I suspect this is because of the firewall.
I would hope so - exposing the SQL management ports to the public is just
plain stupid when it comes to management or security. If they have any
brains they will only allow EM through a secure (VPN) connection or a IP
to IP connection, not just exposed with a password.
spam999free@.rrohio.com
remove 999 in order to email me
Subscribe to:
Posts (Atom)