Connect to SQL Server: network

Showing posts with label network. Show all posts

Tuesday, March 27, 2012

Connecting to SQL Server 2000 on another subnet

Hi Folks,

I'm very new to SQL Server. I have a home network. My primary connection
to the internet is using "Gateway 1" a linksys router, of which, my server
is a LAN node on that router. I have another LAN node connecting to the WAN
node of the "Gateway 2" a wireless USR router to use with my laptop. Using
the wireless laptop, I am on a different subnet than the Server. I'd like
to make a connection to the server through Visual Studio.net but I can't
seem to do it. I'm using TCP/IP with a port different than the default port
(let's call it port 2110, even though it's not). I do have port forwarding
on Gateway1 and I've tried everything from just the server internal IP
address, the external IP address, IP address with port designation, URL with
port designation, nothing seems to work. Any ideas?

Thanks!
RickIt sounds more like you need to configure Gateway2 (not Gateway1)
correctly, if you want to connect to the server from your laptop? The
KB article below might help, but if not, you may get better help in a
networking group of some sort. If you haven't already, you probably
need to use ping, tracert, nslookup etc to make sure you can at least
resolve the server's name and 'see' it on the LAN.

http://support.microsoft.com/kb/287932

Simonsql sql

Sunday, March 25, 2012

connecting to SQL on network machine

Hi,
I'm trying to use one of my machines as a database server, just for local network testing/development etc. This machine/server is on my local network via a router.
Can anyone advise me of how, when using VS 2005 Beta 2, to connect to my SQL Server 2005 installation on the server running on my network. ? In the 'add connection' dialogue, what do I put in the 'Server name:' field, (apart from server name...) is it the name of the machine or the IP address of the machine on the network ?
Any and all advise appreicated.
Thanks in advance.

Maybe u need to have the Client SQL and to open the enterprise manager to register a new server group
After that u can use it in ur program
HTH

|||

Hi Smiling,

Thanks for the response. I now have everything running/installed on sql 2005 (named pipes, tcp/ip etc) but still no luck, although I now have an error message:
'A connection was successfully established with the server, but then an error occured during the pre-login handshake.(provider: Named Pipes Provider, error: 0 -No process is on the other end of the pipe.)'
On my sql 2005 machine Named Pipes is Enabled and 'Local Access Only' is set to 'No'. If I disable Named Pipes I get the same error message !
I have tried your suggestion and registered new server group and specified Named Pipes as the Network Protocol etc. no luck.
any further advice appreciated.

|||i have the same problem.. i receive the same error message if i want toconnect to the database (sql 2005 beta 3) through vs2005.
any ideas ?

Thursday, March 22, 2012

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.

When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.

Hope that helps,

-Lukasz

|||Hi Lukasz,
I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."|||We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder?|||

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

|||I had this same problem and found a good solution here.|||I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.

Any ideas how to fix this problem when running Reporting Services in integrated mode?

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?
sql sql

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?

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.

Tuesday, March 20, 2012

Connecting to Network Server

Hi All,
I have 2 computers, one has SQL2000 and the other has MSDE2000. I have the
SQL tools installed on both computers.
When I use the enterprise manager and try to connect remote server I cannot
get the user to authenticate. It is trying to access the remote server
using the guest account.
There is no domain. Both computer have mixed mode authentication, and are
on the same 192.168.1.x network range.
What am I missing here.
Thanks
Lee
hi Lee,
"Lee Trotter" <latrotter@.@.@.sympatico.ca> ha scritto nel messaggio
news:%23lstCrAaEHA.3112@.tk2msftngp13.phx.gbl...
> Hi All,
> I have 2 computers, one has SQL2000 and the other has MSDE2000. I have
the
> SQL tools installed on both computers.
> When I use the enterprise manager and try to connect remote server I
cannot
> get the user to authenticate. It is trying to access the remote server
> using the guest account.
> There is no domain. Both computer have mixed mode authentication, and are
> on the same 192.168.1.x network range.
I did not undertand if you, from both machines, can not connect remotely or
you can not remotely connect just to the MSDE instance...
if this is the case, MSDE installs by default disabling network protocols,
in order to prevent external malicius attacks, so that only local connection
using Shared Memory are allowed..
you can modify this behaviour bot at install time, specifying the
DISABLENETWORKPROTOCOLS=0 parameter to the setup.exe boostrat MSDE
installer, and later, using Server Network Utility (svrnetcn.exe), enabling
the desired network protocol(s)..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Monday, March 19, 2012

