connect from ASP app: remotely

Showing posts with label remotely. Show all posts

Tuesday, March 27, 2012

Can't get connected to MSDE Remotely

I have a problem getting connected to an instance of MSDE remotely. I can
register the instance in Enterprise Manager, and work with it locally on the
machine it is installed on but cannot get connected remotely. I get the
famous SQL Server does not exist or access is denied.
It is a named instance.
The security mode is set to SQL.
Network Protocols are enabled.
netstat tells me that it is listening on the correct port.
I'm logging in remotely as sa with the correct password.
Any help here would be appreciated.
Also for some reason the name of the server doesn't show up in the list in
Enterprise manager on the remote machine when trying to register the server.
I typed in the name of the server, the sa login and password, but still the
same error. Server doesn't exist or access is denied.
"jdehne" wrote:

> I have a problem getting connected to an instance of MSDE remotely. I can
> register the instance in Enterprise Manager, and work with it locally on the
> machine it is installed on but cannot get connected remotely. I get the
> famous SQL Server does not exist or access is denied.
> It is a named instance.
> The security mode is set to SQL.
> Network Protocols are enabled.
> netstat tells me that it is listening on the correct port.
> I'm logging in remotely as sa with the correct password.
> Any help here would be appreciated.
|||I have also tried adding the alias with the same port as MSDE is configured.
"jdehne" wrote:
[vbcol=seagreen]
> Also for some reason the name of the server doesn't show up in the list in
> Enterprise manager on the remote machine when trying to register the server.
> I typed in the name of the server, the sa login and password, but still the
> same error. Server doesn't exist or access is denied.
> "jdehne" wrote:
|||i have also noticed that when running osql -L on the remote machine the MSDE
instance does not show up.
"jdehne" wrote:
[vbcol=seagreen]
> I have also tried adding the alias with the same port as MSDE is configured.
> "jdehne" wrote:
|||Am Mon, 17 Oct 2005 15:06:03 -0700 schrieb jdehne:
[vbcol=seagreen]
> i have also noticed that when running osql -L on the remote machine the MSDE
> instance does not show up.
> "jdehne" wrote:
I can only guess:
a) TCP is enabled on the server but not on the client
b) connect doesn't work with servername but with server-IP
c) MDAC's are different versions
bye,
Helmut
|||hi,
jdehne wrote:
> i have also noticed that when running osql -L on the remote machine
> the MSDE instance does not show up.
try having a look at http://support.microsoft.com/kb/841251/en-us ,
http://support.microsoft.com/kb/841249/en-us
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I managed to figure it out. SP2 Secruity center was blocking the port and I
had add the sqlserver.exe to the list of programs that can get through the
firewall.
"Andrea Montanari" wrote:

> hi,
> jdehne wrote:
> try having a look at http://support.microsoft.com/kb/841251/en-us ,
> http://support.microsoft.com/kb/841249/en-us
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

Friday, February 24, 2012

Can't connect via HTTP remotely...

Hello-

I've just set up HTTP Access to SSAS and can connect locally, but when trying to connect remotely, as the same domain user, I receive the message:

The connection either timed out or was lost

Unable to connect to the remote server

No connection could be made because the target machine actively refused it

