Connecting to SQL 2005 from other machines

The April CTP was working well but both the June and Sept CTP seem to be having problems with connections outside the local machine. It does not seem to matter how the connection is to be established (from code, from SQL managment studio etc) the same error comes up repeatedly.

Cannot connect to SEPTCTP.

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

Any suggestions besides rolling back to the April CTP (our current solution)?

Is the Named Pipes protocol enabled on server?
On server machine, run SQL Server configuration manager,
open SQL Server Network Configurations and enable Named Pipes.
Or switch client to use TCP/IP protocol rather than Named Pipes.

Thanks,
Michael.

P.S. This seems to be general SQL question, you might
get better response in SQL Server Database Engine group,
rather than in this SSIS-specific group.|||I'm not sure why, but we needed to access remote servers with their IP address AND a specific non-standard port once we upgraded to the newest CTP. This seemed fine for our test applications (we're not releasing anything until the final version is released).

Josh|||

This should be fine, provided that client is also configured

to use TCP/IP protocol and appropriate port. But the error

indicates the connection is using Named Pipes protocol.

It seems like the connection or SQL Client defaults is not

configured properly.

I'm not really a pro in SQL Client configuration, forum
SQL Server Database Engine might have people more
knowlegable in this area.

The answer may depend on whether you are using OLEDB or
ADO.NET connection managed, and in former case - SQL Native
OLEDB provider or Microsoft OLEDB provider for SQL Server.

connecting to server outside network

I'm trying to move some files from our in-house server to a server at our
ISP. I'm using the dts wizard. For the source, I put in the IP address of our
ih-house server. When I click "refresh" to get a list of the databases I get
this error:
Error source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
not exist or access denied.
Context: Error during intialiaztion of the provider.
I am able to ping the in-house sever from the ISP server. I can log in to
the in-house using query analyzer and the login and password that I'm putting
in the dts wizard.
Any idea what might be wrong?
Thanks,
Dan D.
Problem solved. It was a setting in our firewall.
Dan D.
"Dan D." wrote:

> I'm trying to move some files from our in-house server to a server at our
> ISP. I'm using the dts wizard. For the source, I put in the IP address of our
> ih-house server. When I click "refresh" to get a list of the databases I get
> this error:
> Error source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
> not exist or access denied.
> Context: Error during intialiaztion of the provider.
> I am able to ping the in-house sever from the ISP server. I can log in to
> the in-house using query analyzer and the login and password that I'm putting
> in the dts wizard.
> Any idea what might be wrong?
> Thanks,
> --
> Dan D.

connecting to server outside network

I'm trying to move some files from our in-house server to a server at our
ISP. I'm using the dts wizard. For the source, I put in the IP address of our
ih-house server. When I click "refresh" to get a list of the databases I get
this error:
Error source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
not exist or access denied.
Context: Error during intialiaztion of the provider.
I am able to ping the in-house sever from the ISP server. I can log in to
the in-house using query analyzer and the login and password that I'm putting
in the dts wizard.
Any idea what might be wrong?
Thanks,
--
Dan D.Problem solved. It was a setting in our firewall.
--
Dan D.
"Dan D." wrote:
> I'm trying to move some files from our in-house server to a server at our
> ISP. I'm using the dts wizard. For the source, I put in the IP address of our
> ih-house server. When I click "refresh" to get a list of the databases I get
> this error:
> Error source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
> not exist or access denied.
> Context: Error during intialiaztion of the provider.
> I am able to ping the in-house sever from the ISP server. I can log in to
> the in-house using query analyzer and the login and password that I'm putting
> in the dts wizard.
> Any idea what might be wrong?
> Thanks,
> --
> Dan D.

connecting to server outside network

I'm trying to move some files from our in-house server to a server at our
ISP. I'm using the dts wizard. For the source, I put in the IP address of ou
r
ih-house server. When I click "refresh" to get a list of the databases I get
this error:
Error source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server
does
not exist or access denied.
Context: Error during intialiaztion of the provider.
I am able to ping the in-house sever from the ISP server. I can log in to
the in-house using query analyzer and the login and password that I'm puttin
g
in the dts wizard.
Any idea what might be wrong?
Thanks,
--
Dan D.Problem solved. It was a setting in our firewall.
--
Dan D.
"Dan D." wrote:

> I'm trying to move some files from our in-house server to a server at our
> ISP. I'm using the dts wizard. For the source, I put in the IP address of
our
> ih-house server. When I click "refresh" to get a list of the databases I g
et
> this error:
> Error source: Microsoft OLE DB Provider for SQL Server
> Error Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Serv
er does
> not exist or access denied.
> Context: Error during intialiaztion of the provider.
> I am able to ping the in-house sever from the ISP server. I can log in to
> the in-house using query analyzer and the login and password that I'm putt
ing
> in the dts wizard.
> Any idea what might be wrong?
> Thanks,
> --
> Dan D.

connecting to database in runtime using visual basic 6