Connecting to MSDE named instance

If we install MSDE 2000 SP3a with out a named instance we can connect to
through OSQL from a different computer on the network.
We used SVRNETCN.EXE to add TCP/IP to the protocol list.
We changed the port from 1059 or something like that to 1433.
We changed "LoginMode" to 2, but we also tried it with 0
But when we try to connect via OSQL
osql -S ROBXP\RR -U sa -P 11111
we get the following error.
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
the same OSQL command works OK from the local computer.
If we re-install with out a named instance we can connect fine with OSQL
Any ideas?
-Rob
PS. it was installed with the following:
setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
Check your MDAC version on the client you're trying to connect from. Upgrade
to the latest version and try it again.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"rob" wrote:

> If we install MSDE 2000 SP3a with out a named instance we can connect to
> through OSQL from a different computer on the network.
> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
> We changed "LoginMode" to 2, but we also tried it with 0
> But when we try to connect via OSQL
> osql -S ROBXP\RR -U sa -P 11111
> we get the following error.
>
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> the same OSQL command works OK from the local computer.
>
> If we re-install with out a named instance we can connect fine with OSQL
> Any ideas?
> -Rob
> PS. it was installed with the following:
> setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
>
>
|||I ran Componet Checker 2.0 and it indidcates I have MDAC 2.8 SP1 which looks
to be the latest version.
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:86C87062-5A4C-4962-8FB3-99BA9CA2F375@.microsoft.com...
> Check your MDAC version on the client you're trying to connect from.
> Upgrade
> to the latest version and try it again.
|||hi,
rob wrote:

> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
usually 1433 is for default instances, where other port numbers indicates
named instances...
specifying a fixed port and not using the dynamic assigned port (wiche
requires on the server the UDP 1434 port to be available out of eventual
firewall) you have to specify an alias via Client Network Utility
(cliconfg.exe) on each remote client...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
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
|||THANKS it works.
For anyone else reading this thread in the future.
You give it an alias name (RR for example) and and the servername is the
servername\instance
you can test the connection by using the alias name:
osql -S RR -U sa -Pxxxxx
thanks again.
.....
I have done some more testing. The only thing I am concerned about is:
After my program and MSDE is installed on someones computer, if they want to
access it from a different computer they will need to know how to create
exceptions in the WindowsXP firewall.
They will need to open up UPD 1434 and TCP port XXXX where XXXX is whatever
random port is used during installation of MSDE. I can find that port in
the registry and tell them at install time. But my users are not always
very proficient at using computers, and could have a hard time opening up
ports in the firewall.
If anyone has any suggestions about making this easier I would love to hear
about it.
-Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qfs6cFe280bU1@.individual.net...
> hi,
> rob wrote:
>
> usually 1433 is for default instances, where other port numbers indicates
> named instances...
> specifying a fixed port and not using the dynamic assigned port (wiche
> requires on the server the UDP 1434 port to be available out of eventual
> firewall) you have to specify an alias via Client Network Utility
> (cliconfg.exe) on each remote client...
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> 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
>
|||hi Rob,
rob wrote:
> ....
> I have done some more testing. The only thing I am concerned about
> is: After my program and MSDE is installed on someones computer, if
> they want to access it from a different computer they will need to
> know how to create exceptions in the WindowsXP firewall.
> They will need to open up UPD 1434 and TCP port XXXX where XXXX is
> whatever random port is used during installation of MSDE. I can find
> that port in the registry and tell them at install time. But my
> users are not always very proficient at using computers, and could
> have a hard time opening up ports in the firewall.
> If anyone has any suggestions about making this easier I would love
> to hear about it.
>
actually you can provide the script available at
http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
ports" :D
try having a look at it if can helps..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
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
|||Wow, that will make it easier. I was dreading having to give instructions to
open the firewall. ; )
I don't want to bother you, but I have one more question.
Your advice did work, and I can connect to the newly installed instance, -
IF I set up an alias.
BUT,
I have one computer that I installed with an instance that I do NOT have to
set up an alias for to connect remotely. I can not see what is different
for this computer. I even printed out the MSSQL registry settings for the
two computers and could not see a difference (besides uptime, etc.)
Even though your suggestion works, it would be much easier if I did not have
to set up an alias on the clients. Do you have any ideas what I did
differently with the one that works with out an alias?
Thanks,
Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qhp0hFem400U1@.individual.net...
> hi Rob,
> actually you can provide the script available at
> http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
> ports" :D
> try having a look at it if can helps..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> 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 downloaded your program DBMgr2 and was able to connect to my DB without
using an alias. The difference was (from your help file) to use servername =
ROBXP\RR,1433
explicitly name the port number. This works via osql also.
The difference remains that I have one computer that I do not need to know
what the port number is, or set up an alias.
"rob" <ryost@..no.spam.rentright.com> wrote in message
news:OqGjGPbyFHA.2924@.TK2MSFTNGP15.phx.gbl...
> Wow, that will make it easier. I was dreading having to give instructions
> to open the firewall. ; )
> I don't want to bother you, but I have one more question.
> Your advice did work, and I can connect to the newly installed instance, -
> IF I set up an alias.
> BUT,
> I have one computer that I installed with an instance that I do NOT have
> to set up an alias for to connect remotely. I can not see what is
> different for this computer. I even printed out the MSSQL registry
> settings for the two computers and could not see a difference (besides
> uptime, etc.)
> Even though your suggestion works, it would be much easier if I did not
> have to set up an alias on the clients. Do you have any ideas what I did
> differently with the one that works with out an alias?
> Thanks,
> Rob
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3qhp0hFem400U1@.individual.net...
>
|||hi Rob,
rob wrote:
> I downloaded your program DBMgr2 and was able to connect to my DB
> without using an alias. The difference was (from your help file) to
> use servername = ROBXP\RR,1433
> explicitly name the port number. This works via osql also.
> The difference remains that I have one computer that I do not need to
> know what the port number is, or set up an alias.
probably it's not a named instance but a default one, that's to say ROBXP
and not ROBXP\RR..
default instances automatically listen on TCP 1433 as this port is the one
Microsoft reserved on IANA for SQL Server...
try having a look at it..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
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 am pretty sure it is a named instance. I connected to it through your
Dbamgr2k by specifing
MICHELLEP\MICHELLE
I did not have to give it port 1433 (which is its port)
I did set this server up several months ago, and do not remember exactly how
I did it.
Also, when I go to add remove programs it is listed as:
Microsoft SQL Server Desktop Engine (MICHELLE)
and I think the instance name is listed in the paren's
From SQLPing:
C:\>sqlping 192.168.0.88
SQL-Pinging 192.168.0.88
Listening...
ServerName:MICHELLEP
InstanceName:MICHELLE
IsClustered:No
Version:8.00.194
tcp:1433
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qieavFf286oU1@.individual.net...
> probably it's not a named instance but a default one, that's to say ROBXP
> and not ROBXP\RR..
> default instances automatically listen on TCP 1433 as this port is the one
> Microsoft reserved on IANA for SQL Server...
> try having a look at it..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> 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
>

Connecting to MSDE 2000 over a home network

Hi,

I'm trying to connect to an instance of MSDE 2000 from Visual Studio 2005 over a home network. Although I know how to connect to a database from Visual Studio, I'm pretty clueless about configuring Sql Server to allow the connection (I can connect with no problem when I do so from the same computer). Also, with experimenting I've created a bunch of instances of Sql Server that I don't really need and am not sure how to get rid of them. Thanks in advance for any help.

-Dave

I don't know if this will help, but I've already tried enabling all of the network protocols in the instance. Also, I can easily connect to an Access database over the network.

You may want to start here:

http://msdn2.microsoft.com/en-us/library/ms190944.aspx

Buck Woody

Connecting to MSDE 2000 over a home network

Hi,

-Dave

I don't know if this will help, but I've already tried enabling all of the network protocols in the instance. Also, I can easily connect to an Access database over the network.