I can connect remotely if I connect using just the servername (rather than http://...)

Anyone else runinto this one?

Hi Tristan,

For troubleshooting connectivity problems, one great resource is Edward's blog at: http://www.sqljunkies.com/WebLog/edwardm/.

If you still have connectivity issues after following the guidelines described in this blog, please let us know and give more details.

Hope this helps,

Artur

Thursday, February 16, 2012

Can't connect to SQL

Hello,
We just installed SQL 2000 on a remote server. We can't connect to SQL
remotely from a desktop PC. When we try to register the SQL server in
Enterprise Mgr. we get the error:
"Client unable to establish connection. Named Pipes Provider: The network
path was not found. Timeout expired."
I checked the protocols on the SQL server and there is: TCP/IP and Named
Pipes (the default), so I disabled Named Pipes, but the error still occurs.
Anyone know what might be the problem?
Thanks!What Network Operating System (NOS) are you running?
What service packs have been applied?
Are both servers in the same domain?
Do you have to go through a firewall?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>|||Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to SQL
> > remotely from a desktop PC. When we try to register the SQL server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and Named
> > Pipes (the default), so I disabled Named Pipes, but the error still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0063_01C4ABE6.48846340
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Does the client PC list the sqlserver when you try to register it or you =type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to =SQL
> > remotely from a desktop PC. When we try to register the SQL server =in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and =Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_0063_01C4ABE6.48846340
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).There is no firewall on the SQL server (not supposed to be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same =domain?> Do you have to go through a firewall?>> More information =would be helpful.>> Rick Sawtell> MCT, MCSD, MCDBA>>>> "Dean J Garrett" wrote in message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 on a =remote server. We can't connect to SQL> > remotely from a desktop =PC. When we try to register the SQL server in> > Enterprise Mgr. we =get the error:> >> > "Client unable to establish =connection. Named Pipes Provider: Thenetwork> > path was not found. =Timeout expired."> >> > I checked the protocols on the SQL =server and there is: TCP/IP and Named> > Pipes (the default), so I =disabled Named Pipes, but the error still> occurs.> > Anyone =know what might be the problem?> >> > Thanks!> =>> >>>

--=_NextPart_000_0063_01C4ABE6.48846340--|||This is a multi-part message in MIME format.
--=_NextPart_000_007F_01C4ABDA.3DAB8E50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows =validation, then you need to ensure that your workstation is trusted by =the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit =out of my element on this one), but you may need to set up some type of =Share on the W2k3 server so that the pipe is able to connect to the =server.
Hope this helps, maybe someone with some additional insight can be of =service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message =news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect =to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_007F_01C4ABDA.3DAB8E50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Sounds like a security issue to me. =
Are you using SQL validation or Windows =validation? If Windows validation, then you need to ensure that your workstation is =trusted by the W2k3 server's DC.
If you are trying to connect through a named =pipe, then umm. (I'm a bit out of my element on this one), but you may need =to set up some type of Share on the W2k3 server so that the pipe is able to =connect to the server.
Hope this helps, maybe someone with =some additional insight can be of service on this one.
Rick
"TJ" wrote in message news:eY%23g28ArEHA.=1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).There is no firewall on the SQL server (not supposed to be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same domain?> Do you have to go through a =firewall?>> More information would be helpful.>> Rick Sawtell> =MCT, MCSD, MCDBA>>>> "Dean J Garrett" wrote in message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 on =a remote server. We can't connect to SQL> > remotely from a desktop =PC. When we try to register the SQL server in> > Enterprise =Mgr. we get the error:> >> > "Client unable to establish = connection. Named Pipes Provider: Thenetwork> > path =was not found. Timeout expired."> >> > I checked the =protocols on the SQL server and there is: TCP/IP and Named> > Pipes =(the default), so I disabled Named Pipes, but the error still> occurs.> > Anyone know what might be the problem?> >> > Thanks!> >> >>>

--=_NextPart_000_007F_01C4ABDA.3DAB8E50--|||Can you ping the server from the client?
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>|||This is a multi-part message in MIME format.
--=_NextPart_000_00BC_01C4AC60.FF9D8E10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello, when I try to register the remote SQL Server, it does not list it =in the pull-down because I'm using a workstation in an office, and the =SQL Server is a machine in an ISPs data center across the country. =Instead, I type in the IP address for the remote SQL box, and then enter =SQL authentication that works fine when I'm using the SQL Server =directly (via remote desktop). The SQL registration process fails due to =the error:
"Client unable to establish connection. Named pipes provider: The =network path was not found. Time-out expired."
Any clues?
"TJ" <tunj@.hotmail.com> wrote in message =news:eY#g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect =to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_00BC_01C4AC60.FF9D8E10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Hello, when I try to register the =remote SQL Server, it does not list it in the pull-down because I'm using a =workstation in an office, and the SQL Server is a machine in an ISPs data center across =the country. Instead, I type in the IP address for the remote SQL box, and =then enter SQL authentication that works fine when I'm using the SQL Server =directly (via remote desktop). The SQL registration process fails due to the error:
"Client unable to establish connection. =Named pipes provider: The network path was not found. Time-out =expired."
Any clues?
"TJ" wrote in message news:eY#g28ArEHA.1644=@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).There is no firewall on the SQL server (not supposed to be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same domain?> Do you have to go through a =firewall?>> More information would be helpful.>> Rick Sawtell> =MCT, MCSD, MCDBA>>>> "Dean J Garrett" wrote in message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 on =a remote server. We can't connect to SQL> > remotely from a desktop =PC. When we try to register the SQL server in> > Enterprise =Mgr. we get the error:> >> > "Client unable to establish = connection. Named Pipes Provider: Thenetwork> > path =was not found. Timeout expired."> >> > I checked the =protocols on the SQL server and there is: TCP/IP and Named> > Pipes =(the default), so I disabled Named Pipes, but the error still> occurs.> > Anyone know what might be the problem?> >> > Thanks!> >> >>>

--=_NextPart_000_00BC_01C4AC60.FF9D8E10--|||This is a multi-part message in MIME format.
--=_NextPart_000_00C8_01C4AC61.6F469B80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello, the SQL Server 2000 installation uses Mixed authentication, SQL =and Windows. When I try to register the SQL Server remotely from my =desktop, I enter SQL username/password. This always worked in the past =with other SQL servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use =only TCP/IP. As a suggestion by another newsgroup member, I disabled =Name Pipes completely on the remote SQL server, but I still get the =error message below:
"Client unable to establish connection. Named pipes provider: The =network path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message =news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows =validation, then you need to ensure that your workstation is trusted by =the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a =bit out of my element on this one), but you may need to set up some type =of Share on the W2k3 server so that the pipe is able to connect to the =server.
Hope this helps, maybe someone with some additional insight can be =of service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message =news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't =connect to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_00C8_01C4AC61.6F469B80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Hello, the SQL Server 2000 installation =uses Mixed authentication, SQL and Windows. When I try to register the SQL Server =remotely from my desktop, I enter SQL username/password. This always worked in =the past with other SQL servers.
I don't know if I'm trying to use named =pipes, in fact I'd rather use only TCP/IP. As a suggestion by another newsgroup =member, I disabled Name Pipes completely on the remote SQL server, but I still get =the error message below:
"Client unable to establish connection. =Named pipes provider: The network path was not found. Timeout expired."
Any clues?
"Rick Sawtell" =wrote in message news:#3KkuSBrEHA.332@.T=K2MSFTNGP14.phx.gbl...
Sounds like a security issue to me. =
Are you using SQL validation or Windows validation? If Windows validation, then you need to ensure that =your workstation is trusted by the W2k3 server's DC.

If you are trying to connect through a named =pipe, then umm. (I'm a bit out of my element on this one), but you may need =to set up some type of Share on the W2k3 server so that the pipe is able to =connect to the server.

Hope this helps, maybe someone =with some additional insight can be of service on this one.

Rick

"TJ" wrote in message news:eY%23g28ArEHA.=1644@.tk2msftngp13.phx.gbl...
Does the client PC list the =sqlserver when you try to register it or you type it in?
"Dean J Garrett" wrote in =message news:e1vxB2#qEHA.1644=@.tk2msftngp13.phx.gbl...Rick,The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).There is no firewall on the SQL server (not supposed to =be). The server anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" wrote in messagenews:ushY2w#qEHA.2340=@.TK2MSFTNGP11.phx.gbl...> What Network Operating System (NOS) are you running?> What =service packs have been applied?> Are both servers in the same domain?> Do you have to go through a =firewall?>> More information would be helpful.>> Rick Sawtell> =MCT, MCSD, MCDBA>>>> "Dean J Garrett" = wrote in = message> news:u14$po%23qEHA.=2588@.TK2MSFTNGP12.phx.gbl...> > Hello,> >> > We just installed SQL 2000 =on a remote server. We can't connect to SQL> > remotely from =a desktop PC. When we try to register the SQL server in> > = Enterprise Mgr. we get the error:> >> > ="Client unable to establish connection. Named Pipes Provider: =Thenetwork> > path was not found. Timeout expired."> >> > I =checked the protocols on the SQL server and there is: TCP/IP and =Named> > Pipes (the default), so I disabled Named Pipes, but the error = still> occurs.> > Anyone know what might be the problem?> >> > Thanks!> >> =>>>

--=_NextPart_000_00C8_01C4AC61.6F469B80--|||Yes, absolutely.
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:eGqYVuIrEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Can you ping the server from the client?
> Jeff
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to SQL
> > remotely from a desktop PC. When we try to register the SQL server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and Named
> > Pipes (the default), so I disabled Named Pipes, but the error still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>|||You're still trying to use Named Pipes. Use both Client and Server Network
Utilities to ensure TCP/IP
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:#co#$xJrEHA.452@.TK2MSFTNGP09.phx.gbl...
Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and
Windows. When I try to register the SQL Server remotely from my desktop, I
enter SQL username/password. This always worked in the past with other SQL
servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use only
TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes
completely on the remote SQL server, but I still get the error message
below:
"Client unable to establish connection. Named pipes provider: The network
path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows
validation, then you need to ensure that your workstation is trusted by the
W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit
out of my element on this one), but you may need to set up some type of
Share on the W2k3 server so that the pipe is able to connect to the server.
Hope this helps, maybe someone with some additional insight can be of
service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message
news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or you
type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not
SP2).
There is no firewall on the SQL server (not supposed to be). The
server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to
SQL
> > remotely from a desktop PC. When we try to register the SQL server
in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and
Named
> > Pipes (the default), so I disabled Named Pipes, but the error
still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>|||This is the strange thing, I've checked both the Client and Server Network
utils and both show Name Pipes disabled. I've rebooted the server twice.
Maybe I'll have to remove the Name Pipes protocol from the server (not sure
of the ramifications of doing that).
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:#tXe5#KrEHA.2724@.TK2MSFTNGP14.phx.gbl...
> You're still trying to use Named Pipes. Use both Client and Server Network
> Utilities to ensure TCP/IP
> Jeff
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:#co#$xJrEHA.452@.TK2MSFTNGP09.phx.gbl...
> Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and
> Windows. When I try to register the SQL Server remotely from my desktop, I
> enter SQL username/password. This always worked in the past with other SQL
> servers.
> I don't know if I'm trying to use named pipes, in fact I'd rather use only
> TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes
> completely on the remote SQL server, but I still get the error message
> below:
> "Client unable to establish connection. Named pipes provider: The network
> path was not found. Timeout expired."
> Any clues?
> "Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
> news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
> Sounds like a security issue to me.
> Are you using SQL validation or Windows validation? If Windows
> validation, then you need to ensure that your workstation is trusted by
the
> W2k3 server's DC.
> If you are trying to connect through a named pipe, then umm. (I'm a bit
> out of my element on this one), but you may need to set up some type of
> Share on the W2k3 server so that the pipe is able to connect to the
server.
> Hope this helps, maybe someone with some additional insight can be of
> service on this one.
> Rick
> "TJ" <tunj@.hotmail.com> wrote in message
> news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
> Does the client PC list the sqlserver when you try to register it or
you
> type it in?
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
> Rick,
> The SQL Server is Windows 2003 Server, the desktop is XP Pro (not
> SP2).
> There is no firewall on the SQL server (not supposed to be). The
> server and
> desktop PC are not in the same domain. Any clues?
> Thanks!
>
> "Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
> news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> > What Network Operating System (NOS) are you running?
> > What service packs have been applied?
> > Are both servers in the same domain?
> > Do you have to go through a firewall?
> >
> > More information would be helpful.
> >
> > Rick Sawtell
> > MCT, MCSD, MCDBA
> >
> >
> >
> > "Dean J Garrett" <info@.amuletc.com> wrote in message
> > news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > > Hello,
> > >
> > > We just installed SQL 2000 on a remote server. We can't connect
to
> SQL
> > > remotely from a desktop PC. When we try to register the SQL
server
> in
> > > Enterprise Mgr. we get the error:
> > >
> > > "Client unable to establish connection. Named Pipes Provider:
The
> network
> > > path was not found. Timeout expired."
> > >
> > > I checked the protocols on the SQL server and there is: TCP/IP
and
> Named
> > > Pipes (the default), so I disabled Named Pipes, but the error
> still
> > occurs.
> > > Anyone know what might be the problem?
> > >
> > > Thanks!
> > >
> > >
> >
> >
>
>