hi;
i design a crystal report outside visual basic 6. what i did is just calling the crystal report filename. how can i change the source database of my crystal reports in runtime. im using microsoft sql server. the two database had the same table structure.
thanksWhich version of CR are you using?
If it is CR9 then
cr.Database.LogOnServer "p2ssql.dll", "Server", "Database", "UserName,"Password"

Connecting SQL 2005 Mgt STudio through a Cisco Firewall

What ports do i need to open on my Cisco Firewall in order to allow someone outside my firewall access to SQL? They want to connect using MGT Studio.

Thanks

Bosco

YOu will need to open the port assigned to SQL Server (by default the 1433) but this can differ based on the settings you provided during the install.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Except the TCP port Jens mentioned, you may also need to open UDP port 1434 if it's a named instance (also make sure SQL Browser is running). If you want use Named Pipes, you need open up ports used by file sharing.

Connecting from outside world

Hello,
I have just set up SQL server on our system.
I would like to be able to connect from accross the internet, like I can
with exchange. (Using EM)
What do I have to do in order to do this?
Many thanks,
NEIL
Take a look at our Product ISA Server. You can use this to publish your
SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||"Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> I have just set up SQL server on our system.
> I would like to be able to connect from accross the internet, like I can
> with exchange. (Using EM)
> What do I have to do in order to do this?
The most efficient way would be a server (or desktop) that you could run
remote desktop with a copy of EM tools. In this way the MMC is local to SQL
Server and screen and keyboard updates are sent over the WAN. I'd recommend
a VPN solution for connectivity to the remote device.
Steve
|||Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
dual processor machine in a WAN/LAN environment. After several hours of being
"idle", SQL server begins transmitting "Chatter" accross both the LAN and
WAN, flooding the router and bringing the network to its knees. Subsequent
pings either time out or are finally successful yet at very high ms counts.
I also have SQL server 2000 running in a single processor environment where
this is not an issue.
Have you encountered this before? Can you offer any suggestion as to how to
address this problem?
Thanks,
Steve S
"Steve Thompson" wrote:

> "Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
> news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> The most efficient way would be a server (or desktop) that you could run
> remote desktop with a copy of EM tools. In this way the MMC is local to SQL
> Server and screen and keyboard updates are sent over the WAN. I'd recommend
> a VPN solution for connectivity to the remote device.
> Steve
>
>
|||"Steve S" <SteveS@.discussions.microsoft.com> wrote in message
news:504D0B59-2D64-4FC1-8D72-CCD724E78B7B@.microsoft.com...
> Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
> dual processor machine in a WAN/LAN environment. After several hours of
being
> "idle", SQL server begins transmitting "Chatter" accross both the LAN and
> WAN, flooding the router and bringing the network to its knees. Subsequent
> pings either time out or are finally successful yet at very high ms
counts.
> I also have SQL server 2000 running in a single processor environment
where
> this is not an issue.
> Have you encountered this before? Can you offer any suggestion as to how
to
> address this problem?
Hi Steve,
That is not normal activity -- have your scanned your server for a virus,
such as the blaster virus?
Steve

Connecting from outside world

Hello,
I have just set up SQL server on our system.
I would like to be able to connect from accross the internet, like I can
with exchange. (Using EM)
What do I have to do in order to do this?
Many thanks,
NEILTake a look at our Product ISA Server. You can use this to publish your
SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> I have just set up SQL server on our system.
> I would like to be able to connect from accross the internet, like I can
> with exchange. (Using EM)
> What do I have to do in order to do this?
The most efficient way would be a server (or desktop) that you could run
remote desktop with a copy of EM tools. In this way the MMC is local to SQL
Server and screen and keyboard updates are sent over the WAN. I'd recommend
a VPN solution for connectivity to the remote device.
Steve|||Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
dual processor machine in a WAN/LAN environment. After several hours of bein
g
"idle", SQL server begins transmitting "Chatter" accross both the LAN and
WAN, flooding the router and bringing the network to its knees. Subsequent
pings either time out or are finally successful yet at very high ms counts.
I also have SQL server 2000 running in a single processor environment where
this is not an issue.
Have you encountered this before? Can you offer any suggestion as to how to
address this problem?
Thanks,
Steve S
"Steve Thompson" wrote:

> "Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
> news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> The most efficient way would be a server (or desktop) that you could run
> remote desktop with a copy of EM tools. In this way the MMC is local to SQ
L
> Server and screen and keyboard updates are sent over the WAN. I'd recommen
d
> a VPN solution for connectivity to the remote device.
> Steve
>
>|||"Steve S" <SteveS@.discussions.microsoft.com> wrote in message
news:504D0B59-2D64-4FC1-8D72-CCD724E78B7B@.microsoft.com...
> Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
> dual processor machine in a WAN/LAN environment. After several hours of
being
> "idle", SQL server begins transmitting "Chatter" accross both the LAN and
> WAN, flooding the router and bringing the network to its knees. Subsequent
> pings either time out or are finally successful yet at very high ms
counts.
> I also have SQL server 2000 running in a single processor environment
where
> this is not an issue.
> Have you encountered this before? Can you offer any suggestion as to how
to
> address this problem?
Hi Steve,
That is not normal activity -- have your scanned your server for a virus,
such as the blaster virus'
Steve