You may want to start here:

http://msdn2.microsoft.com/en-us/library/ms190944.aspx

Buck Woody

Sunday, March 11, 2012

Connecting to DB over a network

I have set up a database server but i do not know how to connect to the database on that servber via asp can some one help with a connction string?
im new.From ASP you can only use ADO. Here is a sample code:

option explicit

dim con
dim rs

set con = WScript.CreateObject( "ADODB.Connection" )
con.open "PROVIDER=SQLOLEDB;SERVER=your_server;DATABASE=your _db;UID=your_login;PWD=your_password"

set rs = WScript.CreateObject( "ADODB.Recordset" )
rs.open "your select statement", con, 0, 1

do while not rs.EOF
' Process your row set
rs.MoveNext
loop

rs.close
con.close

set rs = nothing
set con = nothing|||so the only difference between connecting to a local db and one over a network is this...
SERVER=your_server;DATABASE=your_db;

thanks a lot.|||the first time i used your code, i was connecting in the asp page. i then tried to connect at session_onstart and had some problems. when i tried to cut and paste back so that i can connect at the asp page again i began getting more problems. i am not sure what i did wrong. heres what i have and i am recieving an OBJECT REQUIRED error

-------
dim cnnLogin
dim rstLogin

strSQL = "SELECT * FROM CityBase.dbo.Login " _
& "WHERE Login='" & Replace(Request.Form("login"), "'", "''") & "' " _
& "AND Pwd='" & Replace(Request.Form("password"), "'", "''") & "';"

set cnnLogin = WScript.CreateObject( "ADODB.Connection" )
cnnLogin.open "PROVIDER=SQLOLEDB;SERVER=CITYSERV1;DATABASE=CityBa se;UID=webuser;PWD=webaccess"

'Set cnnLogin = Server.CreateObject("ADODB.Connection")
'cnnLogin.Open "PROVIDER=SQLOLEDB;SERVER=CITYSERV1;DATABASE=CityBa se;UID=webuser;PWD=webaccess"

Set rstLogin = cnnLogin.Execute(strSQL)|||i seemed to have figured it out. however, i am not sure how. i think becuase i was connecting in each page they over lapped some how between the two pages.

thanks for your help.|||Originally posted by CityInet.com
i seemed to have figured it out. however, i am not sure how. i think becuase i was connecting in each page they over lapped some how between the two pages.

thanks for your help.

I think this is the easiest way.

'-- CursorTypeEnum Values --
Const adOpenForwardOnly = 0
Const adOpenKeyset = 1
Const adOpenDynamic = 2
Const adOpenStatic = 3

'-- LockTypeEnum Values --
Const adLockReadOnly = 1
Const adLockPessimistic = 2
Const adLockOptimistic = 3
Const adLockBatchOptimistic = 4

'-- CursorLocationEnum Values --
Const adUseServer = 2
Const adUseClient = 3

Dim DataConn
Dim rs

Set DataConn = Server.CreateObject("ADODB.Connection")
Set rs = Server.CreateObject( "ADODB.Recordset" )

With DataConn
.ConnectionString = "Provider=SQLOLEDB.1; Data Source=YOUR_SERVER; Persist Security Info=False; User ID=sa; Initial Catalog=YOUR_DATABASE"
.ConnectionTimeout = 15
.CommandTimeout = 30
.CursorLocation = adUseClient
.Open
End With

rs.Open "SELECT * FROM Table", DataConn, adOpenForwardOnly, adLockReadOnly

hth!|||i think i like this way best, but what if i wanted to make my connection in session. as of now i am making it at each page. the application is only being made for less than 50 people to access so i think i would like to make my connection in session. how would i go about doing that?

thanks a lot|||Hi Matt,

Follow this:
======================
Put this in your Global.asa:
Sub Application_OnStart
Application("DataConn_ConnectionString") = "Provider=SQLOLEDB.1; Data Source=YOUR_SERVER; Persist Security Info=False; User ID=sa; Initial Catalog=YOUR_DATABASE"
'
Application("DataConn_ConnectionTimeout") = 15
Application("DataConn_CommandTimeout") = 30
End Sub
======================
Create some include file that do the connection, like this:
<%
'-- CursorTypeEnum Values --
Const adOpenForwardOnly = 0
Const adOpenKeyset = 1
Const adOpenDynamic = 2
Const adOpenStatic = 3