Sunday, February 12, 2012

can't connect to db/ server

don't know if this is the right place, but anyway...
trying to connect remotely to a mysql database hosted on windows 2003 remote
server.
Can connect locally but not remotely.
Excluding db server setup is there anything on the server that could be
blocking?
How would I check to ensure port 3306 is open?
Any other suggestions would be a help
You can use a port scanning utility. Here is the link to a
description of one you can download from MS:
http://support.microsoft.com/?id=310099
Other than that, you may want to try a forum or newsgroup
specifically for MySQL.
-Sue
On Sun, 18 Apr 2004 01:18:30 +0100, "stephen hall"
<shsc21441@.blueyonder.co.uk> wrote:

>don't know if this is the right place, but anyway...
>trying to connect remotely to a mysql database hosted on windows 2003 remote
>server.
>Can connect locally but not remotely.
>Excluding db server setup is there anything on the server that could be
>blocking?
>How would I check to ensure port 3306 is open?
>Any other suggestions would be a help
>

can't connect to db/ server

don't know if this is the right place, but anyway...
trying to connect remotely to a mysql database hosted on windows 2003 remote
server.
Can connect locally but not remotely.
Excluding db server setup is there anything on the server that could be
blocking?
How would I check to ensure port 3306 is open?
Any other suggestions would be a helpYou can use a port scanning utility. Here is the link to a
description of one you can download from MS:
http://support.microsoft.com/?id=310099
Other than that, you may want to try a forum or newsgroup
specifically for MySQL.
-Sue
On Sun, 18 Apr 2004 01:18:30 +0100, "stephen hall"
<shsc21441@.blueyonder.co.uk> wrote:

>don't know if this is the right place, but anyway...
>trying to connect remotely to a mysql database hosted on windows 2003 remot
e
>server.
>Can connect locally but not remotely.
>Excluding db server setup is there anything on the server that could be
>blocking?
>How would I check to ensure port 3306 is open?
>Any other suggestions would be a help
>

Friday, February 10, 2012

Can''t connect to a sql express on a workgroup pc

Hi Guys,

I'm trying to connect to a sql express on a workgroup PC through sql server 2005 standard edition remotely but i can't.

I have checked and make sure that tcp/ip and other protocals are allowed. There is no firewall on both PCs and the sql browser service is running as well.
Somehow i can connect using the IP address but not the name?

Any idea why?

Gemma

post back the error

Madhu

|||

HI Madhu,

Here it is:

TITLE: Connect to Server

Cannot connect to TYPICAL1.

ADDITIONAL INFORMATION:

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) (Microsoft SQL Server, Error: 53)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

BUTTONS:

Gemma

|||

check this out

http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

Madhu

Can't connect remotely when SQL services running as a domain account

I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts. I
configured the sql service and sql agent service to run as a domain account.
I made that account a member of the administrators group on the SQL server,
and restarted the services. Everything looked fine. The problem is, some of
my remote applications cannot connect when it is running as a domain
account, but they are fine when it is running as a local system account. On
a remote Microsoft WSUS server, it breaks when the SQL services on the SQL
server use a domain account. Osql on the remote box generates this:
Cannot generate SSPI context
I did try to research this before posting here, but I couldn't find anything
that described this problem. Everything was referring to PCs connecting from
a different domain. That is not the case here.
Thanks,
MatthewCannot Generate SSPI context is almost always related to there not being a
Service Principal Name defined for that server, account and port in a
Kerberos environment.
Domain accounts do not create an SPN, whereas Domain Admins and Local System
do.
Test this by making (temporarily) your startup account a domain admin and
the resetting in in SQL Enterprise Manager. restart and test connectivity.
If it connects, have your domain admin (must be a domain admin) create an
SPN for the MSSQLSvc in Active Directory.
See the Books Online article "Security Account Delegation" for formot of
what the resulting SPN should look like.
Also, make sure the SQL Server is listening on TCP...make that your first
step.
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts.
> I configured the sql service and sql agent service to run as a domain
> account. I made that account a member of the administrators group on the
> SQL server, and restarted the services. Everything looked fine. The
> problem is, some of my remote applications cannot connect when it is
> running as a domain account, but they are fine when it is running as a
> local system account. On a remote Microsoft WSUS server, it breaks when
> the SQL services on the SQL server use a domain account. Osql on the
> remote box generates this:
> Cannot generate SSPI context
> I did try to research this before posting here, but I couldn't find
> anything that described this problem. Everything was referring to PCs
> connecting from a different domain. That is not the case here.
> Thanks,
> Matthew
>|||I am the domain admin, so that won't be a problem. As soon as some of the
current activity dies down, I will try this. Thanks!
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>|||Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
having problems configuring the alerts. Outlook 2003 SP2 is installed. I
logged in with he SQL service account, and setup the MAPI profile. That
worked fine. When I set up an operator logged in as the service account,
clicking Test email generates this error:
http://img167.imageshack.us/my.php?image=sqlerroran3.png
If I log in as my self, it acts like it went through when I click test, but
no email is generated.
Any ideas?
Thanks again for your help.
-Matthew
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>|||All I can tell you is that SQL mail is profiel specific...could be a
permissions issue on the profile itself?
That's not my area :-)
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
> Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
> having problems configuring the alerts. Outlook 2003 SP2 is installed. I
> logged in with he SQL service account, and setup the MAPI profile. That
> worked fine. When I set up an operator logged in as the service account,
> clicking Test email generates this error:
> http://img167.imageshack.us/my.php?image=sqlerroran3.png
> If I log in as my self, it acts like it went through when I click test,
> but no email is generated.
> Any ideas?
> Thanks again for your help.
> -Matthew
> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>> Cannot Generate SSPI context is almost always related to there not being
>> a Service Principal Name defined for that server, account and port in a
>> Kerberos environment.
>> Domain accounts do not create an SPN, whereas Domain Admins and Local
>> System do.
>> Test this by making (temporarily) your startup account a domain admin and
>> the resetting in in SQL Enterprise Manager. restart and test
>> connectivity.
>> If it connects, have your domain admin (must be a domain admin) create an
>> SPN for the MSSQLSvc in Active Directory.
>> See the Books Online article "Security Account Delegation" for formot of
>> what the resulting SPN should look like.
>> Also, make sure the SQL Server is listening on TCP...make that your first
>> step.
>> --
>> Kevin Hill
>> 3NF Consulting
>> www.3nf-inc.com/NewsGroups.htm
>>
>>
>> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
>> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>>
>|||This thing is baffling. I read a couple posts that just the 'Test' button
has issues. I scheduled some maintenance to run at 4 AM last night. It ran,
sent me the results, and the log indicated the job failed because the last
step, the email, failed.
The job failed. The Job was invoked by Schedule 4 (Schedule 1). The last
step to run was step 1 (Step 1). NOTE: Failed to notify 'SQL Alerts' via
email.
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:uFBi8n43GHA.4924@.TK2MSFTNGP05.phx.gbl...
> All I can tell you is that SQL mail is profiel specific...could be a
> permissions issue on the profile itself?
> That's not my area :-)
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
>> Thanks! Adding the SPN took care of it. I thought I was there, but now
>> I'm having problems configuring the alerts. Outlook 2003 SP2 is
>> installed. I logged in with he SQL service account, and setup the MAPI
>> profile. That worked fine. When I set up an operator logged in as the
>> service account, clicking Test email generates this error:
>> http://img167.imageshack.us/my.php?image=sqlerroran3.png
>> If I log in as my self, it acts like it went through when I click test,
>> but no email is generated.
>> Any ideas?
>> Thanks again for your help.
>> -Matthew
>> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
>> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>> Cannot Generate SSPI context is almost always related to there not being
>> a Service Principal Name defined for that server, account and port in a
>> Kerberos environment.
>> Domain accounts do not create an SPN, whereas Domain Admins and Local
>> System do.
>> Test this by making (temporarily) your startup account a domain admin
>> and the resetting in in SQL Enterprise Manager. restart and test
>> connectivity.
>> If it connects, have your domain admin (must be a domain admin) create
>> an SPN for the MSSQLSvc in Active Directory.
>> See the Books Online article "Security Account Delegation" for formot of
>> what the resulting SPN should look like.
>> Also, make sure the SQL Server is listening on TCP...make that your
>> first step.
>> --
>> Kevin Hill
>> 3NF Consulting
>> www.3nf-inc.com/NewsGroups.htm
>>
>>
>> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
>> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators
>> group on the SQL server, and restarted the services. Everything looked
>> fine. The problem is, some of my remote applications cannot connect
>> when it is running as a domain account, but they are fine when it is
>> running as a local system account. On a remote Microsoft WSUS server,
>> it breaks when the SQL services on the SQL server use a domain account.
>> Osql on the remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>>
>>
>

Can't connect remotely to WSUS referential MSDE database

Hi all,

WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.

I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.

FROM THE SERVER :

osql -E -S MYSERVER\WSUS works fine but

osql -E -S 127.0.0.1\WSUS doesn't work, i get the famous error

[DBNETLIB]Serveur SQL spcifi non trouv.
[DBNETLIB]ConnectionOpen (Connect()).

If i user "osql -L" command, my instance doesn't appear in the list

FROM A CLIENT COMPUTER

osql -E -S MYSERVER\WSUS and

osql -E -S MY_SERVER_IP\WSUS don't work, i get the same error

I've tried tried to understand for hours, and i'm lost. I thought there may be a problem between SQL and 2003, and read SQL sp3a was required. I ran

select @.@.version from osql and got result

Microsoft SQL Server 2000 - 8.00.881 (Intel X86)

8.00.881 is not referenced in ms support as a patched version number !!!!!

Can anyone help me please ?

hi,

Shogre wrote:

Hi all,
WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.
I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.
FROM THE SERVER :
osql -E -S MYSERVER\WSUS works fine but
osql -E -S 127.0.0.1\WSUS doesn't work, i get the famous error
[DBNETLIB]Serveur SQL spcifi non trouv.
[DBNETLIB]ConnectionOpen (Connect()).
If i user "osql -L" command, my instance doesn't appear in the list
FROM A CLIENT COMPUTER
osql -E -S MYSERVER\WSUS and
osql -E -S MY_SERVER_IP\WSUS don't work, i get the same error
I've tried tried to understand for hours, and i'm lost. I thought there may be a problem between SQL and 2003, and read SQL sp3a was required. I ran
select @.@.version from osql and got result
Microsoft SQL Server 2000 - 8.00.881 (Intel X86)
8.00.881 is not referenced in ms support as a patched version number !!!!!
Can anyone help me please ?