'-- LockTypeEnum Values --
Const adLockReadOnly = 1
Const adLockPessimistic = 2
Const adLockOptimistic = 3
Const adLockBatchOptimistic = 4

'-- CursorLocationEnum Values --
Const adUseServer = 2
Const adUseClient = 3

Dim DataConn

Set DataConn = Server.CreateObject("ADODB.Connection")

With DataConn
.ConnectionString = Application("DataConn_ConnectionString")
.ConnectionTimeout = Application("DataConn_ConnectionTimeout")
.CommandTimeout = Application("DataConn_CommandTimeout")
.CursorLocation = adUseClient
.Open
End With
%>
======================
Use it by this way:
<%@. Language=VBScript %>

<%
Dim rs

Set rs = Server.CreateObject( "ADODB.Recordset" )

rs.Open "SELECT * FROM Table", DataConn, adOpenForwardOnly, adLockReadOnly
%>
======================

hth!

Antonio Carlos
www.focoservices.com|||To use the constants for ado, just include adovbs.inc.

Connecting to Database

Connected to SQL database via network but now I have
copied database onto laptop to work from home, I got SQL
2000 Server Edition on laptop but I cannot seem to connect
to local database on laptop, it comes up with errors
saying no database found or access denied. Tried to tell
it to look locally but nothing.Do I need to uninstall
server edition and put personal edition on? Do I did
the .log file on laptop as well?
Any help will be grateful.pls check whether u have creted the user rights for the database, which u in
stalled in ur laptop. if u have not created go to SQL enterprise Manager the
ire u can create new user. then u can able to accress the database.|||After I wrote this posting I did alittle searching around the newsgroups and
found similiar problem, and that suggested uninstalling SQL and reinstallin
g again. I did this and this time I could connect to local SQL server on loc
al machine but it wouldn't
see my database which I had backed up from the original. I didn't have the .
ldf or .log file but I'm getting that in the next day so hopefully it will t
hen allow me to create the database again. I've tried to create a new databa
se and then restore my orig
inal into that database but it's not seen it.
Any help will be appreciated.

Connecting to Database

Connected to SQL database via network but now I have
copied database onto laptop to work from home, I got SQL
2000 Server Edition on laptop but I cannot seem to connect
to local database on laptop, it comes up with errors
saying no database found or access denied. Tried to tell
it to look locally but nothing.Do I need to uninstall
server edition and put personal edition on? Do I did
the .log file on laptop as well?
Any help will be grateful.
pls check whether u have creted the user rights for the database, which u installed in ur laptop. if u have not created go to SQL enterprise Manager theire u can create new user. then u can able to accress the database.
|||After I wrote this posting I did alittle searching around the newsgroups and found similiar problem, and that suggested uninstalling SQL and reinstalling again. I did this and this time I could connect to local SQL server on local machine but it wouldn't
see my database which I had backed up from the original. I didn't have the .ldf or .log file but I'm getting that in the next day so hopefully it will then allow me to create the database again. I've tried to create a new database and then restore my orig
inal into that database but it's not seen it.
Any help will be appreciated.

Thursday, March 8, 2012

Connecting to an instance of MSDE (SQL Server) on a remote machine