yep, I did not find 8.00.881 build as well... http://www.aspfaq.com/SQL2000Builds.asp ... where did you get it?

anyway... usually named instances do not listen on TCP/IP 1433 port as this one is "reserved" for default instances... using the Server Network Utility you shoud check if your named instance is listening on a dynamic associated port or on a fixed port as you should define a firewall exception as well for it... have a look at http://support.microsoft.com/kb/841249/en-us and http://support.microsoft.com/kb/841251/en-us for further info about the built in W2003 Windows Firewall and how to configure it for remote connections...

regards

Cant connect remotely to SQL Server

I just reinstalled SQL Server and after reattaching my databases, I can't connect remotely. If I use "localhost" in my connection string it works fine, but I can't register my remote Enterprise Manager this way.

I have looked around and made sure that my SQL Server installation has the same name as my computer and I checked the networks settings for SQl Server and it says it is using port 1433 (as expected?). I can't ping port 1433, nor can I connect if I put :1433 in the connection string (is that normal?) I am no network expert so I am not sure of the expected behaviours. I am digging through the Internet for a solution (Microsoft Support is a bit pricy to be anything but a last resort for us), but I thought I would ask here in case someone has a suggestion.

Any help is appreciated.

SP4 was not installed properly, so SQL Server was not listening on port 1433. All fixed now!