I have recently installed MS Office 2003 on a new machine running as a
storage machine on a peer to peer XP Professional network. I followed all
the instructioons and allowed only the login password to be changed.
I am now hoping to connect to the SQL Server instance from a desktop PC
(i.e. remotely). I have installed SQL Server2000 developer edition on my
local machine and have tried to conncet through the login presented as part
of the query analyser.
I can see the remote SQL Server instance in the drop down box and am
entering my loginID and password. I am assuming that my login ID should be
"sa" (default) and my password should match that which I set when I installed
the MSDE SQL Server on the remote machine.
When I go to connect a dialogue box pops up for about 30 secs informing that
the computer is attenmpting connection before I get an error message (Msg No.
17, Level 16, State 1: SQL Server does not exist or access denied).
I am logged on as adminsiatrator on both machines, and as far as I can tell
I should be able to connect. Is there anything I am missing?
hi Andrew,
andrew wrote:
> I have recently installed MS Office 2003 on a new machine running as a
> storage machine on a peer to peer XP Professional network. I
> followed all the instructioons and allowed only the login password to
> be changed.
> I am now hoping to connect to the SQL Server instance from a desktop
> PC (i.e. remotely). I have installed SQL Server2000 developer
> edition on my local machine and have tried to conncet through the
> login presented as part of the query analyser.
> I can see the remote SQL Server instance in the drop down box and am
> entering my loginID and password. I am assuming that my login ID
> should be "sa" (default) and my password should match that which I
> set when I installed the MSDE SQL Server on the remote machine.
> When I go to connect a dialogue box pops up for about 30 secs
> informing that the computer is attenmpting connection before I get an
> error message (Msg No. 17, Level 16, State 1: SQL Server does not
> exist or access denied).
> I am logged on as adminsiatrator on both machines, and as far as I
> can tell I should be able to connect. Is there anything I am missing?
this kind of excpetion is a generic MDAC exception, as reported in
http://support.microsoft.com/default...06&Product=sql
chances are you installed MSDE on the remote pc without enabling it's
network protocols (default behavior for MSDE installations) or the remote
WinXP is protected by WinXP sp2 Windows Firewall...
for the protoccols case, please verify via the Server Network Utility
(svrnetcn.exe) the desired protocol is enable...
for Windows Firewall,
http://support.microsoft.com/default.aspx?kbid=841249
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Connecting to an alias fails

Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>

Connecting to an alias fails

Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>

Wednesday, March 7, 2012

Connecting to a remote sql server for merge replication (push) in SQL Server 2005 Replicat

I am trying to setup a merge (push) replication to a server/database
in a
remote network. I created the publication and connected to the remote
network using VPN but cannot register nor see the remote sql server.
In sql
server 2000, I was able to register the server in my Enterprise
Manager
(after creating an alias) and then created the push subscription. I
connect
to the remote network server using VPN. How do I go about doing this
in SQL
Server 2005? The publisher is a WorkGroup edition while the subscriber
is
standard edition. Authentication is set to both win and sql and
verified
the user and password used to attempt registration. Any help will be
greatly appreciated.
Create an alias on the publisher to the subscriber. Use client network
utility to do this, and for the server name use its fully qualified domain
name. Try to ping both servers from each other.
You may have to use anonymous subscribers to get this to work if you can't
map an unc drive between the two.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<pete970t@.gmail.com> wrote in message
news:1182891307.332293.251610@.u2g2000hsc.googlegro ups.com...
>I am trying to setup a merge (push) replication to a server/database
> in a
> remote network. I created the publication and connected to the remote
> network using VPN but cannot register nor see the remote sql server.
> In sql
> server 2000, I was able to register the server in my Enterprise
> Manager
> (after creating an alias) and then created the push subscription. I
> connect
> to the remote network server using VPN. How do I go about doing this
> in SQL
> Server 2005? The publisher is a WorkGroup edition while the subscriber
> is
> standard edition. Authentication is set to both win and sql and
> verified
> the user and password used to attempt registration. Any help will be
> greatly appreciated.
>

Tuesday, March 27, 2012

Connecting to SQL Server 2000 on another subnet

Sunday, March 25, 2012

connecting to SQL on network machine

Thursday, March 22, 2012

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

connecting to server outside network

connecting to server outside network

connecting to server outside network

Tuesday, March 20, 2012

Connecting to Network Server

Monday, March 19, 2012

Connecting to MSDE named instance

Connecting to MSDE 2000 over a home network

Connecting to MSDE 2000 over a home network

Sunday, March 11, 2012

Connecting to DB over a network

Connecting to Database

Connecting to Database

Thursday, March 8, 2012

Connecting to an instance of MSDE (SQL Server) on a remote machine

Connecting to an alias fails

Connecting to an alias fails

Wednesday, March 7, 2012

Connecting to a remote sql server for merge replication (push) in SQL Server 2005 Replicat

Connect to SQL Server

Blog Archive

About Me