Cant connect remotely to SQL Express on Virtual Private Server

I've just bought a Virtual Private Server Account because I want to host a number of different ASP.NET sites, each backed by their own SQL database. I've downloaded SQLEXPRE.EXE and SQLServer2005_SSMEE-x64.msi to the server and installed the database engine and Management Studio Express on the VPS.

My problem is that I cannot access the SQLEXPRESS on my server from my local machine. The Management Studio Express cannot get logged in. I've used "Surface Area Configuration Manager" to allow "Local and remote connections" using TCP/IP only. I've used SQL Server Configuration Manager" to enable the TCP/IP protocol. After making these changes I've stopped and started the SQL server - and even rebooted the machine. I've created a login "Remote User" for this access. I've added sqlservr.exe as an exception to the firewall.

What else do I need to do? Is there a simpleton's guide to completing this task?

Did you start the sql server browsing service?

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Can't connect remotely to SQL Express as 'sa'

I have a remote server with SQL Server 2005 Express installed on it. I
try to connect to it from my local machine using TCP/IP. I have the
remote SQL Express set to mixed mode and enabled TCP/IP.
If I connect using a self-created login it works fine and I can run
queries against the database. However whenever I try to login with the
'sa' account, it doesn't work (Login failed). I'm 100% sure the 'sa'
account is enabled and the password is correct. When I connect using
MSSMSE from my local machine to the remote SQL Express using the 'sa'
account it works fine and I can do everything.
So, the password I use for the 'sa' account is definitely correct but
somehow it doesn't allow me to connect from anything else than MSSMSE.
E.g. the following VBscript does not work:
Set Conn = CreateObject("ADODB.Connection")
Conn.Open "Provider=SQLOLEDB;Data
Source=10.10.10.94;DATABASE=Test;User Id=sa;Password=testing;Connect
Timeout=3;network library=DBNETLIB;"
Conn.Close
Set Conn = Nothing
It gives:
C:\test.vbs(2, 1) Microsoft OLE DB Provider for SQL Server:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.
When I connect with isql, I get "Login failed for 'sa'".
It has kept me busy for almost 4 hours already and I can't figure out
what's going on. It feels like some security settings in SQL Express
prevents me from using the 'sa' account from any application except
MSSMSE.
Any help is appreciated...
Grtz,
Marco>E.g. the following VBscript does not work:
>Set Conn = CreateObject("ADODB.Connection")
>Conn.Open "Provider=SQLOLEDB;Data
>Source=10.10.10.94;DATABASE=Test;User Id=sa;Password=testing;Connect
>Timeout=3;network library=DBNETLIB;"
>Conn.Close
>Set Conn = Nothing
I fixed the problem. For anybody interested, here's how I fixed it...
The problem was most likely not related to the account. I probably
made a mistake while testing it. Or mixed results might have been
caused by the fact that I tested with both dynamic ports and fixed
ports.
The problem was fixed by changing the "Data Source". I changed it to:
Data Source=SERVER\SQLINSTANCE
So, e.g.:
Data Source=10.10.10.94\SQLEXPRESS1
This is with Dynamic ports.
Cheers,
Marco

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDe...aspx?tabid=37.
John

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37.
John

Tuesday, March 27, 2012

Can't get connected to MSDE Remotely

Friday, February 24, 2012

Can't connect via HTTP remotely...

Thursday, February 16, 2012

Can't connect to SQL

Sunday, February 12, 2012

can't connect to db/ server

can't connect to db/ server

Friday, February 10, 2012

Can''t connect to a sql express on a workgroup pc

Can't connect remotely when SQL services running as a domain account

Can't connect remotely when SQL services running as a domain account

Can't connect remotely when SQL services running as a domain account

Can't connect remotely to WSUS referential MSDE database

Cant connect remotely to SQL Server

Cant connect remotely to SQL Express on Virtual Private Server

Can't connect remotely to SQL Express as 'sa'

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

connect from ASP app

Blog Archive

About Me